Hi,

I have a problem(?) with my IPv6 LAN - I am new to the IPv6 business so
maybe this is a silly question.

I have two v6 capable devices on my LAN. One is a Cisco (running IOS
brburke-ipv6-v113_5_5_T-release 139), the other is a i386 running
-current (as of a few weeks ago, i.e. before the elf change).

The i386 is NOT configured as a router. It runs route6d.
During boot it gets assigned the link local address:

 fe80:1::2a0:24ff:fe53:5890

The Cisco gets a link local address

 FE80::260:70FF:FE62:7735

and recognizes a neighbour FE80::2A0:24FF:FE53:5890 (NOTE the missing 1:!!!).

This results in the following curious (at least for me) situation:
From the NetBSD host I can run a ping6 to the cisco:

phil:~>/sbin/ping6 FE80::260:70FF:FE62:7735
PING6(56=40+8+8 bytes) fe80::2a0:24ff:fe53:5890 --> fe80::260:70ff:fe62:7735
16 bytes from fe80::260:70ff:fe62:7735, icmp_seq=0 hlim=255 time=2.093 ms

Ping from the Cisco back to the NetBSD machine works fine too:

sam#ping ipv6 fe80::260:70ff:fe62:7735
Output Interface: Ethernet0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FE80::260:70FF:FE62:7735, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms

So everything seems to be fine, BUT:
Where do I see the  FE80::2A0:24FF:FE53:5890 in the NetBSD ifconfig or
netstat -r output?
Why can't I ping6 on NetBSD to the local address fe80::2a0:24ff:fe53:5890 ???
What's the business of fe80:0: vs. fe80:1: ???
Is it something special with the KAME stack?

BTW ndp -a gives:

Neighbor                      Linklayer Address   Netif Expire    St Flgs Prbs
fe80:1::260:70ff:fe62:7735    0:60:70:62:77:35      ex0  32s       R    R 
fe80:1::2a0:24ff:fe53:5890    0:a0:24:53:58:90      ex0  permanent R      


Should I read more RFCs? (I know, the answer is always YES :-)
It would be nice, if someone could point me to the right direction.

Any ideas?

Greetings,

Andreas

PS Is it a good idea to put link local IPv6 addresses into /etc/hosts?