darkmatter
Cadet
- Joined
- Feb 27, 2019
- Messages
- 4
Hi everybody!
I use Freenas for over five years now and am very satisfied with its performance. If I came across an issue I could solve it quickly by checking the documentation or googling. However, now I am facing an issue which I seem to fail to overcome by myself and in respect of which I have found no relevant hint in the forum (although a couple of posts seem to relate to it but do in fact not).
The issue is that (typically after a while) jails cannot be accessed from my PC (192.168.10.108) or any laptop in my home network although the jails are running and - if I jexec into them from the FreeNAS shell - have access to the FreeNAS host (192.168.10.8) and internet (also DNS provided by a local DNS server under 192.168.10.40 works fine). The PC has internet connection and can reach the FreeNAS host's WebGUI.
Background:
I recently upgraded to the FreeNAS 11.2 release and created three jails by using the WebGUI. At that point in time each of the three jails could be reached from the PC and worked fine. Since then I can only access any of the jails if I restart them. Then they can be pinged and accessed from the PC but it appears that after a while (it feels like some idle time) the access fails (PING to the jail from the PC and from the jail to the PC does not work, access to web server in the jail fails; however, the jail still has access to the internet and DNS).
Although I have what I believe is a good understanding of different OSes and networking I am stuck and grateful for any hint.
Thank you!
This is the ifconfig of the FreeNAS host (which has two NICs, but as you can see only one is connected with a cable):
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>
ether d8:50:e6:c1:24:8c
hwaddr d8:50:e6:c1:24:8c
inet 192.168.10.8 netmask 0xffffff00 broadcast 192.168.10.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether d8:50:e6:c1:24:8d
hwaddr d8:50:e6:c1:24:8d
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
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
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:39:d5:24:fe:00
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: vnet0:44 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 7 priority 128 path cost 2000
member: vnet0:43 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 2000
member: vnet0:42 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 6 priority 128 path cost 2000
member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 20000
vnet0:42: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: associated with jail: Plex as nic: epair0b
options=8<VLAN_MTU>
ether d8:50:e6:31:41:ea
hwaddr 02:22:d0:00:06:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
vnet0:43: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: associated with jail: nextcloud as nic: epair0b
options=8<VLAN_MTU>
ether d8:50:e6:ba:b5:81
hwaddr 02:22:d0:00:05:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
vnet0:44: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: associated with jail: SABnSick as nic: epair0b
options=8<VLAN_MTU>
ether d8:50:e6:32:33:43
hwaddr 02:22:d0:00:07:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
This is the ifconfig of the plex jail:
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 d8:50:e6:ba:b5:82
hwaddr 02:22:d0:00:08:0b
inet 192.168.10.18 netmask 0xffffff00 broadcast 192.168.10.255
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
I use Freenas for over five years now and am very satisfied with its performance. If I came across an issue I could solve it quickly by checking the documentation or googling. However, now I am facing an issue which I seem to fail to overcome by myself and in respect of which I have found no relevant hint in the forum (although a couple of posts seem to relate to it but do in fact not).
The issue is that (typically after a while) jails cannot be accessed from my PC (192.168.10.108) or any laptop in my home network although the jails are running and - if I jexec into them from the FreeNAS shell - have access to the FreeNAS host (192.168.10.8) and internet (also DNS provided by a local DNS server under 192.168.10.40 works fine). The PC has internet connection and can reach the FreeNAS host's WebGUI.
Background:
I recently upgraded to the FreeNAS 11.2 release and created three jails by using the WebGUI. At that point in time each of the three jails could be reached from the PC and worked fine. Since then I can only access any of the jails if I restart them. Then they can be pinged and accessed from the PC but it appears that after a while (it feels like some idle time) the access fails (PING to the jail from the PC and from the jail to the PC does not work, access to web server in the jail fails; however, the jail still has access to the internet and DNS).
Although I have what I believe is a good understanding of different OSes and networking I am stuck and grateful for any hint.
Thank you!
This is the ifconfig of the FreeNAS host (which has two NICs, but as you can see only one is connected with a cable):
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>
ether d8:50:e6:c1:24:8c
hwaddr d8:50:e6:c1:24:8c
inet 192.168.10.8 netmask 0xffffff00 broadcast 192.168.10.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether d8:50:e6:c1:24:8d
hwaddr d8:50:e6:c1:24:8d
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
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
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:39:d5:24:fe:00
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: vnet0:44 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 7 priority 128 path cost 2000
member: vnet0:43 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 2000
member: vnet0:42 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 6 priority 128 path cost 2000
member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 20000
vnet0:42: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: associated with jail: Plex as nic: epair0b
options=8<VLAN_MTU>
ether d8:50:e6:31:41:ea
hwaddr 02:22:d0:00:06:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
vnet0:43: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: associated with jail: nextcloud as nic: epair0b
options=8<VLAN_MTU>
ether d8:50:e6:ba:b5:81
hwaddr 02:22:d0:00:05:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
vnet0:44: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: associated with jail: SABnSick as nic: epair0b
options=8<VLAN_MTU>
ether d8:50:e6:32:33:43
hwaddr 02:22:d0:00:07:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
This is the ifconfig of the plex jail:
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 d8:50:e6:ba:b5:82
hwaddr 02:22:d0:00:08:0b
inet 192.168.10.18 netmask 0xffffff00 broadcast 192.168.10.255
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair