Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Mar 2011 16:52:53 +0200
From:      Bernd Walter <ticso@cicely7.cicely.de>
To:        "Daniel O'Connor" <doconnor@gsoft.com.au>
Cc:        freebsd-current@freebsd.org, Marcin Cieslak <saper@saper.info>
Subject:   Re: ipv6 / rtadv problem
Message-ID:  <20110329145253.GA34921@cicely7.cicely.de>
In-Reply-To: <FB4A5B71-6EC6-4CFE-BD84-927A82730913@gsoft.com.au>
References:  <451C39DA-76B9-4767-9FFC-24F2A182E301@dons.net.au> <AANLkTinaELN40kvgDrjN0=iPT1KJNS=P2duFEk7jRS2W@mail.gmail.com> <0C27BDBF-1F22-4DFD-A1A5-48D0BD1618BC@gsoft.com.au> <71147117-D87B-4F36-9838-238E144BB51F@gsoft.com.au> <slrnip3kp3.2dqp.saper@saper.info> <FB4A5B71-6EC6-4CFE-BD84-927A82730913@gsoft.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 29, 2011 at 11:43:57PM +1030, Daniel O'Connor wrote:
> 
> It is running a fairly old FreeBSD (6.x..), maybe there are bugs there..

I don't think there are general bugs about neighbor discovery in FreeBSD
since the beginning, but NIC drivers might have multicast bugs and
although you are running this host since a long time such bugs might be
unnoticed.
You can show and clear the neighbor cache data by using ndp command,
which has similar handling as arp.
If you use tcpdump to debug NDP packets be aware that by enabling
promiscuous mode you get every multicast packet despite of correct
filter setup, so you won't see a problem if the driver isn't
configuring the filter correctly.
On the other hand you can workaround a such driver bug by enabling
promiscuous mode.

-- 
B.Walter <bernd@bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110329145253.GA34921>