May 26, 201412 yr I'm running unRAID beta 6 and trying to understand how unRAID allocates the installed NICs, I have one onboard nic and a dual intel nic card as below: r8169 0000:07:00.0 eth0: RTL8168evl/8111evl at 0xffffc9000006e000, bc:5f:f4:bc:b4:fb, XID 0c900880 IRQ 149 r8169 0000:07:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] e1000 0000:04:06.0 eth1: (PCI:33MHz:32-bit) 00:11:0a:15:25:65 e1000 0000:04:06.0 eth1: Intel® PRO/1000 Network Connection e1000 0000:04:06.1 eth2: (PCI:33MHz:32-bit) 00:11:0a:15:25:64 e1000 0000:04:06.1 eth2: Intel® PRO/1000 Network Connection Currently I have xen as a host with one guest and only one bridge (on the onboard realtek card). I'd like to install pfsense, so in trying to prepare for that I've been thinking about how to use the nics I have. So ultimately I guess it makes sense to create bridges instead on passing through the dual nic card - one for LAN and the other for WAN access. (Maybe there's a better setup here, thoughts?) As such I'm thinking about disabling the onboard nic and creating two bridges for the dual intel nic card, does this make sense? Before doing that, I'm trying to understand the output of ifconfig and how /boot/config/network.cfg fits in? br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.99 netmask 255.255.255.0 broadcast 192.168.1.255 ether 00:11:0a:XX:XX:XX txqueuelen 0 (Ethernet) RX packets 2204 bytes 166008 (162.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1632 bytes 655230 (639.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether bc:5f:f4:XX:XX:XX txqueuelen 1000 (Ethernet) RX packets 3085 bytes 514270 (502.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3464 bytes 776247 (758.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 ether 00:11:0a:XX:XX:XX txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth2: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 ether 00:11:0a:XX:XX:XX txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 # Generated settings: USE_DHCP="no" IPADDR="192.168.XX.XX" NETMASK="255.255.255.0" GATEWAY="192.168.XX.XX" DHCP_KEEPRESOLV="no" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" DNS_SERVER3="" BONDING="no" BONDING_MODE="1" BRIDGING="yes" BRNAME="br0" BRSTP="yes" What makes no sense to me, eth0 (the realtek card mac:bc:5f:f4:XX:XX:XX) is associated with br0, yet br0 has a mac address from one of the intel nics (00:11:0a:XX:XX:XX) which is what I wouldn't expect. I would expect br0 to have the same mac as eth0 (bc:5f:f4:XX:XX:XX). What's going on here? EDIT: I guess all of the nics are being added to the same bridge by default, doing: brctl delif br0 eth1 brctl delif br0 eth2 seems to have cleared it up, br0 has the correct mac. Not sure why, but I think this is what's happening. Also the network.cfg from what I understand only pertains to the first nic found on the system, right? Will that always be the same on every reboot? And finally, additional brX's will need to be configured in the go file? Correct?
May 26, 201412 yr I am not sure why your Mac addresses are mixed up but I can tell you how I setup my pfsense VM. With my setup I am passing through 2 NIC's for pfsense and keeping one NIC for unRAID. I didn't do anything with bridges. An important note: each NIC has its own PCI device ID (even your dual NIC). First thing to do is exclude the two NIC's when unRAID boots. Then assign those same PCI ID's to the pfsense VM. Start up pfsense and you should see two NIC's available to assign.
May 26, 201412 yr Author For some reason the other interfaces were also assigned to br0, don't know why but after I did: brctl delif br0 eth1 brctl delif br0 eth2 the correct mac address shows up on br0. Just to understand your setup: you have onboard + dual nics? So your unRAID has no bridges? So you have three ethernet cables, two (onboard + one nic from the dual) going to the same switch and same subnet? and the other to your modem? What's your topology like? As for your setup, if I pass through both NICs and use them for LAN/WAN then I guess I wouldn't be able to use the LAN nic for any other guest. I would then have to use the onboard nic (realtek) for guests. That means I would have two nics running to the same switch for the same LAN and the WAN to the modem. And if I do disable the onboard nic and stick with the intels I can't do what you suggest? Just asking what's the "best practice" way of doing this.
May 26, 201412 yr For some reason the other interfaces were also assigned to br0, don't know why but after I did: brctl delif br0 eth1 brctl delif br0 eth2 the correct mac address shows up on br0. Just to understand your setup: you have onboard + dual nics? So your unRAID has no bridges? So you have three ethernet cables, two (onboard + one nic from the dual) going to the same switch and same subnet? and the other to your modem? What's your topology like? As for your setup, if I pass through both NICs and use them for LAN/WAN then I guess I wouldn't be able to use the LAN nic for any other guest. I would then have to use the onboard nic (realtek) for guests. That means I would have two nics running to the same switch for the same LAN and the WAN to the modem. And if I do disable the onboard nic and stick with the intels I can't do what you suggest? Just asking what's the "best practice" way of doing this. My motherboard as 2 onboard NIC's and I added a PCIe NIC. Yes I do have three Ethernet cables. So modem -> pfsense VM WAN -> pfsense VM LAN -> switch -> unRAID. Others suggested to me to just use bridges but I was on a mission to get the 2 onboard NIC's passed through to pfsense... I'm not sure in the best practice? One big down side to a pfsense VM is that you cannot do maintained to unRAID with taking down the internet and therefore you no longer have access to unRAID.
Archived
This topic is now archived and is closed to further replies.