From owner-freebsd-current@freebsd.org Wed Feb 3 15:31:59 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0714A99FE4 for ; Wed, 3 Feb 2016 15:31:59 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BA7641D38 for ; Wed, 3 Feb 2016 15:31:59 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u13FWSBZ093857 for ; Wed, 3 Feb 2016 07:32:34 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <56B1ACDF.30807@pean.org>, From: "Chris H" Subject: Re: arp flapping after udating system to 11-CURRENT. Date: Wed, 03 Feb 2016 07:32:34 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2016 15:32:00 -0000 On Wed, 03 Feb 2016 06:55:47 -0800 "Chris H" wrote > On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerstål 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 metric 0 mtu 1500 options=82008 This also occurs on my 9-STABLE boxes re0: flags=8843 metric 0 mtu 1500 options=8209b nfe0: flags=8843 metric 0 mtu 1500 options=82008 nfe0: flags=8843 metric 0 mtu 1500 options=82008 --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 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 > > 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 > > ifmaxaddr 0 port 10 priority 128 path cost 66666 > > member: wlan1 flags=143 > > ifmaxaddr 0 port 9 priority 128 path cost 66666 > > member: wlan0 flags=143 > > ifmaxaddr 0 port 8 priority 128 path cost 22222 > > member: em1 flags=143 > > ifmaxaddr 0 port 2 priority 128 path cost 2000000 > > > > em1: flags=8943 metric 0 > > mtu 1500 > > description: wired LAN > > > > options=42098 > > ether 00:00:24:d0:9e:5d > > nd6 options=29 > > media: Ethernet autoselect (1000baseT ) > > 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"