Re: recent MFC code to 6-STABLE kills ipv6

> On Sun, 2005-11-06 at 18:06 +0900, SUZUKI Shinsuke wrote:
> > Hello Sean,
> > 
> > >>>>> On Sat, 5 Nov 2005 14:39:13 -0800
> > >>>>> sean_at_mcneil.com(Sean McNeil)  said:
> > 
> > > > sean> ping6 does NOT work for
> > > > sean> fe80::203:6dff:fe1a:b19b%dc0
> > > > sean> 2002:18c7:2d36:0:203:6dff:fe1a:b19b
> > > > sean> 2002:18c7:2d36::
> > > >
> > > > It seems an IPv6 operation for dc0 is disabled entirely.  Don't you
> > > > see an error message from your kernel like following?
> > > > 	dc0: possible hardware address duplication detected, disable IPv6
> > > No, nothing like that in any logs.  I can't see how there could  
> > > suddenly be a duplication of hardware addresses.  I agree, though,  
> > > that IPv6 is disabled for dc0.  Some change in the kernel has caused  
> > > this.
> > 
> > I tried the same configuration (with the different interface card)
> > using the latest RELENG-6 in my environment, but I couldn't reproduce
> > your problem.

In order to really duplicate his configuration, you would need to use
the same network card. But of course you can't do that, because he
never mentioned just what card he has.

The dc(4) driver supports a whole bunch of different chips. It really
really really matters that you tell us exactly which one you have.

It would also really really help if you could run a packet dump on
dc0 while trying to ping6 it from another host. You should do
tcpdump -n -e -p -i dc0 so as not to force it into promisc mode.

-Bill

--
=============================================================================
-Bill Paul            (510) 749-2329 | Senior Engineer, Master of Unix-Fu
                 wpaul_at_windriver.com | Wind River Systems
=============================================================================
              <adamw> you're just BEGGING to face the moose
=============================================================================