ping: bind icmp socket: Invalid argument

Hi,

I'm struggling with ping6.  On an IPv6 autoconfigured Etch
machine:

# ip -6 addr list dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,10000> 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 
       valid_lft forever preferred_lft forever

# strace ping6 fe80::214:22ff:fe13:e171
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
connect(4, {sa_family=AF_INET6, sin6_port=htons(1025),
inet_pton(AF_INET6, "fe80::214:22ff:fe13:e171",
&sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1
EINVAL (Invalid argument)
connect: Invalid argument

I can't ping my own link-local address.  Trying a
neighbour:

# strace ping6 fe80::214:22ff:fe13:ed7a
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
connect(4, {sa_family=AF_INET6, sin6_port=htons(1025),
inet_pton(AF_INET6, "fe80::214:22ff:fe13:ed7a",
&sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1
EINVAL (Invalid argument)

Global addresses (either mine or the neighbour's) respond to
ping6,
though.

What am I doing wrong?
-- 
Thanks,
Feri.


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

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 with
-I

cbzen:~$ ping6 -Ieth0 fe80::20d:60ff:feb7:5c69
PING fe80::20d:60ff:feb7:5c69(fe80::20d:60ff:feb7:5c69)
from
fe80::20d:60ff:feb7:5c69 eth0: 56 data bytes
64 bytes from fe80::20d:60ff:feb7:5c69: icmp_seq=1 ttl=64
time=0.033 ms
64 bytes from fe80::20d:60ff:feb7:5c69: icmp_seq=2 ttl=64
time=0.033 ms

--- fe80::20d:60ff:feb7:5c69 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time
1002ms
rtt min/avg/max/mdev = 0.033/0.033/0.033/0.000 ms

> -- 
> Thanks,
> Feri.
> 

Cheers,

Chris

-- 
Christopher Bodenstein   -   christopher.bodensteinbe.easynet.net
           CB8461-RIPE   -   Systems Administrator
    Easynet Belgium SA   -   http://www.be.easynet.net/

     "Great acts are made up of small deeds." Lao
Tsu

Christopher Bodenstein <christopher.bodensteinbe.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
-- 
Thanks,
Feri.


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

As far as I can see, you should type the interface address
directly
after the -I, so -Ieth0 and not -I eth0.
On 8/23/07, Ferenc Wagner <wferiniif.hu> wrote:
> Christopher Bodenstein <christopher.bodensteinbe.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
> --
> Thanks,
> Feri.
>
>
> --
> To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
> with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org
>
>


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

"Gerdriaan Mulder" <naairdreggmail.com> writes:

> On 8/23/07, Ferenc Wagner <wferiniif.hu> wrote:
>
>> Christopher Bodenstein
<christopher.bodensteinbe.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.


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org