On Wed, 03 Feb 2016 06:55:47 -0800 "Chris H" <bsd-li...@bsdforge.com> wrote

> On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerstål <pe...@pean.org> wrote
> 
> > Hi!
> > 
> > I recently upgraded my system to 11-CURRENT (FreeBSD 11.0-CURRENT #0 
> > r295087: Sun Jan 31 10:21:31 CET 2016) and after that all of my other 
> > devices in the network complains about arp-flapping:
> > 
> > arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> > arp: 172.25.0.1 moved from 02:e8:ea:15:66:00 to 00:00:24:d0:9e:5d on re0
> > arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> > 
> FWIW I'm seeing this too. As it happened; I had just changed upstream
> providers, getting a larger static block (IP's), as well as updating
> my long overdue -CURRENT. So I simply blamed it on their (upstream)
> network. I'd love to get to the bottom of this, and would be happy to
> help.
> 
> FreeBSD dev-box 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294112:
> Mon Jan 18 14:25:01 PST 2016 root@dev-box:/usr/obj/usr/src/sys/DEVBOX amd64
> 
> src is at Revision: 406193
> 
Well, it would have helped if I had also mentioned that I'm not using
a bridge, and list the interfaces involved. :/

nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=82008<VLAN_MTU,WOL_MAGIC,LINKSTATE>

This also occurs on my 9-STABLE boxes
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500  
options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>

nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=82008<VLAN_MTU,WOL_MAGIC,LINKSTATE>

nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=82008<VLAN_MTU,WOL_MAGIC,LINKSTATE>

--Chris
> 
> > 
> > It seems to be flapping between the virtual mac of my bridge interface 
> > and the actual mac adress on the physical interface. This was not the 
> > case when i ran FreeBSD 10.2. Is there some settings I need to do?
> > 
> > 
> > bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
> > 1500
> >          description: wired <-> wifi bridge
> >          ether 02:e8:ea:15:66:00
> >          inet 172.25.0.1 netmask 0xffffff00 broadcast 172.25.0.255
> >          inet6 2001:470:de59::1 prefixlen 64
> >          inet6 fe80::2%bridge0 prefixlen 64 scopeid 0xb
> >          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: wlan2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
> >                  ifmaxaddr 0 port 10 priority 128 path cost 66666
> >          member: wlan1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
> >                  ifmaxaddr 0 port 9 priority 128 path cost 66666
> >          member: wlan0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
> >                  ifmaxaddr 0 port 8 priority 128 path cost 22222
> >          member: em1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
> >                  ifmaxaddr 0 port 2 priority 128 path cost 2000000
> > 
> > em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 
> > mtu 1500
> >          description: wired LAN
> >  
> > options=42098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
> >          ether 00:00:24:d0:9e:5d
> >          nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> >          media: Ethernet autoselect (1000baseT <full-duplex>)
> >          status: active
> > 
> > 
> > /Peter.
> 
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to