All my plugins and jails IPs are suddendly unreachable ERR_CONNECTION_REFUSED

ChuckMCCluck

Dabbler
Joined
Mar 8, 2019
Messages
15
I'm having a really strange issue, I was recently adding a mount point to one of my jails and I realized after rebooting the jail I could no longer reach it with the IP. I couldn't figure out what was wrong so I decided just to restart my whole FREENAS system and after that I couldn't reach any of my jail or plugin IPs even though all of them except that single one were working fine before reboot. The one virtual machine I am running is still reachable by it's IP it seems that only the Jails were effected, I can also log into the jails and successfully ping a website on all of them, some of them are going through my VPN gateway and some of them are just going to the default router gateway.

I don't know what's happening, the only recent change I made to my FREENAS system in the last few weeks was I installed a gigabit ethernet card, I was having a few strange issues with PLEX randomly disconnecting after installing it but other than that I didn't have any issues until now.
 
Joined
Jan 7, 2015
Messages
1,150
This is likely caused by the addition of the new network card I would suspect. Did you remove/disable the old card? Certainly a network issue. Show the output of ifconfig from the host and each jail if you can.

Looking in the jail configs you see lines similar to these (/mnt/iocage/jails/JAIL/config.json)

"interfaces": "vnet0:bridge0",
"ip4": "new",
"ip4_addr": "em0|192.168.1.21/24",

If the new network card is different than in my example em0, it could cause some issues like these id suspect.
 

ChuckMCCluck

Dabbler
Joined
Mar 8, 2019
Messages
15
This is likely caused by the addition of the new network card I would suspect. Did you remove/disable the old card? Certainly a network issue. Show the output of ifconfig from the host and each jail if you can.

Looking in the jail configs you see lines similar to these (/mnt/iocage/jails/JAIL/config.json)

"interfaces": "vnet0:bridge0",
"ip4": "new",
"ip4_addr": "em0|192.168.1.21/24",

If the new network card is different than in my example em0, it could cause some issues like these id suspect.

I haven't tried unplugging the card yet, the FREENAS server is a little hard to get to where I have it, how would I disable it?

Freenas Shell:
Code:
root@freenas[~]# ifconfig
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 98:48:27:58:11:60
        hwaddr 98:48:27:58:11:60
        inet 192.168.1.246 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
re1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 8c:89:a5:82:a3:1f
        hwaddr 8c:89:a5:82:a3:1f
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (10baseT/UTP <half-duplex>)
        status: no carrier
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
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: Attached to Jackett
        options=80000<LINKSTATE>
        ether 00:bd:76:c6:f8:00
        hwaddr 00:bd:76:c6:f8:00
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: active
        groups: tap
        Opened by PID 3986
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:14:82:ad:05: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:5 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 10 priority 128 path cost 2000
        member: vnet0:4 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 9 priority 128 path cost 2000
        member: vnet0:3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 8 priority 128 path cost 2000
        member: vnet0:2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 7 priority 128 path cost 2000
        member: vnet0:1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 6 priority 128 path cost 2000
        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 55
        member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000000
vnet0:1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: couchpotato as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:1c:24:41
        hwaddr 02:25:10:00:06:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
vnet0:2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: sonarr as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:a5:a4:7e
        hwaddr 02:25:10:00:07:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
vnet0:3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: deluge_2 as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:f8:00:6b
        hwaddr 02:25:10:00:08:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
vnet0:4: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: plex-plexpass as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:30:63:77
        hwaddr 02:25:10:00:09:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
vnet0:5: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: deluge as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:56:71:77
        hwaddr 02:25:10:00:0a:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Deluge Jail:
Code:
root@deluge:~ # 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 8c:89:a5:56:71:78
        hwaddr 02:25:10:00:0b:0b
        inet 192.168.1.243 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Deluge 2 Jail:
Code:
root@deluge-2:~ # 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 8c:89:a5:f8:00:6c
        hwaddr 02:25:10:00:09:0b
        inet 192.168.1.244 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Plex Jail:
Code:
root@plex-plexpass:~ # 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 8c:89:a5:30:63:78
        hwaddr 02:25:10:00:0a:0b
        inet 192.168.1.175 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Couch Potato Jail:
Code:
root@couchpotato:~ # 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 8c:89:a5:1c:24:42
        hwaddr 02:25:10:00:07:0b
        inet 192.168.1.147 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Sonarr Jail:
Code:
root@sonarr:~ # 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 8c:89:a5:a5:a4:7f
        hwaddr 02:25:10:00:08:0b
        inet 192.168.1.149 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
 
Joined
Jan 7, 2015
Messages
1,150
Ok this all looks normal, but the question is, is the ethernet cable connected to the new card or the old card then? One is connected and one isnt.
 
Joined
Jan 7, 2015
Messages
1,150
If this is an onboard NIC card, you would disable it in the machine bios. If its not onboard just simply remove it with the machine off.
 
Joined
Jan 7, 2015
Messages
1,150
You might also check to make sure the jails are using re0 as your network card.
Looking in the jail configs you see lines similar to these (/mnt/iocage/jails/JAIL/config.json)

"interfaces": "vnet0:bridge0",
"ip4": "new",
"ip4_addr": "em0|192.168.1.21/24",

If the new network card is different than in my example em0, it could cause some issues like these id suspect.

Id look into this as well, make sure in each config.json you have the correct network card. In your case its re0 not em0 or re1.

nano /mnt/iocage/jails/JAIL/config.json
 
Joined
Jan 7, 2015
Messages
1,150
Also did you set this network card up to use the same ip address as the old one? Something in the stack is wonky because of that change in network card I think.
 

ChuckMCCluck

Dabbler
Joined
Mar 8, 2019
Messages
15
If this is an onboard NIC card, you would disable it in the machine bios. If its not onboard just simply remove it with the machine off.

Ok I removed the gigabit card, plugged the ethernet cable back into the onboard ethernet and rebooted. Freenas is still reachable but the jails still aren't same error when trying to connect through the IP, ERR_CONNECTION_REFUSED, nothing has changed.

Also did you set this network card up to use the same ip address as the old one? Something in the stack is wonky because of that change in network card I think.

I just installed the NIC, plugged in the ethernet cable into the new NIC and booted the server back up when I originally installed it, I didn't modify any settings in FREENAS.
 
Joined
Jan 7, 2015
Messages
1,150
Show me the output of ifconfig with the old NIC connected.
 

ChuckMCCluck

Dabbler
Joined
Mar 8, 2019
Messages
15
Show me the output of ifconfig with the old NIC connected.

Freenas Shell:
Code:
root@freenas[~]# ifconfig
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 8c:89:a5:82:a3:1f
        hwaddr 8c:89:a5:82:a3:1f
        inet 192.168.1.246 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        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
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: Attached to Jackett
        options=80000<LINKSTATE>
        ether 00:bd:7b:62:f8:00
        hwaddr 00:bd:7b:62:f8:00
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: active
        groups: tap
        Opened by PID 4777
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:14:82:ad:05: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:5 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 9 priority 128 path cost 2000
        member: vnet0:4 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 8 priority 128 path cost 2000
        member: vnet0:3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 7 priority 128 path cost 2000
        member: vnet0:2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 6 priority 128 path cost 2000
        member: vnet0:1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 5 priority 128 path cost 2000
        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 3 priority 128 path cost 2000000
vnet0:1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: couchpotato as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:1c:24:41
        hwaddr 02:25:10:00:05:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
vnet0:2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: sonarr as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:a5:a4:7e
        hwaddr 02:25:10:00:06:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
vnet0:3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: deluge_2 as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:f8:00:6b
        hwaddr 02:25:10:00:07:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
vnet0:4: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: plex-plexpass as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:30:63:77
        hwaddr 02:25:10:00:08:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
vnet0:5: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: deluge as nic: epair0b
        options=8<VLAN_MTU>
        ether 8c:89:a5:56:71:77
        hwaddr 02:25:10:00:09:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Plex Jail:
Code:
root@plex-plexpass:~ # 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 8c:89:a5:30:63:78
        hwaddr 02:25:10:00:09:0b
        inet 192.168.1.175 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Couch Potato Jail:
Code:
root@couchpotato:~ # 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 8c:89:a5:1c:24:42
        hwaddr 02:25:10:00:06:0b
        inet 192.168.1.147 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Deluge Jail:
Code:
root@deluge:~ # 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 8c:89:a5:56:71:78
        hwaddr 02:25:10:00:0a:0b
        inet 192.168.1.243 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Deluge 2 Jail:
Code:
root@deluge-2:~ # 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 8c:89:a5:f8:00:6c
        hwaddr 02:25:10:00:08:0b
        inet 192.168.1.244 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair


