10.11.2015 16:23, Carlos E. R. пишет:
cer@Telcontar:~> ping6 "fe80::eee:e6ff:fed7:bb5f"
connect: Invalid argument
cer@Telcontar:~>
Why the second one fails, I can not imagine.
This is link-local address which cannot be interpreted without knowing
scope (loosely speaking, interface) where it is configured. Each
interface may have the *same* address (which is different from IPv4).
You always need to qualify link local address with link to which it applies:
bor@bor-Latitude-E5450:~/src/linux$ ip a l dev wlan0
3: wlan0: mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether 5c:e0:c5:27:c7:70 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.41/24 brd 192.168.1.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::5ee0:c5ff:fe27:c770/64 scope link
valid_lft forever preferred_lft forever
bor@bor-Latitude-E5450:~/src/linux$ ping6 fe80::5ee0:c5ff:fe27:c770
connect: Invalid argument
bor@bor-Latitude-E5450:~/src/linux$ ping6 fe80::5ee0:c5ff:fe27:c770%wlan0
PING fe80::5ee0:c5ff:fe27:c770%wlan0(fe80::5ee0:c5ff:fe27:c770) 56 data
bytes
64 bytes from fe80::5ee0:c5ff:fe27:c770: icmp_seq=1 ttl=64 time=0.039 ms
64 bytes from fe80::5ee0:c5ff:fe27:c770: icmp_seq=2 ttl=64 time=0.050 ms
^C
--- fe80::5ee0:c5ff:fe27:c770%wlan0 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.039/0.044/0.050/0.008 ms
bor@bor-Latitude-E5450:~/src/linux$ ping6 -I wlan0 fe80::5ee0:c5ff:fe27:c770
PING fe80::5ee0:c5ff:fe27:c770(fe80::5ee0:c5ff:fe27:c770) from
fe80::5ee0:c5ff:fe27:c770 wlan0: 56 data bytes
64 bytes from fe80::5ee0:c5ff:fe27:c770: icmp_seq=1 ttl=64 time=0.048 ms
64 bytes from fe80::5ee0:c5ff:fe27:c770: icmp_seq=2 ttl=64 time=0.020 ms
^C
--- fe80::5ee0:c5ff:fe27:c770 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.020/0.034/0.048/0.014 ms
bor@bor-Latitude-E5450:~/src/linux$
--
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org