Pascal Hambourg wrote:
> Hello,
>
> Cork Soaker a écrit :
>> ~$ping6 fe80::20c:76ff:fe81:1
>> connect: Invalid argument
>
> This is a "link local" address, so you must specify which interface to
> use because such an address may be reachable on any interface. For the
> ping6 command, use the -I option, e.g. :
>
> $ ping6 -I eth0 fe80::20c:76ff:fe81:1
>
> With other programs, you can use the syntax <address>%<interface> as the
> destination, e.g. :
>
> $ telnet fe80::20c:76ff:fe81:1%eth0
>
> But it is best to use global or unique local unicast addresses.
That's it! :-D
ping6 worked fine with %eth0 appended to the end, I'm very happy to say. :-)
I really should have figured this out from my Windows days, but alas, I
did not!
However, given that the PC only had two IPv6 addresses,
fe80::20c:76ff:fe81:1 and ::1, I would have hoped the stack would be
able to figure out where to send the ping (as the fe80 address would be
unreachable on lo).
I am, of course, aware of the problem with multiple NICs and link-local
addresses, but this shouldn't affect desktop users, and of course MID
and mobile-IPv6 users, as most will only have one network card, so maybe
this needs to be resolved before stupid Windozers start crying about the
"complexity" of Linux networking?
Thanks again Pascal.
|