9.3 - trouble installing plugin on 2nd NIC

[Barry]

Hi,

I'm running FreeNAS-9.3-STABLE-201602031011...

I have 2 NICs (Internal (192.168.11.9) + DMZ (.211.9)). All services (HTTP, SSH, CIFS) are only bound to Internal.

I have Jails set to use the .211 network.

I installed the Transmission plugin, and got a bunch of errors (below), and the FreeNAS web UI will not load the Plugins-Installed page, or the page sometimes eventually loads but says Transmission is disabled.
It seems like the system is trying to connect from the DMZ NIC address to the Transmission service on .129:

[root@freenas] /mnt/v4tb# lsof|grep 12346
python2.7 2791 root 38u IPv4 0xfffff801629e5b70 0t0 TCP 192.168.211.9:24458->192.168.211.129:12346 (SYN_SENT)

Also, I cannot ping the .211.129 IP (I can ping .211.9)

Is this a networking issue or something else?

I don't have IPv6 configured at all, btw.

Thanks,
Barry

Mar 22 20:43:58 freenas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.211.129
Mar 22 20:44:03 freenas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.211.129
Mar 22 20:44:12 freenas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.211.129
Mar 22 20:45:43 freenas warden: Building new Jail... Please wait...
Mar 22 20:45:44 freenas warden: zfs clone v4tb/jails/.warden-template-pluginjail@clean v4tb/jails/transmission_1
Mar 22 20:45:44 freenas warden: Success!
Mar 22 20:45:44 freenas warden: Jail created at /mnt/v4tb/jails/transmission_1
Mar 22 20:45:45 freenas bridge0: Ethernet address: 02:2b:cb:ba:c8:00
Mar 22 20:45:45 freenas kernel: bridge0: link state changed to UP
Mar 22 20:45:45 freenas kernel: bridge0: link state changed to UP
Mar 22 20:45:45 freenas kernel: em0: promiscuous mode enabled
Mar 22 20:45:45 freenas epair0a: Ethernet address: 02:92:bf:00:06:0a
Mar 22 20:45:45 freenas epair0b: Ethernet address: 02:92:bf:00:07:0b
Mar 22 20:45:45 freenas kernel: epair0a: link state changed to UP
Mar 22 20:45:45 freenas kernel: epair0a: link state changed to UP
Mar 22 20:45:45 freenas kernel: epair0b: link state changed to UP
Mar 22 20:45:45 freenas kernel: epair0b: link state changed to UP
Mar 22 20:45:45 freenas kernel: epair0a: promiscuous mode enabled
Mar 22 20:45:45 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Mar 22 20:45:45 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Mar 22 20:46:00 freenas notifier: Performing sanity check on nginx configuration:
Mar 22 20:46:00 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Mar 22 20:46:00 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Mar 22 20:46:07 freenas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://192.168.11.9/plugins/transmission/1/_s/treemenu: timed out
Mar 22 20:48:24 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.11.9/plugins/transmission/1/_s/status: No JSON object could be decoded
Mar 22 20:49:44 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.11.9/plugins/transmission/1/_s/status: No JSON object could be decoded
Mar 22 20:49:57 freenas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://192.168.11.9/plugins/transmission/1/_s/treemenu: timed out


[root@freenas] /mnt/v4tb# warden list -v
id: 1
host: transmission_1
iface:
ipv4: 192.168.211.129/24
alias-ipv4:
bridge-ipv4:
alias-bridge-ipv4:
defaultrouter-ipv4:
ipv6:
alias-ipv6:
bridge-ipv6:
alias-bridge-ipv6:
defaultrouter-ipv6:
autostart: Enabled
vnet: Enabled
nat: Disabled
mac: 02:92:bf:00:07:0b
status: Running
type: pluginjail
flags: allow.raw_sockets=true

 

[Barry]

Does the DMZ network need a default gateway?
Where would I set that?

edit: I tried changing the Jails to use DHCP and re-installed Transmission but it isn't picking up an address from my DHCP server.

Thanks

 

[Barry]

OK... I removed the plugin, deleted the second NIC, reset the Jail configuration and tried again... no luck but different errors.

Then I removed the plugin, rebooted, and tried again... still no luck... here's the log:

Mar 22 22:11:21 freenas kernel: epair0a: link state changed to DOWN
Mar 22 22:11:21 freenas kernel: epair0a: link state changed to DOWN
Mar 22 22:11:21 freenas kernel: epair0b: link state changed to DOWN
Mar 22 22:11:21 freenas kernel: epair0b: link state changed to DOWN
Mar 22 22:11:21 freenas kernel: bridge0: link state changed to DOWN
Mar 22 22:11:21 freenas kernel: bridge0: link state changed to DOWN
Mar 22 22:11:21 freenas kernel: em0: promiscuous mode disabled
Mar 22 22:11:24 freenas kernel: ifa_del_loopback_route: deletion failed
Mar 22 22:11:24 freenas Freed UMA keg (udp_inpcb) was not empty (20 items). Lost 2 pages of memory.
Mar 22 22:11:24 freenas Freed UMA keg (udpcb) was not empty (336 items). Lost 2 pages of memory.
Mar 22 22:11:24 freenas Freed UMA keg (tcp_inpcb) was not empty (20 items). Lost 2 pages of memory.
Mar 22 22:11:24 freenas Freed UMA keg (tcpcb) was not empty (8 items). Lost 2 pages of memory.
Mar 22 22:11:24 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Mar 22 22:11:24 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required

From FreeNAS, I can ping the Transmission jail (.11.129 now), and I can telnet to port 12346, so it seems to be running (I don't know if I tried before from FreeNAS).
However, I cannot ping or access it from my LAN, and the FreeNAS web UI says it's not running.

I should mention I'm running in a VM (ESXi 5.5, PCI Pass-through of LSI for storage); I don't think ESXi would have a problem with multiple IPs on one NIC though, and my PC can see the MAC address of the .129 'NIC' (I'm a bit surprised it gets a different MAC).
And, since FreeNAS can ping it and connect, that wouldn't explain why FreeNAS thinks Transmission isn't running.

Thanks,
Barry

 

[Barry]

This seems similar to https://bugs.pcbsd.org/issues/12108

 

[Joshua Parker Ruehlig]

not sure if you tried this, but in my system with multiple interfaces defined, I always need to disable VIMAGE and assign my jails to specific interface for networking/plugin stuff to work properly.

 

[Barry]

not sure if you tried this, but in my system with multiple interfaces defined, I always need to disable VIMAGE and assign my jails to specific interface for networking/plugin stuff to work properly.

Hi, I hadn't tried that, but I assume now that I'm on a single NIC, it shouldn't be necessary, right?

Thanks,
Barry

 

[Joshua Parker Ruehlig]

not sure, I probably need to do it because my system has 2 different interfaces (which are both laggs) in different networks.