Every time the NAS restarts, my jail then starts without network connectivity.
In the GUI I can see
And in the shell, there is not epair interface listed.
If I restart the jail (not the NAS), I get connectivity right away
And I see epair0b in the shell
What could be causing that? Like could the jail be starting before the driver for the physical network interface?
In the GUI I can see
And in the shell, there is not epair interface listed.
root@plexy:~ # ifconfig
lo0: flags=8008<LOOPBACK,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
groups: pfllog
root@plexy:~ #
If I restart the jail (not the NAS), I get connectivity right away
And I see epair0b in the shell
root@plexy:~ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
groups: pflog
epair0b: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:60:16:02:31
hwaddr 02:30:c0:fd:39:0b
inet 192.168.11.232 netmask 0xfffffe00 broadcast 192.168.11.255
groups: epair
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
nd6 options=1<PERFORMNUD>
root@plexy:~ #
What could be causing that? Like could the jail be starting before the driver for the physical network interface?