Subject: IPv6 interface problem (maybe a de problem, who knows?)
To: None <netbsd-users@netbsd.org>
From: Dustin Sallings <dustin@spy.net>
List: netbsd-users
Date: 08/19/2001 00:10:43
	I'm having a strange problem with an IPv6 router/firewall.  I've
got three interfaces:

NetBSD juan 1.5 NetBSD 1.5 (FIREWALLJUAN) #0: Thu Aug 16 00:09:44 PDT 2001
dustin@juan:/tmp/FIREWALLJUAN i386

juan# ifconfig de0
de0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        media: Ethernet autoselect (100baseTX)
        status: active
        inet 192.168.42.1 netmask 0xffffff00 broadcast 192.168.42.255
        inet6 fe80::2c0:95ff:fefa:d5ff%de0 prefixlen 64 scopeid 0x2
        inet6 3ffe:b80:d9:1::1 prefixlen 48
juan# ifconfig ex0
ex0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        media: Ethernet none (none)
        inet 192.168.1.98 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::210:4bff:fe10:40a4%ex0 prefixlen 64 scopeid 0x1
        inet6 3ffe:b80:d9::1 prefixlen 48
juan# ifconfig gif0
gif0: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1280
        tunnel inet 24.15.92.77 --> 206.123.31.114
        inet6 fe80::210:4bff:fe10:40a4%gif0 -> :: prefixlen 64 scopeid 0xb
        inet6 3ffe:b80:2:46b::2 -> 3ffe:b80:2:46b::1 prefixlen 64


	I can ping any of those interface addresses except
3ffe:b80:d9:1::1 (I recently added de0 for the wireless LAN).  When I try
to ping the de0 address, it just sits there, though I do see this message
in syslog:

Aug 18 23:44:48 juan /netbsd: nd6_lookup: failed to add route for a
neighbor(3ffe:0b80:00d9:0001::0001), errno=17

	This also prevents machines on the wireless LAN from talking.  17
is EEXIST for those who don't want to look it up, however I can't find any
references that would match:

juan# netstat -rn | egrep 3ffe:b80:d9
3ffe:b80:d9::/48              link#1                    UC          0
0   1500  ex0
3ffe:b80:d9::1                00:10:4b:10:40:a4         UHL         1
19   1500  lo0
3ffe:b80:d9:0:2c0:4fff:fe07:cae3 00:c0:4f:07:ca:e3         UHL         0
435   1500  ex0

	I noticed it had a route for the ex0 address to the ex0 MAC
address, so I figured I'd give that a shot on the de0, but adding its
inet6 address on de0 to the MAC of de0 didn't get me anywhere (did get me
a couple new weird kernel messages, though...I got these with dmesg, so
I don't know if they all go together):

nd6_lookup: failed to add route for a neighbor(3ffe:0b80:00d9:0001::0001),
errno=17
nd6_storelladdr: something odd happens
nd6_storelladdr failed

	This *could* be a de problem, as there is something else stranging
happening with de0 (if I don't keep traffic going over it, it claims the
link is dead), but it feels like that's unrelated.

--
SPY                      My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
|    Key fingerprint =  87 02 57 08 02 D0 DA D6  C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________