t;
>>> When pinging local-link addresses, you should specify the interface
>>> with -I
>>
>> Ahem, that works, thanks. It's even written clearly in the manual.
>> Too bad that I tried using the interface address instead of the
>> interface name:
> # ping6 -I fe80::214:22ff:fe13:e171 fe80::214:22ff:fe13:ed7a
> ping: bind icmp socket: Invalid argument
>
> where strace reveals
>
> socket(PF_INET6, SOCK_RAW, IPPROTO_ICMPV6) = 3
> bind(3, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6,
> "fe80::214:22ff:fe13:
that I tried using the interface address instead of the
interface name:
# ping6 -I fe80::214:22ff:fe13:e171 fe80::214:22ff:fe13:ed7a
ping: bind icmp socket: Invalid argument
where strace reveals
socket(PF_INET6, SOCK_RAW, IPPROTO_ICMPV6) = 3
bind(3, {sa_family=AF_INET6, sin6_port=htons(0), ine
On Thu, Aug 23, 2007 at 05:10:56PM +0200, Ferenc Wagner wrote:
> Hi,
>
Hello,
> I'm struggling with ping6. On an IPv6 autoconfigured Etch machine:
>
[snip]
> I can't ping my own link-local address. Trying a neighbour:
>
When pinging local-link addresses, you should specify the interface wit
Hi,
I'm struggling with ping6. On an IPv6 autoconfigured Etch machine:
# ip -6 addr list dev eth0
2: eth0: mtu 1500 qlen 100
inet6 2001:738:0:1:214:22ff:fe13:e171/64 scope global dynamic
valid_lft 2592000sec preferred_lft 604800sec
inet6 fe80::214:22ff:fe13:e171/64 scope link
5 matches
Mail list logo