Re: ping: bind icmp socket: Invalid argument

[Ferenc Wagner <wferi@niif.hu>]

"Gerdriaan Mulder" <naairdreg@gmail.com> writes:

> On 8/23/07, Ferenc Wagner <wferi@niif.hu> wrote:
>
>> Christopher Bodenstein <christopher.bodenstein@be.easynet.net> writes:
>>
>>> On Thu, Aug 23, 2007 at 05:10:56PM +0200, Ferenc Wagner wrote:
>>>
>>> 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:e171", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINVAL (Invalid argument)
>>
>> Am I using an overly old version of ping6?
>> # ping6 -V
>> ping6 utility, iputils-ss020927
>
> As far as I can see, you should type the interface address directly
> after the -I, so -Ieth0 and not -I eth0.

Well, no, -Ieth0 and -I eth0 both work.  With interface address
instead of interface name it doesn't work either way.
-- 
Thanks,
Feri.