Sonarr Jail:
Code:
root@sonarr:~ # 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 8c:89:a5:a5:a4:7f
        hwaddr 02:25:10:00:07:0b
        inet 192.168.1.149 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
 
Joined
Jan 7, 2015
Messages
1,150
The new card gets the same ip, you are using all vnet, I would think this should be working. Post me an example of one of your jails config.json
You can find this in /mnt/tank/iocage/jails/JAIL/config.json or iocage get all JAIL
 
Joined
Jan 7, 2015
Messages
1,150
The only difference i see in the physical cards, is the mac addresses. They are both realtek NICs of a similar chipset.

Im curious if once in a jail can you ping a different jail? The FN host? The gateway? Google?

Can you ping all the jails from the host? The gateway? Google?
 

ChuckMCCluck

Dabbler
Joined
Mar 8, 2019
Messages
15
The new card gets the same ip, you are using all vnet, I would think this should be working. Post me an example of one of your jails config.json
You can find this in /mnt/tank/iocage/jails/JAIL/config.json or iocage get all JAIL

Deluge Jail:
Code:
root@freenas[~]# iocage get all deluge
CONFIG_VERSION:14.1
allow_chflags:0
allow_mlock:0
allow_mount:0
allow_mount_devfs:0
allow_mount_nullfs:0
allow_mount_procfs:0
allow_mount_tmpfs:0
allow_mount_zfs:0
allow_quotas:0
allow_raw_sockets:0
allow_set_hostname:1
allow_socket_af:0
allow_sysvipc:0
allow_tun:0
available:readonly
basejail:yes
boot:on
bpf:yes
children_max:0
cloned_release:11.2-RELEASE
comment:none
compression:lz4
compressratio:readonly
coredumpsize:off
count:1
cpuset:off
cputime:off
datasize:off
dedup:off
defaultrouter:192.168.1.186
defaultrouter6:192.168.1.245
depends:none
devfs_ruleset:4
dhcp:off
enforce_statfs:2
exec_clean:1
exec_fib:0
exec_jail_user:root
exec_poststart:/usr/bin/true
exec_poststop:/usr/bin/true
exec_prestart:/usr/bin/true
exec_prestop:/usr/bin/true
exec_start:/bin/sh /etc/rc
exec_stop:/bin/sh /etc/rc.shutdown
exec_system_jail_user:0
exec_system_user:root
exec_timeout:60
host_domainname:none
host_hostname:deluge
host_hostuuid:deluge
host_time:yes
hostid:6f150d5d-f2d7-11e9-8693-8c89a582a31f
hostid_strict_check:off
interfaces:vnet0:bridge0
ip4:new
ip4_addr:vnet0|192.168.1.243/24
ip4_saddrsel:1
ip6:new
ip6_addr:none
ip6_saddrsel:1
jail_zfs:off
jail_zfs_dataset:iocage/jails/deluge/data
jail_zfs_mountpoint:none
last_started:2020-10-17 23:32:35
login_flags:-f root
mac_prefix:8c89a5
maxproc:off
memorylocked:off
memoryuse:off
mount_devfs:1
mount_fdescfs:1
mount_linprocfs:0
mount_procfs:0
mountpoint:readonly
msgqqueued:off
msgqsize:off
nmsgq:off
notes:k
nsemop:off
nshm:off
nthr:off
openfiles:off
origin:readonly
owner:root
pcpu:off
priority:99
pseudoterminals:off
quota:none
release:11.2-RELEASE-p14
reservation:none
resolver:/etc/resolv.conf
rlimits:off
securelevel:2
shmsize:off
stacksize:off
state:up
stop_timeout:30
swapuse:off
sync_state:none
sync_target:none
sync_tgt_zpool:none
sysvmsg:new
sysvsem:new
sysvshm:new
template:no
type:pluginv2
used:readonly
vmemoryuse:off
vnet:on
vnet0_mac:8c89a5567177 8c89a5567178
vnet1_mac:none
vnet2_mac:none
vnet3_mac:none
vnet_default_interface:auto
vnet_interfaces:none
wallclock:off


The only difference i see in the physical cards, is the mac addresses. They are both realtek NICs of a similar chipset.

Im curious if once in a jail can you ping a different jail? The FN host? The gateway? Google?

Can you ping all the jails from the host? The gateway? Google?

