how-to block ads
|
|
Share Topic
 |
 |
|
|
|
Reviews:
 ·Google Voice
·Junction Networks
·Callcentric
 ·T-Mobile US
 ·AT&T U-Verse
| reply to ConstantineM
6rd just works indeed! Even when your OS doesn't support it!Over at my FTTU and IPv4-wise, my ZyXEL router stopped working around midnight today (2012-02-15T00) for good, and the connexion seemed quite dead when trying to revive it directly at the ONT with an OpenBSD netbook, too. 2Wire PoS has been disconnected for several months, but I guess they do have that crappy authentication going on after all? Had to put the 2Wire PoS back into service, leaving no excuse not to try 6rd.
6rd is quite boring. It just works. :-)
This is on OS X 10.5 (yes, 10.5, which obviously has no 6rd support).
% printf "%02x%02x:%02x%02x\n" 99 124 xxx xxx
637c:YYYY
sudo ifconfig gif0 tunnel 99.124.xxx.xxx 12.83.49.81
sudo ifconfig gif0 inet6 2602:306:37cY:YYY0::1 prefixlen 60
sudo route add -inet6 default -interface gif0
% traceroute -I 12.83.49.81
traceroute to 12.83.49.81 (12.83.49.81), 32 hops max, 60 byte packets
5 12.83.39.137 (12.83.39.137) 3.583 ms 2.173 ms 1.882 ms
6 12.83.49.81 (12.83.49.81) 1.813 ms 1.518 ms 1.540 ms
% traceroute6 ns4.linode.com
traceroute6 to ns4.linode.com (2600:3c03::a) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets
1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 2.209 ms 1.871 ms 1.815 ms
2 sfcca01jt.ip.att.net (2001:1890:ff:ffff:12:122:126:241) 3.612 ms 3.588 ms 3.687 ms
3 2001:1890:1fff:40d:192:205:33:50 (2001:1890:1fff:40d:192:205:33:50) 5.432 ms * 5.567 ms
4 nyk-b2-v6.telia.net (2001:2000:3018:39::1) 77.77 ms 78.044 ms 78.822 ms
5 nac-ic-114014-nyk-b2.c.telia.net (2001:2000:3080:46::2) 76.989 ms 77.049 ms 76.955 ms
6 e1.2.tbr2.mmu.nac.net (2001:518:1001:3::2) 77.676 ms 77.757 ms 77.78 ms
7 Vlan805.esd1.mmu.nac.net (2001:518:2001:5::2) 78.886 ms 80.195 ms 78.718 ms
8 2001:518:2800:3::2 (2001:518:2800:3::2) 78.69 ms 78.849 ms 78.725 ms
9 ns4.linode.com (2600:3c03::a) 78.33 ms 77.946 ms 77.767 ms
% traceroute ns4.linode.com
traceroute to ns4.linode.com (207.192.70.10), 32 hops max, 40 byte packets
5 12.83.39.137 (12.83.39.137) 3.591 ms 2.302 ms 2.418 ms
6 ppp-151-164-52-233.rcsntx.swbell.net (151.164.52.233) 4.896 ms 4.254 ms 4.098 ms
7 asn4436-nlayer.pxpaca.sbcglobal.net (151.164.46.70) 6.131 ms 6.476 ms 8.813 ms
8 ae0-80g.cr1.pao1.us.nlayer.net (69.22.153.18) 5.656 ms 4.189 ms 4.074 ms
9 ae1-60g.cr1.sfo1.us.nlayer.net (69.22.143.169) 5.371 ms 5.289 ms 5.062 ms
10 xe-1-2-0.cr1.slc1.us.nlayer.net (69.22.142.96) 22.531 ms 22.867 ms 22.016 ms
11 xe-0-3-0.cr1.ord1.us.nlayer.net (69.22.142.101) 56.448 ms 56.244 ms 55.929 ms
12 xe-9-2-0.cr1.ewr1.us.nlayer.net (69.22.142.75) 75.541 ms 75.642 ms 75.418 ms
13 ae1-70g.ar2.ewr1.us.nlayer.net (69.31.94.118) 80.255 ms 79.729 ms 76.732 ms
14 as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net (69.31.95.130) 77.457 ms 76.987 ms 76.975 ms
15 0.e1-2.tbr1.mmu.nac.net (209.123.10.118) 78.117 ms 77.715 ms 78.437 ms
16 vlan803.esd2.mmu.nac.net (209.123.10.30) 78.247 ms 77.647 ms 77.971 ms
17 207.99.53.46 (207.99.53.46) 78.274 ms 77.553 ms 77.599 ms
18 ns4.linode.com (207.192.70.10) 78.482 ms 78.088 ms 78.224 ms
% traceroute ns2.linode.com
traceroute to ns2.linode.com (65.19.178.10), 32 hops max, 40 byte packets
5 12.83.39.137 (12.83.39.137) 3.102 ms 2.376 ms 2.672 ms
6 12.122.200.9 (12.122.200.9) 3.967 ms 3.606 ms 3.714 ms
7 dcr2-so-3-0-0.washington.savvis.net (192.205.32.46) 6.394 ms 192.205.32.50 (192.205.32.50) 5.996 ms 208.51.134.1 (208.51.134.1) 6.122 ms
8 po1-20G.ar3.SJC2.gblx.net (67.16.134.26) 5.954 ms 188.998 ms 200.258 ms
9 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 6.361 ms 6.022 ms 5.615 ms
10 10gigabitethernet1-1.core1.fmt1.he.net (72.52.92.109) 9.235 ms 17.773 ms 6.752 ms
11 linode-llc.10gigabitethernet2-3.core1.fmt1.he.net (64.62.250.6) 10.632 ms 8.125 ms 7.812 ms
12 ns2.linode.com (65.19.178.10) 7.259 ms 6.758 ms 6.698 ms
% traceroute6 ns2.linode.com
traceroute6 to ns2.linode.com (2600:3c01::a) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets
1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 2.729 ms 1.91 ms 1.766 ms
2 la2ca02jt.ip.att.net (2001:1890:ff:ffff:12:122:127:43) 14.564 ms 14.409 ms 14.385 ms
3 10gigabitethernet5-2.core1.lax2.he.net (2001:470:0:1e6::1) 14.458 ms 15.662 ms 24.833 ms
4 10gigabitethernet2-1.core1.lax1.he.net (2001:470:0:72::1) 14.206 ms 14.287 ms 14.391 ms
5 10gigabitethernet7-4.core1.fmt2.he.net (2001:470:0:18d::1) 22.733 ms 23.853 ms 25.081 ms
6 gige-g4-18.core1.fmt1.he.net (2001:470:0:2d::1) 22.758 ms 22.674 ms linode-llc.10gigabitethernet2-3.core1.fmt1.he.net (2001:470:1:1db::2) 23.296 ms
7 ns2.linode.com (2600:3c01::a) 22.903 ms 22.875 ms 22.795 ms
Routing to the first and second IPv6 hops is absolutely great, just as good as comparative IPv4 hops. (No bunch of useless hops anymore.)
However, AT&T's in-network IPv6 routing is oftentimes far from optimal: traffic from AT&T SJC to ISC PAO goes through Chicago, HE FMT — through LAX, but other routes are pretty decent.
Out of other possible problems, seems like dns6rd1.sbcglobal.net and dns6rd2.sbcglobal.net are not anycast, so, the unicast-based CDNs seem to suffer greatly from poor DNS resolution. But the 6rd gateway, 12.83.49.81, is definitely anycast, no questions there! I am still coloured impressed. :-) You don't get 1.5ms tunnel endpoints on residential connexions here and there. :) | |
Reviews:
·Google Voice
·Junction Networks
·Callcentric
·T-Mobile US
·AT&T U-Verse
| The best thing about 6rd is that 2Wire doesn't support it! BTW, best thing about this 6rd tunnel is that 2Wire PoS has no bloody clue about it! So, it most likely cannot impose any stupid stateful inspections or some such!
The 2Wire PoS can be disconnected, rebooted and whatnot, yet all the IPv6 ssh connections would continue as casual (provided you don't try to shove any data over the said ssh pipes during the time when the underlying channel is not available for prolonged periods). Try that with IPv4! (Technically, that's how it should work with publicly routable IPv4 addresses, too; but 2Wire PoS has an SPI firewall that cannot be turned off, so, it doesn't in practice, even if you do pay lots of money for AT&T's Static IPv4 packages.)
...
It's funny how so many people are looking for "killer apps" for IPv6.
If you look at Google's and T-Mobile USA's presentation over at »sites.google.com/site/ipv6implem···0/agenda , you'll notice that IPv6 indeed does have a killer app: IPv6 lets you have p2p again.
p2p is the killer app. IPv6 has it. p2p is not just BitTorrent, it's also iChat AV and all the jazz. Looking at the Yahoo! Broadband slides from SoftBank, you'll quickly come to realise that IPv4 p2p is a walking dead. Internet is a global phenomenon, and IPv4 p2p is walking dead for a fact. | |
Reviews:
·Google Voice
·Junction Networks
·Callcentric
·T-Mobile US
·AT&T U-Verse
| reply to ConstantineM
OS X: gif0 default inet6 route getting lost every 24-hourssaid by ConstantineM:This is on OS X 10.5 (yes, 10.5, which obviously has no 6rd support).
% printf "%02x%02x:%02x%02x\n" 99 124 xxx xxx
637c:YYYY
sudo ifconfig gif0 tunnel 99.124.xxx.xxx 12.83.49.81
sudo ifconfig gif0 inet6 2602:306:37cY:YYY0::1 prefixlen 60
sudo route add -inet6 default -interface gif0
It seems like my default -inet6 route is automatically removed perhaps every 24 hours after being added (happened twice already), so, I either have to re-run `sudo route add -inet6 default -interface gif0` right away before the ssh will take notice, or risk losing all my ssh sessions.
Any ideas what could be removing the default gif0 route? It doesn't seem like I'm running a dhclient or anything: en0 (GigE) is manual static, and en1 (WiFi) is turned off as of a few days, with last /var/db/dhcpclient/leases/ dated a few days ago.
P.S. Just went to the Network Preferences, and noticed that perhaps I should change "Configure IPv6" from "Automatically" to "Off" on the Ethernet interface? | |
Mangix
join:2012-02-16
Concord, CA | i'm trying out something similar but it's not working. the particular line is "V6PREFIX=$(printf '2602:300:%02x%02x:%02x%02x' $(echo $WANIP | tr . ' '))"
that should make a /64 address. but don't i need a /60? | |
Reviews:
·Google Voice
·Junction Networks
·Callcentric
·T-Mobile US
·AT&T U-Verse
| reply to ConstantineM
Solved: OS X gif0 default inet6 route getting lost every 24hsaid by ConstantineM:said by ConstantineM:This is on OS X 10.5 (yes, 10.5, which obviously has no 6rd support).
% printf "%02x%02x:%02x%02x\n" 99 124 xxx xxx
637c:YYYY
sudo ifconfig gif0 tunnel 99.124.xxx.xxx 12.83.49.81
sudo ifconfig gif0 inet6 2602:306:37cY:YYY0::1 prefixlen 60
sudo route add -inet6 default -interface gif0
It seems like my default -inet6 route is automatically removed perhaps every 24 hours after being added (happened twice already), so, I either have to re-run `sudo route add -inet6 default -interface gif0` right away before the ssh will take notice, or risk losing all my ssh sessions. Any ideas what could be removing the default gif0 route? It doesn't seem like I'm running a dhclient or anything: en0 (GigE) is manual static, and en1 (WiFi) is turned off as of a few days, with last /var/db/dhcpclient/leases/ dated a few days ago. FYI: I've got OS X to work by also adding an inet6 route with the gateway being set to my IPv6 address of the gif0 interface explicitly, and since then, the inet6 route no longer disappears, so, my problem appears solved.
It seems, however, that after a reboot, you do have to add the route being the interface first (looks like an OS X bug in that the inet6 specification of the gif0 interface is missing from the route table otherwise), only adding the explicit IP address route afterwards. So I think something like below would be a succinct summary of the workaround:
sudo ifconfig gif0 tunnel 99.124.xxx.xxx 12.83.49.81
sudo ifconfig gif0 inet6 2602:306:37cY:YYY0:: prefixlen 60
sudo route add -inet6 default -interface gif0
sudo route add -inet6 2000:: -prefixlen 3 2602:306:36cY:YYY0::
| |
|
