FreeNAS 11.1 Bridging Ethernet Change?

Status
Not open for further replies.

fricker_greg

Explorer
Joined
Jun 4, 2016
Messages
71
Hey all, I have had the following system set up originally on 9.2 -> 9.3 -> 9.10 -> 11.1 where I set up a bridging init script to be run at start up that I use to connect directly to my FreeNAS to access the files over 10Gbe:

X9SRH-7TF (with 2 10GBe NICs)
64 GB ECC Ram
E5-1620 V2
6 x 4TB WD red in raidz2

This was the script I set to do at start up in init:

Code:
ifconfig ix0 up; ifconfig bridge3 create; ifconfig bridge3 addm ix1 addm ix0 up


One ethernet port was plugged into my network switch and one goes back to my main rig. This was set up during the 9.2 days and has been working great for me during 9.3 and 9.10. I was able to both access my storage on FreeNAS at 10GBe speeds and access the internet. However, when upgrading to 11.1, I found that I am only able to access the internet but I am not able to mount any of my shares from the ethernet as I used to be able to. I can also not log into the freenas box while using the ethernet only, but I have no problems accessing the internet or other devices on my network.

I think that the bridge is just tunneling data over to the other port without letting me access the server in the interim. Did something change from FreeBSD 10 to 11 that could explain this change in behavior? I think not as 9.10 was based on FreeBSD 10. Is there something I should change about this script?

I apologize for the limit use case of this post and the fact that this is a gerry-rigged scenario, but it has been rock solid for me for the last year or so. Thank you for your response.
 

fricker_greg

Explorer
Joined
Jun 4, 2016
Messages
71
output of ifconfig

Code:
ix0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

	options=a400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>

	ether 0c:c4:7a:5e:ca:f6

	hwaddr 0c:c4:7a:5e:ca:f6

	nd6 options=9<PERFORMNUD,IFDISABLED>

	media: Ethernet autoselect (10Gbase-T <full-duplex>)

	status: active

ix1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

	options=a400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>

	ether 0c:c4:7a:5e:ca:f7

	hwaddr 0c:c4:7a:5e:ca:f7

	inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 

	nd6 options=9<PERFORMNUD,IFDISABLED>

	media: Ethernet autoselect (1000baseT <full-duplex,rxpause,txpause>)

	status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

	options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>

	inet6 ::1 prefixlen 128 

	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 

	inet 127.0.0.1 netmask 0xff000000 

	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

	groups: lo 

bridge3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

	ether 02:11:1a:e6:cb:03

	nd6 options=9<PERFORMNUD,IFDISABLED>

	groups: bridge 

	id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15

	maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200

	root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0

	member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

			ifmaxaddr 0 port 5 priority 128 path cost 2000

	member: ix0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

			ifmaxaddr 0 port 1 priority 128 path cost 2000

	member: ix1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

			ifmaxaddr 0 port 2 priority 128 path cost 2000

epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

	options=8<VLAN_MTU>

	ether 02:65:50:00:05:0a

	hwaddr 02:65:50:00:05:0a

	nd6 options=1<PERFORMNUD>

	media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)

	status: active

	groups: epair
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
You can try asking if anything changed on the FreeBSD forums, since they're probably more aware of this sort of detail.
 
Status
Not open for further replies.
Top