1 |
On Fri, Jan 6, 2012 at 3:09 PM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> Grant Edwards wrote: |
3 |
>> I've enabled ipv6 support in my kernel and it appears to be working on |
4 |
>> the "lo" interface: |
5 |
>> |
6 |
>> # ip -6 addr show lo |
7 |
>> |
8 |
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 |
9 |
>> inet6 ::1/128 scope host |
10 |
>> valid_lft forever preferred_lft forever |
11 |
>> |
12 |
>> # ping6 -c3 ::1 |
13 |
>> |
14 |
>> PING ::1(::1) 56 data bytes |
15 |
>> 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.022 ms |
16 |
>> 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.021 ms |
17 |
>> 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.021 ms |
18 |
>> |
19 |
>> --- ::1 ping statistics --- |
20 |
>> 3 packets transmitted, 3 received, 0% packet loss, time 1998ms |
21 |
>> rtt min/avg/max/mdev = 0.021/0.021/0.022/0.003 ms |
22 |
>> |
23 |
>> And the other interfaces all have link-local addresses: |
24 |
>> |
25 |
>> # ip -6 addr show eth1 |
26 |
>> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 |
27 |
>> inet6 fe80::216:17ff:fe84:a7b3/64 scope link |
28 |
>> valid_lft forever preferred_lft forever |
29 |
>> |
30 |
>> But I can't ping6 any of the "real" interfaces (or any external |
31 |
>> address): |
32 |
>> |
33 |
>> # ping6 -c3 fe80::216:17ff:fe84:a7b3 |
34 |
>> |
35 |
>> connect: Invalid argument |
36 |
>> |
37 |
>> Why can I ping "lo" at ::1 and not "eth1" at fe80::216:17ff:fe84:a7b3? |
38 |
>> |
39 |
>> I'm guessing there might other packages I have to re-emerge with the |
40 |
>> ipv6 use flag. But, I do not want to rebuild everything capable of |
41 |
>> supporting ipv6, since there are only a few selected programs that |
42 |
>> I'll be using with ipv6. I thought I might have to rebuild glibc, but |
43 |
>> it doens't list ipv6 as one of it's use flags. |
44 |
>> |
45 |
>> Any hints? |
46 |
>> |
47 |
> |
48 |
> ping6 -c3 fe80::216:17ff:fe84:a7b3%eth0 |
49 |
> |
50 |
> Link-local addresses are only valid at the link-level scope, and you |
51 |
> have to specify which link you're referring to. Global-scope addresses |
52 |
> don't have the same limitation. |
53 |
|
54 |
and to see the scope you can view the output of ifconfig, see |
55 |
something in there like this next to each address: |
56 |
|
57 |
scopeid 0x0<global> |
58 |
scopeid 0x20<link> |