From owner-freebsd-current@FreeBSD.ORG Tue Mar 29 12:07:39 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8BC7106566B for ; Tue, 29 Mar 2011 12:07:39 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 56C278FC1B for ; Tue, 29 Mar 2011 12:07:38 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id p2TBYN2v051967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Mar 2011 13:34:23 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.4/8.14.4) with ESMTP id p2TBYKiH012509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Mar 2011 13:34:20 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id p2TBYKJj034129; Tue, 29 Mar 2011 13:34:20 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id p2TBYFs8034128; Tue, 29 Mar 2011 13:34:15 +0200 (CEST) (envelope-from ticso) Date: Tue, 29 Mar 2011 13:34:14 +0200 From: Bernd Walter To: "Daniel O'Connor" Message-ID: <20110329113414.GA33138@cicely7.cicely.de> References: <451C39DA-76B9-4767-9FFC-24F2A182E301@dons.net.au> <0C27BDBF-1F22-4DFD-A1A5-48D0BD1618BC@gsoft.com.au> <71147117-D87B-4F36-9838-238E144BB51F@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: Sergey Kandaurov , freebsd-current Current Subject: Re: ipv6 / rtadv problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2011 12:07:40 -0000 On Tue, Mar 29, 2011 at 08:24:53PM +1030, Daniel O'Connor wrote: > > On 29/03/2011, at 19:05, Sergey Kandaurov wrote: > >> This is repeatable after a reboot, I haven't experienced with FreeBSD 8.x. > >> > > > > I would assume an NDP communication problem or some such, > > it would be interesting to see this sort of traffic, also ifconfig and > > ndp -a output. > > Grr.. I had to reinstall today because I forgot to create a swap partition and now I can't reproduce the problem :( NDP effectively replaces ARP for IPv6. Like ARP it is also learning by received packets and not only by direct query and because of this problems might be unnoticed. Unlike ARP NDP is using multicast - instead of sending the inquiry to a broadcast address each address has a solicatated multicast address where the query goes to. A NIC driver might have broken multicast support, I doub't that's a problem for your em, but it is more likely that the bug is on the other host. It also could be a problem with multicast aware switches - getting multicast switiching right isn't an easy task and many implementations are full of bugs. If an NDP entry expires a host typically reasks using the unicast address and the last known MAC, so once everything seems to run an underlying multicast problem can live unnoticed for a much longer time. Currently my own LAN router has a NIC driver with broken multicast support and nevertheless everything seems to work fine since months now, but I know the bug is there and that it can bite me each day. And unlike ARP NDP is ICMPv6 and not an individual protocol, some people agressivlely filter ICMPv*, which can easily catch too much. Especially since many people configuring filter lists are not aware of those solicitated addresses. My assumption is that the problem is with the other host or switch network and you just never noticed this so far because this kind of problem can easily hide for a very long time. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.