From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ipv6 problem with ping6
Date: Fri, 6 Jan 2012 15:20:01 -0600 [thread overview]
Message-ID: <CAEH5T2Pf17pHTXLypCYc_-pk5buZdhKq_raAzKJ1OJWP=dsAjA@mail.gmail.com> (raw)
In-Reply-To: <4F076320.8030208@gmail.com>
On Fri, Jan 6, 2012 at 3:09 PM, Michael Mol <mikemol@gmail.com> wrote:
> Grant Edwards wrote:
>> I've enabled ipv6 support in my kernel and it appears to be working on
>> the "lo" interface:
>>
>> # ip -6 addr show lo
>>
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
>> inet6 ::1/128 scope host
>> valid_lft forever preferred_lft forever
>>
>> # ping6 -c3 ::1
>>
>> PING ::1(::1) 56 data bytes
>> 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.022 ms
>> 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.021 ms
>> 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.021 ms
>>
>> --- ::1 ping statistics ---
>> 3 packets transmitted, 3 received, 0% packet loss, time 1998ms
>> rtt min/avg/max/mdev = 0.021/0.021/0.022/0.003 ms
>>
>> And the other interfaces all have link-local addresses:
>>
>> # ip -6 addr show eth1
>> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
>> inet6 fe80::216:17ff:fe84:a7b3/64 scope link
>> valid_lft forever preferred_lft forever
>>
>> But I can't ping6 any of the "real" interfaces (or any external
>> address):
>>
>> # ping6 -c3 fe80::216:17ff:fe84:a7b3
>>
>> connect: Invalid argument
>>
>> Why can I ping "lo" at ::1 and not "eth1" at fe80::216:17ff:fe84:a7b3?
>>
>> I'm guessing there might other packages I have to re-emerge with the
>> ipv6 use flag. But, I do not want to rebuild everything capable of
>> supporting ipv6, since there are only a few selected programs that
>> I'll be using with ipv6. I thought I might have to rebuild glibc, but
>> it doens't list ipv6 as one of it's use flags.
>>
>> Any hints?
>>
>
> ping6 -c3 fe80::216:17ff:fe84:a7b3%eth0
>
> Link-local addresses are only valid at the link-level scope, and you
> have to specify which link you're referring to. Global-scope addresses
> don't have the same limitation.
and to see the scope you can view the output of ifconfig, see
something in there like this next to each address:
scopeid 0x0<global>
scopeid 0x20<link>
next prev parent reply other threads:[~2012-01-06 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 21:02 [gentoo-user] ipv6 problem with ping6 Grant Edwards
2012-01-06 21:09 ` Michael Mol
2012-01-06 21:20 ` Paul Hartman [this message]
2012-01-06 21:27 ` Michael Mol
2012-01-06 21:40 ` [gentoo-user] " Grant Edwards
2012-01-06 21:51 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEH5T2Pf17pHTXLypCYc_-pk5buZdhKq_raAzKJ1OJWP=dsAjA@mail.gmail.com' \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox