Iohyve VM Networking Issue

adrianwi · Nov 3, 2019

Not sure how best to describe this, as something strange happened to my FreeNAS box last night whilst asleep. I woke up to some e-mail from Jetpack to say my Wordpress site which is hosted in a jail on my FreeNAS box was down. When I checked all the other jails, they were unavailable too, although when I looked at the FreeNAS box it was still powered on, but I couldn't access the GUI.

The only option was a hard reboot, and at first glance, everything appeared to come back online, or at least the jails did. I also have a Ubuntu VM, which I use for Crashplan and Docker, but when I checked that the VM had started up, but the network service had failed to start. I rebooted it, but I'm having the same problem:

Code:

[FAILED] Failed to start Raise network interfaces.

I'm still a little lost when it comes to networking, so really not sure how to even start diagnosing this. I think FreeNAS creates a tap interface for the VM, and that appears to be happening according to the console, although it does appear to go up and down a little

Code:

Nov  3 08:42:43 freenas1 rpc.statd: Unsolicited notification from host crashplan.bhyve
Nov  3 08:42:43 freenas1 rpc.statd: Unsolicited notification from host crashplan
Nov  3 08:46:19 freenas1 kernel: tap5: link state changed to DOWN
Nov  3 08:46:19 freenas1 kernel: tap5: link state changed to DOWN
Nov  3 08:46:49 freenas1 kernel: tap5: link state changed to UP
Nov  3 08:46:49 freenas1 kernel: tap5: link state changed to UP
Nov  3 10:33:24 freenas1 kernel: tap5: link state changed to DOWN
Nov  3 10:33:24 freenas1 kernel: tap5: link state changed to DOWN
Nov  3 10:33:38 freenas1 kernel: tap5: link state changed to UP
Nov  3 10:33:38 freenas1 kernel: tap5: link state changed to UP
Nov  3 10:43:00 freenas1 kernel: tap5: link state changed to DOWN
Nov  3 10:43:00 freenas1 kernel: tap5: link state changed to DOWN
Nov  3 10:43:11 freenas1 kernel: tap5: link state changed to UP
Nov  3 10:43:11 freenas1 kernel: tap5: link state changed to UP

Everything was working fine when I went to bed last night, so I'm at a loss as to what might be wrong :-(

Any ideas?

Thanks

adrianwi · Nov 3, 2019

I've just tried to create a new VM and it also can't establish a network automatically, so I'm thinking the problem is related to DHCP?

This is the IfCONFIG on my FreeNAS box:

Code:

root@freenas1:/ # ifconfig
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 0c:c4:7a:33:59:a2
    hwaddr 0c:c4:7a:33:59:a2
    inet 192.168.168.15 netmask 0xffffff00 broadcast 192.168.168.255
    inet6 fe80::ec4:7aff:fe33:59a2%igb0 prefixlen 64 scopeid 0x1
    nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
    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 0c:c4:7a:33:59:a3
    hwaddr 0c:c4:7a:33:59:a3
    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 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
    description: iohyve-bridge-igb0
    ether 02:cd:bc:ed:3c: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: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 15 priority 128 path cost 2000000
    member: vnet0:9 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 14 priority 128 path cost 2000
    member: vnet0:8 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 13 priority 128 path cost 2000
    member: vnet0:7 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 12 priority 128 path cost 2000
    member: vnet0:6 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 11 priority 128 path cost 2000
    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: tap5 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 5 priority 128 path cost 2000000
    member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 1 priority 128 path cost 20000
tap5: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: iohyve-crashplan--
    options=80000<LINKSTATE>
    ether 00:bd:79:db:f8:05
    hwaddr 00:bd:79:db:f8:05
    nd6 options=1<PERFORMNUD>
    media: Ethernet autoselect
    status: no carrier
    groups: tap
vnet0:1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: homeassistant as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:b3:40:32
    hwaddr 02:46:d0: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: vpn as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:49:46:d1
    hwaddr 02:46:d0: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: ssl-proxy as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:68:78:43
    hwaddr 02:46:d0: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: embyms as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:0d:d6:f3
    hwaddr 02:46:d0: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: nextcloud as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:ba:b5:81
    hwaddr 02:46:d0:00:0a:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
vnet0:6: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: limesurvey as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:f4:44:33
    hwaddr 02:46:d0:00:0b:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
vnet0:7: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: dns as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:fd:33:60
    hwaddr 02:46:d0:00:0c:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
vnet0:8: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: calibre as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:66:c6:3f
    hwaddr 02:46:d0:00:0d:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
vnet0:9: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: wordpress as nic: epair0b
    options=8<VLAN_MTU>
    ether 02:ff:60:ed:53:08
    hwaddr 02:46:d0:00:0e:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: Attached to ubuntu
    options=80000<LINKSTATE>
    ether 00:bd:08:3c:3f:00
    hwaddr 00:bd:08:3c:3f:00
    nd6 options=1<PERFORMNUD>
    media: Ethernet autoselect
    status: active
    groups: tap
    Opened by PID 24022

adrianwi · Nov 3, 2019

So, further investigation on another machine and that couldn't get a DHCP address automatically, so I thought I'd try configuring the VM with a static address and it's up and running again.

Would it be possible for a router (in my case a pretty old AirPort Extreme) to stop working as a router, but continue to function as a wireless AP, although I'm sure my wireless devices are all set to auto-assign an IP address. I'm happy that my VM is up and running again, but somewhat confused about what caused it and if I still have a problem somewhere

Important Announcement for the TrueNAS Community.

Iohyve VM Networking Issue

adrianwi

Guru

adrianwi

Guru

adrianwi

Guru

Similar threads