Date: Wed, 3 Feb 2016 11:13:21 -0500 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: arp flapping after udating system to 11-CURRENT. Message-ID: <56B22721.7000507@freebsd.org> In-Reply-To: <d357d529bafe5a3093daefb90fd37d77@ultimatedns.net> References: <56B1ACDF.30807@pean.org> <fb6bc4b427bcf5285bbca4aaafd07016@ultimatedns.net> <d357d529bafe5a3093daefb90fd37d77@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ORe61JoqG4TF1NSurk68uBn2bTo92jiP1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-02-03 10:32, Chris H wrote: > On Wed, 03 Feb 2016 06:55:47 -0800 "Chris H" <bsd-lists@bsdforge.com> w= rote >=20 >> On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerst=C3=A5l <peter@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= =20 >>> 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. :/ >=20 > nfe0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu= 1500 > options=3D82008<VLAN_MTU,WOL_MAGIC,LINKSTATE> >=20 > This also occurs on my 9-STABLE boxes > re0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu = 1500 =20 > options=3D8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_M= AGIC,LINKSTATE> >=20 > nfe0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu= 1500 > options=3D82008<VLAN_MTU,WOL_MAGIC,LINKSTATE> >=20 > nfe0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu= 1500 > options=3D82008<VLAN_MTU,WOL_MAGIC,LINKSTATE> >=20 > --Chris >> >>> >>> It seems to be flapping between the virtual mac of my bridge interfac= e=20 >>> and the actual mac adress on the physical interface. This was not the= =20 >>> case when i ran FreeBSD 10.2. Is there some settings I need to do? >>> >>> >>> bridge0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric = 0 mtu=20 >>> 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=3D1<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=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP= > >>> ifmaxaddr 0 port 10 priority 128 path cost 66666 >>> member: wlan1 flags=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP= > >>> ifmaxaddr 0 port 9 priority 128 path cost 66666 >>> member: wlan0 flags=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP= > >>> ifmaxaddr 0 port 8 priority 128 path cost 22222 >>> member: em1 flags=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> >>> ifmaxaddr 0 port 2 priority 128 path cost 2000000 >>> >>> em1: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> met= ric 0=20 >>> mtu 1500 >>> description: wired LAN >>> =20 >>> options=3D42098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HW= TSO> >>> ether 00:00:24:d0:9e:5d >>> nd6 options=3D29<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-unsubscribe@freebsd.= org" >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 Chris: If you are not using a bridge, please provide the complete output of ifconfig, and the log messages about the arp flapping, so we can see which two interfaces it is bouncing between. --=20 Allan Jude --ORe61JoqG4TF1NSurk68uBn2bTo92jiP1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWsiclAAoJEBmVNT4SmAt+T+MQALbyTaSu2O90fX3HIOBYI4Qj TN4hHaIxxMHrnsOjOcyhXEyI1aQ6bbI1xoks7E/IDwlt66JEMB47eX9Clr+FONQC FbNXn5zIlOUnZTt1ZHAHQRJRX85xWhHCUT6bjtvPuTEJxrhYClg4hIiS8s8oUhKp bWnyhm568QgDOYmVh1GbAmWZfpfFCYeCunXMVqE3EYfw9jq6N1bW+HRC/pVMmWPH i4qvx/G6ZgR0T1FG6T9sJvJ8DnFHpK1aSbCs7OcfcAmrgK1dNqqHJldcZFvDfGar CIzmV3NgMpEA7k31roR5/lcoBYqMvQ/5hp1U5ybs9woNsYWJtBp8nCkb7e1TpS5F /D+v2DU0ZdQdY15eujnK8P+c7H0yNQp/Iu0RQN81VsI/p9ZNXAYfpmYviKEfa+pt MC2L+aefgGlf8XX2KA5tb80b9mM81bpNCK8xpBeUBYOJeTtXHEtU1uwOrmKpoUOi 6Am2hYhB5h9izZKfd5p4VnfgGfoBjy43Pc8JBmtX6I3cr8qITCUww2kuZibWFlfl AvpxQ2OAu7YGUp6uo0MrKBdtld1dFmg+0aokzZgL93yc65Q7XxWxAnBh2Wz40S38 WHaw9fVYTd35JRnb4kXe2bW5QZXjY6vPlTs2H+nuM3hF6UmohhkDPWrdp0FY8B7M NChVRjUQgXo4EJjAtKQE =WRxD -----END PGP SIGNATURE----- --ORe61JoqG4TF1NSurk68uBn2bTo92jiP1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56B22721.7000507>