Epair0 behaves like Schrödinger's cat and is not working anymore after upgrading to 15.0

[DosKobold]

Hey guys,

i updated to 15.0-RELEASE a few days ago. My whole system was broken, but i fixed it (some lib errors). But now i see that my jail networking is not working properly anymore. I use iocage to manage my jails and i only use linux at work, so i am a absolute noob at networking. I can communicate between jails <--> network but not jails <--> host anymore. Therefor my bridge is still working but not the epair. I did not change anything besides the update to 15.0.

Following my ifconfig output and epair0 playing Schrödinger's cat: Existing and non existing at the same time. I do not understand that phenomena.

root@freebsd-nas:~ # freebsd-version
15.0-RELEASE-p1
root@freebsd-nas:~ # ifconfig
re0: flags=1008943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 08:bf:b8:30:a4:da
        inet 192.168.178.161 netmask 0xffffff00 broadcast 192.168.178.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
        options=10<VLAN_HWTAGGING>
        ether 58:9c:fc:10:52:51
        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
        bridge flags=0<>
        member: vnet0.2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                port 8 priority 128 path cost 2000 vlan protocol 802.1q
        member: vnet0.1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                port 5 priority 128 path cost 2000 vlan protocol 802.1q
        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                port 1 priority 128 path cost 20000 vlan protocol 802.1q
        groups: bridge
        nd6 options=9<PERFORMNUD,IFDISABLED>
vnet0.1: flags=1008943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
        description: associated with jail: NextCloudServer2 as nic: epair0b
        options=20000b<RXCSUM,TXCSUM,VLAN_MTU,RXCSUM_IPV6>
        ether 0a:bf:b8:f5:ba:3c
        hwaddr 58:9c:fc:10:83:d3
        groups: epair
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
vnet0.2: flags=1008943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
        description: associated with jail: ShareServer2 as nic: epair0b
        options=20000b<RXCSUM,TXCSUM,VLAN_MTU,RXCSUM_IPV6>
        ether 0a:bf:b8:b2:27:39
        hwaddr 58:9c:fc:10:ea:72
        groups: epair
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
root@freebsd-nas:~ # ifconfig epair0 create
ifconfig: interface epair0 already exists
root@freebsd-nas:~ # ifconfig epair0 destroy
ifconfig: interface epair0 does not exist

I appreciate any help. Thank you very much!

 

[SirDice]

I can communicate between jails <--> network but not jails <--> host anymore. Therefor my bridge is still working but not the epair.

If the epair wasn't working then jails <--> network wouldn't work either. Communications to/from the jails to the network runs over the epair too.

Following my ifconfig output and epair0 playing Schrödinger's cat: Existing and non existing at the same time. I do not understand that phenomena.

They've been renamed; vnet0.1 and vnet0.2.

 

[DosKobold]

If the epair wasn't working then jails <--> network wouldn't work either. Communications to/from the jails to the network runs over the epair too.


They've been renamed; vnet0.1 and vnet0.2.

1. I thought the bridge links the different interfaces. Why does the traffic goes over re0 but cannot reach it?
2. But why is the output so misleading (existing /non-existing)?
3. What can i do now? Or better: Where can i get more information about the current settings to find the error?