From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 00:52:56 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99AB4106566B for ; Thu, 12 Feb 2009 00:52:56 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (brucec-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:c09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 59F428FC14 for ; Thu, 12 Feb 2009 00:52:56 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 349AB19256 for ; Thu, 12 Feb 2009 00:52:55 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on muon X-Spam-Level: X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 Received: from gluon (unknown [IPv6:2a01:348:10f:0:240:f4ff:fe57:9871]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA for ; Thu, 12 Feb 2009 00:52:55 +0000 (GMT) Date: Thu, 12 Feb 2009 00:52:49 +0000 From: Bruce Cran To: freebsd-net@freebsd.org Message-ID: <20090212005249.10ce416c@gluon> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.14.4; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: IPv6 autoconfiguration fails X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2009 00:52:56 -0000 [forwarding from current@] I recently reinstalled -current on my laptop and have started seeing IPv6 autoconfiguration failing. I have two interfaces re0 and ath0: re0 is plugged in and gets an address via DHCP while I'm not using wireless at the moment so ath0 remains unconfigured. However it seems the IPv6 autoconfiguration tries to use ath0 instead of re0. During boot I see: re0: link state changed to UP Starting Network: lo0 re0. No ALTQ support in kernel ALTQ related functions disabled No ALTQ support in kernel ALTQ related functions disabled No ALTQ support in kernel ALTQ related functions disabled pf enabled add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 net.inet6.ip6.forwarding: 0 -> 0 net.inet6.ip6.accept_rtadv: 0 -> 1 get_llflag() failed, anyway I'll try sendmsg on ath0: Can't assign requested address sendmsg on ath0: Can't assign requested address sendmsg on ath0: Can't assign requested address add net fe80::: gateway ::1 add net ff02::: gateway ::1 IPv4 mapped IPv6 address support=NO Waiting 30s for an interface to come up: ...........(re0) ifconfig shows re0 having IPv4 and IPv6 link-local addresses but no autoconfigured address, while I'm running rtadvd on the router which is connected via re0. -- Bruce Cran