netdev
[Top] [All Lists]

Re: ping6 error

To: David Stevens <dlstevens@xxxxxxxxxx>
Subject: Re: ping6 error
From: Takashi Hibi <hibi665@xxxxxxx>
Date: Thu, 22 Apr 2004 10:31:39 +0900
Cc: netdev@xxxxxxxxxxx, netdev-bounce@xxxxxxxxxxx
In-reply-to: (Your message of "Wed, 21 Apr 2004 15:05:47 -0700") <OFBD219784.C2049213-ON88256E7D.0078B0F7-88256E7D.00796149@us.ibm.com>
References: <OFBD219784.C2049213-ON88256E7D.0078B0F7-88256E7D.00796149@us.ibm.com>
Sender: netdev-bounce@xxxxxxxxxxx
Thank you for the response.

> Takashi Hibi wrote on 04/20/2004 11:08:32 PM:
> 
>> There are IPv6 addresses for which ping6 doesn't work.
>> The host has a global IPv6 address.
> 
>> $ ping6 ff05::1    (site-local multicast address)
>> connect: Cannot assign requested address
> 
> This makes less sense (but doesn't fail for me on 2.6.x kernels).
> Multicast memberships are per-interface, so a multi-homed host or
> router may not have a route for that address to the interface you
> actually wanted. It's almost always best to specify "-I" in ping6
> to get what you want.

The problem occurs with 2.4.x kernel.
And -I option doesn't help. (same result)
I didn't check with newest 2.6.x kernel yet.

> 
>> $ ping6 fec0::1    (site-local address)
>> connect: Cannot assign requested address
> 
> This works fine on my 2.6.1 system talking to my 2.6.5 system,
> when I have an address with an fec0 prefix on both. If you don't,
> it's probably a routing table issue-- try "netstat -A inet6 -rn"
> and see if you have routing table entries on each so that they
> can talk to each other.
> 

If it is a problem of routing talbe, the error would be "network unreachable".
Since the default route is set, I think routing table is OK.
And when the host has an address with fec0 prefix, ping6 succeeds.

Regards,
Takashi Hibi


<Prev in Thread] Current Thread [Next in Thread>