Are link-scope addresses ping6'able? (connect: Invalid argument)
I have a machine that is participating in the ipv6 network over a
wireless link. It's receiving router announcements and
autoconfiguring them. In testing, tho, I'm finding that I cannot ping
the link-scoped address. Is that to be expected?
elf@cerise ~ > ip -6 route
2002:XXXX:8e1a:1::/64 dev ath0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev ath0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev ath0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
default via fe80::20c:76ff:feb6:7207 dev ath0 proto kernel metric 1024 expires 1382sec mtu 1500 advmss 1440 hoplimit 64
unreachable default dev lo proto none metric -1 error -101 hoplimit 255
elf@cerise ~ > ip addr
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:0d:60:8d:4a:27 brd ff:ff:ff:ff:ff:ff
3: ath0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 199
link/ether 00:09:5b:68:7c:0a brd ff:ff:ff:ff:ff:ff
inet 192.168.XXX.XXX/24 brd 192.168.8.255 scope global ath0
inet6 2002:XXXX:8e1a:1:209:5bff:fe68:7c0a/64 scope global dynamic
valid_lft 2591759sec preferred_lft 604559sec
inet6 fe80::209:5bff:fe68:7c0a/64 scope link
valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
elf@cerise ~ > ping6 fe80::209:5bff:fe68:7c0a
connect: Invalid argument
Reply to: