The Asus RT-N56U (alternative to Actiontec router) - Canadian TV, Computing and Home Theatre Forums

file · 2012-03-23, 02:41 PM

Just threw a firmware build onto my business router. Thought I would share this:

C:\Users\jcolp>tracert -6 ipv6.google.com

Tracing route to ipv6.l.google.com [2001:4860:800a::63]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 2001:470:8:348::
2 36 ms 34 ms 36 ms jcolp-1.tunnel.tserv13.ash1.ipv6.he.net [2001:47
0:7:348::1]
3 30 ms 36 ms 28 ms gige-g4-12.core1.ash1.he.net [2001:470:0:90::1]

4 32 ms 32 ms 29 ms 2001:4860:1:1:0:1b1b:0:d
5 32 ms 30 ms 32 ms 2001:4860::1:0:9ff
6 46 ms 46 ms 47 ms 2001:4860::1:0:5db
7 48 ms 47 ms 46 ms 2001:4860::8:0:2f04
8 48 ms 46 ms 47 ms 2001:4860::2:0:ba
9 52 ms 52 ms 54 ms 2001:4860:0:1::10f
10 46 ms 50 ms 49 ms yx-in-x63.1e100.net [2001:4860:800a::63]

Trace complete.

Some final testing and web GUI tweaking to do, but it seems to work. Turn it on, copy/paste 3 different things from the tunnelbroker.net tunnel page, reboot, and boom. IPv6!

The really cool thing is that the tunnelbroker server in Virginia is *very* close. About 20-25ms away so the added latency of going over IPv6 is actually very minimal and in some cases is less than going over IPv4 to the same place.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

2012-03-23, 02:41 PM	#11
file Join Date: Nov 2010 Location: Riverview, NB Posts: 761	Just threw a firmware build onto my business router. Thought I would share this: C:\Users\jcolp>tracert -6 ipv6.google.com Tracing route to ipv6.l.google.com [2001:4860:800a::63] over a maximum of 30 hops: 1 3 ms 3 ms 3 ms 2001:470:8:348:: 2 36 ms 34 ms 36 ms jcolp-1.tunnel.tserv13.ash1.ipv6.he.net [2001:47 0:7:348::1] 3 30 ms 36 ms 28 ms gige-g4-12.core1.ash1.he.net [2001:470:0:90::1] 4 32 ms 32 ms 29 ms 2001:4860:1:1:0:1b1b:0:d 5 32 ms 30 ms 32 ms 2001:4860::1:0:9ff 6 46 ms 46 ms 47 ms 2001:4860::1:0:5db 7 48 ms 47 ms 46 ms 2001:4860::8:0:2f04 8 48 ms 46 ms 47 ms 2001:4860::2:0:ba 9 52 ms 52 ms 54 ms 2001:4860:0:1::10f 10 46 ms 50 ms 49 ms yx-in-x63.1e100.net [2001:4860:800a::63] Trace complete. Some final testing and web GUI tweaking to do, but it seems to work. Turn it on, copy/paste 3 different things from the tunnelbroker.net tunnel page, reboot, and boom. IPv6! The really cool thing is that the tunnelbroker server in Virginia is very close. About 20-25ms away so the added latency of going over IPv6 is actually very minimal and in some cases is less than going over IPv4 to the same place.