Can't connect to Plex after adding second nic

[LordCrc]

I just installed FreeNAS for the first time, and got it running quick quickly with Plex in a jail.

All was smooth until I added a second nic, at which point I could no longer access Plex.

My primary NIC (as identified in the dashboard) is the on-board Intel 1G. It's connected to my LAN.
The secondary NIC is a 10G fiber card connected directly to my desktop PC.

The hardware is working fine, and I can reach SMB via LAN or 10G just fine.

Plex jail is configured to use DHCP, and thus VNet and PF is enabled.

Before I added the second NIC, the list in Network/Interfaces was empty. So I started by adding the LAN interface, em0. I set it to use DHCP (fixed lease in the DHCP server), and nothing else. The DHCP server assigns IPs in 192.168.42.0/24.

Then I added the 10G NIC, with a fixed IP of 10.10.10.1/8. After rebooting I could no longer reach my jailed Plex.

Looking at the Plugin page, I see that Plex has gotten an IP in the 192.xxx range. But from ifconfig on the host and inside jail I see that the vnet adapter is bound to the 10G interface, and the bridge lists this adapter first. So why is it doing this, and how can I make FreeNAS configure the bridge against the primary NIC?

For reference, ifconfig from before starting up Plex jail:

Code:

[root@freenas ~]# ifconfig
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
		ether 9c:5c:8e:93:94:24
		hwaddr 9c:5c:8e:93:94:24
		inet6 fe80::9e5c:8eff:fe93:9424%em0 prefixlen 64 scopeid 0x1
		inet 192.168.42.138 netmask 0xffffff00 broadcast 192.168.42.255
		nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
		media: Ethernet autoselect (1000baseT <full-duplex>)
		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 0x2
		inet 127.0.0.1 netmask 0xff000000
		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
		groups: lo
mlxen0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=ed07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWFILTER,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
		ether 00:02:c9:4e:1d:fa
		hwaddr 00:02:c9:4e:1d:fa
		inet 10.10.10.1 netmask 0xff000000 broadcast 10.255.255.255
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
		status: active
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		ether 02:af:32:46:14:00
		nd6 options=1<PERFORMNUD>
		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: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 1 priority 128 path cost 20000

And after starting Plex:

Code:

[root@freenas ~]# ifconfig
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150
0
		options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
		ether 9c:5c:8e:93:94:24
		hwaddr 9c:5c:8e:93:94:24
		inet6 fe80::9e5c:8eff:fe93:9424%em0 prefixlen 64 scopeid 0x1
		inet 192.168.42.138 netmask 0xffffff00 broadcast 192.168.42.255
		nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
		media: Ethernet autoselect (1000baseT <full-duplex>)
		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 0x2
		inet 127.0.0.1 netmask 0xff000000
		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
		groups: lo
mlxen0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=ed07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS
UM,TSO4,TSO6,LRO,VLAN_HWFILTER,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
		ether 00:02:c9:4e:1d:fa
		hwaddr 00:02:c9:4e:1d:fa
		inet 10.10.10.1 netmask 0xff000000 broadcast 10.255.255.255
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
		status: active
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		ether 02:af:32:46:14:00
		nd6 options=1<PERFORMNUD>
		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: vnet0:6 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 5 priority 128 path cost 2000
		member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 1 priority 128 path cost 20000
vnet0:6: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		description: associated with jail: plex
		options=8<VLAN_MTU>
		ether 02:ff:60:14:fa:09
		hwaddr 02:b0:d0:00:05:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair

edit: maybe this fits better in the networking section, mods feel free to move it.

 

[LordCrc]

Ok, bit confused here now.

Seems while the media type says 10G, from the jail shell I can reach the world:

Code:

root@plex:~ # ifconfig
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 0x1
		inet 127.0.0.1 netmask 0xff000000
		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
		groups: lo
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=8<VLAN_MTU>
		ether 02:ff:60:14:fa:0a
		hwaddr 02:b0:d0:00:06:0b
		inet 192.168.42.169 netmask 0xffffff00 broadcast 192.168.42.255
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair
root@plex:~ # ping -c 1 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=120 time=97.660 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 97.660/97.660/97.660/0.000 ms

Traceroute clearly shows it going directly to my router, not via the 10G link, so media showing 10G is clearly misleading.

So is there any firewall settings that can be messing things up?

 

[LordCrc]

Well then, that was fun.

So, port scanning the host showed that the plex management port was open. That lead me to checking the plex server logs (in jail), which showed that the connection was rejected by plex as being insecure... That's when I noticed the "Manage" option in the plugins menu linked to http and not https. After changing to https I could reach plex.

I must have changed some plex options without recalling after getting plex running, but before installing the second NIC.