From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 16:07:40 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 953B4106566B for ; Thu, 12 Feb 2009 16:07:40 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 2FB748FC0C for ; Thu, 12 Feb 2009 16:07:40 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 44609 invoked by uid 89); 12 Feb 2009 16:08:36 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by v6.ibctech.ca with ESMTPA; 12 Feb 2009 16:08:35 -0000 Message-ID: <49944940.2040500@ibctech.ca> Date: Thu, 12 Feb 2009 11:07:28 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Bruce Cran References: <20090212005249.10ce416c@gluon> <4994389D.8050203@ibctech.ca> <20090212154251.5742210a@gluon> In-Reply-To: <20090212154251.5742210a@gluon> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: 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 16:07:41 -0000 Bruce Cran wrote: > On Thu, 12 Feb 2009 09:56:29 -0500 > Steve Bertrand wrote: > >> Bruce Cran wrote: >>> [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. >> There is a very similar issue over on -questions. >> >> Does it help if you disable rtadv on ath0?: >> >> # ndp -i ath0 -- -accept_rtadv > > It didn't help, but your last message on -questions made me realise I'd > made the classic mistake of enabling a firewall but not allowing inbound > icmp[6] packets. As soon as I'd reloaded the rules things started > working again. Good stuff. Just a note that blocking inbound ICMP will break Path MTU discovery, which, if not considered, can be quite difficult to troubleshoot. Cheers, Steve