I can pretty much do all that, I can ping google from every jail and the host, I can ping another jail from a different jail, I can ping a jail from the host, I can ping the host from a jail. I can ping both my router gateway and my vpn gateway from a jail and the host.
 

ChuckMCCluck

Dabbler
Joined
Mar 8, 2019
Messages
15
I don't know if this helps but my VPN gateway also has PIHole installed, typically when I get a connection refused error that means PIHole is blocking it but I've completely disabled PIHole a few times to see if that was an issue and it didn't change anything. I have other devices that aren't even going through the VPN gateway with PIHole and they can't connect to the jail IP either so I doubt that it's an issue with that. FREENAS has been giving me issues every step of the way since I installed it two years ago and I'm tempted more than ever to just switch to ProxMox but I just got everything setup to how I like it on FREENAS and it would really suck to start over. It doesn't seem like the NIC card was an issue at all considering it isn't even working after removing it, all I can think of is that FREENAS just tripped over itself and broke something because installing the NIC card is all I have done. I'm trying to think of what else I could of done to break something myself, I recently made a Windows share of my Plugins pool, although I did delete the share to see if that was the issue. Could of I messed up some permissions doing that? I didn't move any files around or do anything else to my plugins pool just made a Windows share then deleted it.
 
Last edited:
Joined
Jan 7, 2015
Messages
1,150
Something is hosed up but I can't get my finger on it. Is your gateway actually 192.168.1.186? Also you have ip6 defaultrouter setup with an ip4 address as the gateway inside the jail. Not sure if using but it isn't right. Everything else looks ok to me. I'm not sure where to tell you to go now.

What happens if you set up a new plugin for say CP or something in a new temp jail configured the same way? Does it work as expected? Or it too fails to connect?
 

ChuckMCCluck

Dabbler
Joined
Mar 8, 2019
Messages
15
Something is hosed up but I can't get my finger on it. Is your gateway actually 192.168.1.186? Also you have ip6 defaultrouter setup with an ip4 address as the gateway inside the jail. Not sure if using but it isn't right. Everything else looks ok to me. I'm not sure where to tell you to go now.

What happens if you set up a new plugin for say CP or something in a new temp jail configured the same way? Does it work as expected? Or it too fails to connect?

Well I tried installing a new plugin and I'm getting this error
Code:
[EFAULT] Exception: CallError:[EFAULT] An error occured! Please read above occured, destroyed deluge_3.


Looking this up I'm seeing someone on reddit who is in a very similar situation as me Reddit Post

but he seemed to have messed around with some files in the plugins pool and I know I didn't do so. My plugins pool is on a SSD and I wanted to see how fast the transfer speeds were with this new gigabit NIC I got compared to my standard HDD storage pool. So I created a Windows share for the Plugins pool transferred a 1 gb file to the root of the pool to see the transfer speeds and then immediately deleted the file and deleted the share.
 
Joined
Jan 7, 2015
Messages
1,150
So you make an interesting point sharing the plugin pool out. If these permissions get changed inadvertantly the apps might not start certainly wouldnt start up with wonky permissions. You can check this using ll on the directories in question.

Now a new direction. From inside these jails are the softwares actually running? CP for instance? You can use any manner of ways to see this. top, netstat, etc.. Id see if CP is running and listening inside the jail.

netstat -Wan | grep 5050

If not, do

service couchpotato start
 
Joined
Jan 7, 2015
Messages
1,150
Looks as if you are kind of out of date too. Your jails are 11.2-RELEASE. Also I see alot of these type of issues with people with Realtek onboard NICs. Not saying its the issue but something to consider.
 

ChuckMCCluck

Dabbler
Joined
Mar 8, 2019
Messages
15
So you make an interesting point sharing the plugin pool out. If these permissions get changed inadvertantly the apps might not start certainly wouldnt start up with wonky permissions. You can check this using ll on the directories in question.

Now a new direction. From inside these jails are the softwares actually running? CP for instance? You can use any manner of ways to see this. top, netstat, etc.. Id see if CP is running and listening inside the jail.

netstat -Wan | grep 5050

If not, do

service couchpotato start

Code:
netstat -Wan | grep 5050

Doesn't return anything and
Code:
service couchpotato start

returns
Code:
Starting couchpotato.
su: /bin/csh: Permission denied
/usr/local/etc/rc.d/couchpotato: WARNING: failed to start couchpotato


Seems like it is a permission issue?
 
Top