On Tue, 2007-11-20 at 08:41 -0500, Philip Bellino wrote:
Bazsi,
Linux 2.6.x, Windows XP, Windows Vista, FreeBSD, Solaris 8 and up. All support IPv6 which of course supports Link Local addresses. Execute the following commands to see the IPv6 configuration: Linux/FreeBSD - /sbin/ifconfig Windows - ipconfig /all Solaris - ifconfig -a
This is not what I had mind when I requested packages to support link local addresses. Of course ifconfig does it, otherwise it would not be possible to configure interfaces. I meant something like a telnet client, how do you tell telnet to connect to a link local address? When I tried to do that I got an error: telnet fe80::290:f5ff:fe28:b55e Trying fe80::290:f5ff:fe28:b55e... telnet: Unable to connect to remote host: Invalid argument The reason I asked is to have a peek at the interface they provide for configuring the scope id. I've now tried using telnet/ssh/ping6, and neither could connect to a link-local address. I don't see its use then, it should be used without further configuration, but it turned out it is not possible.
Why the IPv6 gurus require the link local address to be scoped is still a mystery to me, but since it is, the rule is that the stack needs to know which interface to send the IPv6 packet out of, so "ip_ttl" does not apply here. Please note that the scope_id is not needed for Link Global IPv6 addresses.
The reason I mentioned ip_ttl() is, that when setting that to 1 means that the given packet will never leave the network. I originally thought this was the reason to use link-local addresses in the first place. -- Bazsi