From owner-freebsd-net@freebsd.org Thu Mar 30 02:47:05 2017 Return-Path: Delivered-To: freebsd-net@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 1C0BED25941 for ; Thu, 30 Mar 2017 02:47:05 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [IPv6:2001:19f0:5801:2ba:5400:ff:fe59:15d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BCA13CF9; Thu, 30 Mar 2017 02:47:04 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: by lauren.room52.net (Postfix) with ESMTPSA id BD2F429105; Thu, 30 Mar 2017 13:46:57 +1100 (AEDT) Subject: Re: IPv6: "xxx::x already configured" in logs... why? To: freebsd-net@freebsd.org References: <20140612202349.GA65079@thebighonker.lerctr.org> <20140619.181129.1279477227287764712.hrs@allbsd.org> <20140619140801.GA65420@thebighonker.lerctr.org> <20140620.130812.1612764660960146940.hrs@allbsd.org> Cc: Hiroki Sato , ler@lerctr.org From: Lawrence Stewart Message-ID: Date: Wed, 29 Mar 2017 21:46:51 -0500 User-Agent: Not your concern MIME-Version: 1.0 In-Reply-To: <20140620.130812.1612764660960146940.hrs@allbsd.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 02:47:05 -0000 [resurrecting an old thread] On 19/06/2014 23:08, Hiroki Sato wrote: > Larry Rosenman wrote > in <20140619140801.GA65420@thebighonker.lerctr.org>: > > le> > le> Ideas? (I may be an idiot, so any criticism welcomed). > le> > le> > le> > le> if you need the 1841's config, I can supply that as well. It's using a Hurricane > le> > le> electric Tunnel. > le> > > le> > How frequent were the log message added into /var/log/messages? And > le> > when did it start to happen after boot. Just after lagg0 is > le> > configured? > le> > > le> > -- Hiroki > le> Looks like: > le> > le> Jun 12 07:00:01 thebighonker kernel: in6_ifadd: 2001:470:1f0f:3ad:223:7dff:fe9e:6e8a is already configured > > Thank you. Three more questions: > > 1. output of "ifconfig lagg0", "ifconfig bce0", and "ifconfig bce1". > > 2. output of "netstat -s -i". > > 3. output of "ndp -p". > > The cause of the message is that the automatically-configured address > is not recognized as "configured" one and FreeBSD IPv6 stack is > trying to add it every time a Router Advertisement message is > received. I am still not sure why it happened, but the above three > would help for further investigation. I've recently set up a VPS with v6 and am seeing the same "in6_ifadd: is already configured" messages in response to periodically received router advertisements every 5-10 mins. The host is a KVM-based virtual machine with vtnet-based NIC. v6 is fully functional with the statically assigned v6 address, but the spam in /var/log/messages is annoying. FreeBSD revision: FreeBSD lauren 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315059: Sun Mar 12 20:44:50 AEDT 2017 root@builder-head-amd64:/usr/obj/lauren/usr/src/sys/GENERIC-NODEBUG amd64 Relevant bits from /etc/rc.conf: rtsold_enable="YES" ipv6_activate_all_interfaces="YES" rtsold_flags="-aF" ifconfig_vtnet0_ipv6="inet6 prefixlen 64" Interface: vtnet0: flags=8843 metric 0 mtu 1500 options=6c07bb ether inet netmask 0xfffffe00 broadcast inet6 %vtnet0 prefixlen 64 scopeid 0x1 inet6 prefixlen 64 nd6 options=23 media: Ethernet 10Gbase-T status: active I would have thought rtsold should be able to play nice with statically assigned v6 addresses... any ideas? Cheers, Lawrence