https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289295

            Bug ID: 289295
           Summary: Host IP address ARP mapping jumps to address-less
                    epair interface added to a bridge unexpectedly
           Product: Base System
           Version: 14.3-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: [email protected]
          Reporter: [email protected]

In a kernel I see:

```
Aug 29 20:27:45 ha kernel: arp: 172.22.9.14 moved from 02:a0:26:ba:7a:0a to
00:e0:67:1f:29:90 on eth0
Aug 30 05:06:40 ha kernel: arp: 172.22.9.14 moved from 00:e0:67:1f:29:90 to
02:a0:26:ba:7a:0a on eth0
Aug 30 05:07:12 ha kernel: arp: 172.22.9.14 moved from 02:a0:26:ba:7a:0a to
00:e0:67:1f:29:90 on eth0
Aug 31 03:24:04 ha kernel: arp: 172.22.9.14 moved from 00:e0:67:1f:29:90 to
02:a0:26:ba:7a:0a on eth0
Aug 31 03:26:58 ha kernel: arp: 172.22.9.14 moved from 02:a0:26:ba:7a:0a to
00:e0:67:1f:29:90 on eth0
```

usually a few times a day, but each day

correct MAC address for 172.22.9.14 is 00:e0:67:1f:29:90 - it is just properly
assigned on igb0, no reconfigurations on a way

but, sometimes, it jumps to 02:a0:26:ba:7a:0a which is of epair1a, added into a
bridge on the same host, igb0 is a member of the bridge
epair1a has no ip address

eth0 above is renamed epair1b in vnet jail, so, it is jail who has apr confused
time to time.


# ifconfig igb0
igb0: flags=1008943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP>
metric 0 mtu 1500
       
options=a520b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,HWSTATS>
        ether 00:e0:67:1f:29:90
        inet 172.22.9.14 netmask 0xffffff00 broadcast 172.22.9.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

# uname -UK
1403000 1403000


# ifconfig epair1a
epair1a: flags=1008943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP>
metric 0 mtu 1500
        description: ha-eth0
        options=8<VLAN_MTU>
        ether 02:a0:26:ba:7a:0a
        groups: epair
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

# ifconfig -j 1 -v eth0
eth0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0
mtu 1500
        options=8<VLAN_MTU>
        ether 00:a0:98:67:f1:a3
        hwaddr 02:a0:26:ba:7a:0b
        inet 172.22.9.15 netmask 0xffffff00 broadcast 172.22.9.255
        groups: epair
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        drivername: epair1

# ifconfig bridge1
bridge1: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric
0 mtu 1500
        description: igb0
        options=0
        ether 58:9c:fc:10:e3:6c
        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: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 8 priority 128 path cost 2000
        member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        groups: bridge
        nd6 options=9<PERFORMNUD,IFDISABLED>

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to