hey guys

ok, i got this custom built/modified suse linux setup, and it has this ip interface with an ipv6 link local address and a ipv6 application address (addressing used by other applications.)

eth0 inet6 fe80::6:ff:fe00:2%i6dd2 prefixlen 64 scopeid 0xb
inet6 2001:1b70:4292:8225::5 prefixlen 128
>

> ping6 2001:1b70:4292:8225::5
PING6(56=40+8+8 bytes) 2001:1b70:4292:8225::5 --> 2001:1b70:4292:8225::5
16 bytes from 2001:1b70:4292:8225::5, icmp_seq=0 hlim=64 time=0.279 ms
16 bytes from 2001:1b70:4292:8225::5, icmp_seq=1 hlim=64 time=0.334 ms
^C

--- 2001:1b70:4292:8225::5 ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.279/0.306/0.334/0.028 ms
> ping6 fe80::6:ff:fe00:2
UDP connect

as you can see, if I ping the 2001---5 it works, but link local just gives me UDP connect. So i don't know what's wrong with it. whether it is working or not.

thanks guys

Try adding the -I eth0 parameter. ping6 fe80::6:ff:fe00:2%0xb may also work.

Link-local addresses have a limited scope, which means they are only visible in a certain context. That's how it's possible to have a link-local address on every interface although technically, the addresses all belong in the same subnet.

However, I have no idea why ping6 would return "UDP connect" when you try to ping the link-local address without a scope identifier. The version of ping6 on my system simply returns "unknown host".

hi ser olmy

thanks for the clarification, you are right, if i include -i ping works.

davy