1 |
On Wed, Jun 8, 2011 at 5:04 PM, Mick <michaelkintzios@×××××.com> wrote: |
2 |
> On Wednesday 08 Jun 2011 20:51:10 Paul Hartman wrote: |
3 |
>> |
4 |
>> Charter Communications cable internet: |
5 |
>> |
6 |
>> Test with IPv4 DNS record |
7 |
>> ok (0.580s) using ipv4 |
8 |
>> Test with IPv6 DNS record |
9 |
>> ok (0.268s) using ipv6 |
10 |
>> Test with Dual Stack DNS record |
11 |
>> ok (0.256s) using ipv6 |
12 |
>> Test for Dual Stack DNS and large packet |
13 |
>> ok (0.090s) using ipv6 |
14 |
>> Test IPv4 without DNS |
15 |
>> ok (0.148s) using ipv4 |
16 |
>> Test IPv6 without DNS |
17 |
>> ok (0.162s) using ipv6 |
18 |
>> Test IPv6 large packet |
19 |
>> ok (0.092s) using ipv6 |
20 |
>> Test if your ISP's DNS server uses IPv6 |
21 |
>> ok (0.316s) using ipv6 |
22 |
>> |
23 |
>> :) |
24 |
> |
25 |
> I find this rather confusing! Paul is your ISP offering native IPv6 and if |
26 |
> they do does your router speak ipv6? |
27 |
|
28 |
My ISP (Charter) does not offer native IPv6 yet, but they do offer a |
29 |
6RD Border Relay. It is basically an IPv6 tunnel that runs over an |
30 |
IPv4 network, but the important part is that the tunnel server is |
31 |
running within my ISP's network. That means I get my full internet |
32 |
speed on IPv6 traffic! |
33 |
|
34 |
My wireless router is running DD-WRT (which is a Linux distro). It is |
35 |
running kernel 2.6.34 and has all the ipv6 modules enabled in the |
36 |
kernel. Basically, it is setup by loading the "sit" module |
37 |
(CONFIG_IPV6_SIT_6RD in kernel config). Then using the "ip" command to |
38 |
create a sit tunnel and set up the routes for IPv6 traffic, and then |
39 |
starts radvd (the IPv6 router advertisement daemon, think of it as a |
40 |
kind of DHCP server for IPv6 addresses). The process should be exactly |
41 |
the same on OpenWRT. |
42 |
|
43 |
After that, machines on my local network (including wifi) can get both |
44 |
IPv4 and IPv6 addresses from the router and can talk to the outside |
45 |
world on either network. |
46 |
|
47 |
(and then when you get to that point, you should create IPv6 firewall |
48 |
rules on the router and/or computers, or else risk leaving their |
49 |
entire network open to bad guys) |
50 |
|
51 |
> What does your /etc/resolv.conf show? |
52 |
|
53 |
$ cat /etc/resolv.conf |
54 |
nameserver 127.0.0.1 |
55 |
|
56 |
(because I run net-dns/unbound on my local machine). For the other |
57 |
computers/devices they use the DNS server which runs on the router, |
58 |
192.168.0.1 |
59 |
|
60 |
My ISP does offer DNS servers at actual IPv6 addresses, though I'm not |
61 |
using them. |
62 |
|
63 |
> When I run this test I get: |
64 |
> |
65 |
> Test with IPv4 DNS record |
66 |
> ok (0.552s) using ipv4 |
67 |
> Test with IPv6 DNS record |
68 |
> bad (0.197s) |
69 |
> Test with Dual Stack DNS record |
70 |
> ok (0.558s) using ipv4 |
71 |
> Test for Dual Stack DNS and large packet |
72 |
> ok (0.239s) using ipv4 |
73 |
> Test IPv4 without DNS |
74 |
> ok (0.368s) using ipv4 |
75 |
> Test IPv6 without DNS |
76 |
> bad (0.022s) |
77 |
> Test IPv6 large packet |
78 |
> bad (0.025s) |
79 |
> Test if your ISP's DNS server uses IPv6 |
80 |
> ok (0.691s) using ipv4 |
81 |
|
82 |
For example all this stuff just works normally here: |
83 |
|
84 |
$ host ipv6.google.com |
85 |
ipv6.google.com is an alias for ipv6.l.google.com. |
86 |
ipv6.l.google.com has IPv6 address 2001:4860:800b::93 |
87 |
|
88 |
# traceroute6 ipv6.google.com |
89 |
traceroute to ipv6.l.google.com (2001:4860:800b::93) from |
90 |
2602:100:xx:xx:xx:xx:xx:xx, 30 hops max, 24 byte packets |
91 |
1 2602:100:xx:xx:1::1 (2602:100:xx:xx:1::1) 0.459 ms 0.383 ms 0.353 ms |
92 |
2 * * * |
93 |
3 2001:506:100:6c::1 (2001:506:100:6c::1) 11.29 ms 7.999 ms 7.773 ms |
94 |
4 bbr01olvemo.tge0-3-0-4.mo.olve.charter.com (2001:506:100:23::1) |
95 |
9.093 ms 7.715 ms 7.691 ms |
96 |
5 bbr02chcgil.tge0-3-0-0.il.chcg.charter.com (2001:506:100:55::2) |
97 |
33.981 ms 25.812 ms 23.573 ms |
98 |
6 prr01chcgil.tge2-4.il.chcg.charter.com (2001:506:100:317::1) |
99 |
16.862 ms 17.737 ms 16.46 ms |
100 |
7 v201.core1.chi1.he.net (2001:470:0:114::1) 18.04 ms 17.368 ms 24.015 ms |
101 |
8 * * * |
102 |
9 2001:4860::1:0:92e (2001:4860::1:0:92e) 34.911 ms 18.025 ms 25.379 ms |
103 |
10 2001:4860::8:0:281e (2001:4860::8:0:281e) 27.843 ms 28.74 ms 28.569 ms |
104 |
11 2001:4860::2:0:7ef (2001:4860::2:0:7ef) 27.568 ms 28.365 ms 28.221 ms |
105 |
12 2001:4860:0:1::83 (2001:4860:0:1::83) 27.586 ms 37.284 ms 35.649 ms |
106 |
13 iw-in-x93.1e100.net (2001:4860:800b::93) 27.731 ms 27.647 ms 28.372 ms |
107 |
|
108 |
> From Windows7 I can ping ipv6 addresses (but not domain names) because it uses |
109 |
> Teredo, but from Linux I cannot. |
110 |
|
111 |
For Microsoft Windows (at least Windows 7), when it detects IPv6 |
112 |
advertisement server on the local network, it will use it |
113 |
automatically. When no IPv6 is detected, it uses Teredo instead. Maybe |
114 |
your DNS servers don't return IPv6 addresses? |
115 |
|
116 |
On my wife's Windows 7 laptop, it just worked perfectly after I |
117 |
enabled it on my router and her wifi reconnected. All tests on |
118 |
test-ipv6.com pass except for the last DNS test. She can go to sites |
119 |
like http://www.v6.facebook.com no problems. |
120 |
|
121 |
BTW, Windows Vista and 7 generate randomized host IDs for public IPv6 |
122 |
addresses, it's generally advised to disable that. You can do that by |
123 |
running this at administrator cmd prompt: |
124 |
netsh interface ipv6 set global randomizeidentifiers=disabled |
125 |
|
126 |
And now I'll try not to talk about Windows on this list again for the |
127 |
remainder of the year. ;) |
128 |
|
129 |
Hope that helps! |