Most people ask for how to disable ipv6, but my problem is: I don’t know how to make ipv6 work. I’ve already got a ipv6 address, but I still cannot visit the ipv6 website. Could any one help me?
ifconfig like below:
eth0 Link encap:Ethernet HWaddr 00:13:D3:EF:C6:FF
inet addr:10.0.20.124 Bcast:10.0.20.255 Mask:255.255.255.0
inet6 addr: fe80::213:d3ff:feef:c6ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:83484 errors:0 dropped:0 overruns:0 frame:0
TX packets:63901 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:86326776 (82.3 Mb) TX bytes:6663521 (6.3 Mb)
Interrupt:23 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:111 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:9992 (9.7 Kb) TX bytes:9992 (9.7 Kb)
How are you trying to visit that site? Internal LAN?
Does your router supports IPv6?
Your ISP has to support IPv6, and also all the routers in between. But if the target is on a LAN IPv6 is not a problem, various services are already listening on IPv6 ports, e.g. Apache.
On 04/30/10 09:16, greenhand wrote:
> Most people ask for how to disable ipv6, but my problem is: I don’t know
> how to make ipv6 work. I’ve already got a ipv6 address, but I still
> cannot visit the ipv6 website. Could any one help me?
> ifconfig like below:
> eth0 Link encap:Ethernet HWaddr 00:13:D3:EF:C6:FF
> inet addr:10.0.20.124 Bcast:10.0.20.255 Mask:255.255.255.0
> inet6 addr: fe80::213:d3ff:feef:c6ff/64 Scope:Link
That is a so-called local-link address, only valid within your local LAN.
For access to the “world” you need an address in the 2000/3 net range.
eth0 Link encap:Ethernet HWaddr 00:0E:A6:38:E6:0D
inet addr:10.0.0.150 Bcast:10.0.255.255 Mask:255.255.0.0
inet6 addr: 2001:888:190f:0:20e:a6ff:fe38:e60d/64 Scope:Global
The ‘Scope’ at the end says it all.
So sign up with a tunnel provider, e.g. SixXS, or better yet, put some pressure
on your ISP so they provide native ipv6.
I also 've seen a lot of threads with problems with IPV6. Do you know how many ISPs now support IPV6?
Many of those problems are actually issues with resolution of IPv6 domains. Some broken resolvers (e.g. inside modem/routers) take a long time to answer AAAA queries (even if the answer is nothing) or actually give a wrong answer. Since there is no control (last I looked) to disable this lookup in libc, the gross fix is to disable IPv6.
On 04/30/10 23:16, framp wrote:
> LittleRedRooster;2159275 Wrote:
>> … or better yet, put some pressure on your ISP so they provide native
> I also 've seen a lot of threads with problems with IPV6. Do you know
> how many ISPs now support IPV6?
Very few, I know, but without clients asking for ipv6 support, nothing will
change until the shit really hits the proverbial fan.
My ISP has at least been providing for a 6to4 tunnel for a number of years
for those who want to experiment with ipv6, and from what I see, the number
of ipv6 enabled sites is increasing steadily.
E.g., when I do a YaST or zypper update, I usually get an ipv6 enabled site
as mirror here in the Netherlands.
ipv6 really is very easy to configure, once you have a reliable connection
from your ISP.
With radvd running somewhere in the network, all other connections happen