neighbor discovery problem

Mathieu Arnold mat at FreeBSD.org
Tue Aug 12 12:53:35 UTC 2008


+-le 12.08.2008 13:26:00 +0100, Pete French a dit :
|> The network is pretty simple,
|> 
|> gateway :
|> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|>         options=b<RXCSUM,TXCSUM,VLAN_MTU>
|>         inet6 fe80::207:e9ff:fe0e:dead%em0 prefixlen 64 scopeid 0x1 
|>         inet6 2a01:678:1:443:: prefixlen 64 
|>         inet6 2a01:678:100:: prefixlen 48 
| 
| Hmmm, are machine numbers of all zeroes legal in IPv6 ? I would
| configure those as '2a01:678:1:443::1' and '2a01:678:100::1' if
| I were you. All zeroes as a machine number is certainly a no-no in
| IPv4, and I wouldn't use it in IPv6 either. I have no idea if it's
| actually a problem, but it gives me a bad feeling....

Well, hum, I'm pretty sure there's no network and broadcast addresses in
IPv6. Routing works, ping works, only neighbor discovery does strange things,
from time to time. I'm a bit reluctant to change all that the eve of my going
on vacation.

I just discovered that I can't ping6 ff02::1%em0 on the gateway, well, I can,
there are answers comming back, but, hum, they don't seem to sink in, and
ping6 don't say anything.

I'll investigate.

-- 
Mathieu Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080812/29c0a19d/attachment.pgp


More information about the freebsd-stable mailing list