1 edit | Sprint Mobile Broadband Native IP6 A few days ago, I was trying to figure out if my Sprint connection would give me an IP6 address. After a while, I got irritated with not even being able to add IPv6 protocol to a dial-up connection in XP. Today I finally took the time to install the Sprint software on my laptop running Windows Vista Ultimate. Dialed the connection and got full IP6 connectivity.
Pretty damn neat if you ask me. 
C:\Users\Craig>tracert -6 sprintv6.net
Tracing route to sprintv6.net [2001:440:1239:4::2]
over a maximum of 30 hops:
1 * * * Request timed out.
2 160 ms 153 ms 152 ms sl-bb1v6-rly-t-1005.sprintv6.net [2001:440:1239:1010::1]
3 168 ms 169 ms 162 ms sl-bb1v6-nyc-t-1000.sprintv6.net [2001:440:1239:1001::2]
4 169 ms 169 ms 167 ms sl-s1v6-nyc-t-1004.sprintv6.net [2001:440:1239:100e::2]
5 163 ms 163 ms 172 ms www.sprintv6.net [2001:440:1239:4::2]
Trace complete.
--
Sprint Mobile Broadband PX-500 | Windows XP MCE SP2 | Mobile AMD Athlon 64 4000+ | 1.5GB RAM | ATI Mobile Radeon X600 128MB | 120GB HDD |
|
 visitor
join:2001-07-26
Manchester, CT | Very slick! Are those typical ping times for ipv4 traceroutes from the mobile service as well?
--
One minute... and Clarkson still sux! |
|
| With pretty much any other server, my latency with IPv6 is much higher. It might be a 180ms round-trip with IP4, but 300ms with IP6. Not sure why..
Pinging www.sprintv6.net [208.11.232.29] with 32 bytes of
Reply from 208.11.232.29: bytes=32 time=136ms TTL=239
Reply from 208.11.232.29: bytes=32 time=157ms TTL=239
Reply from 208.11.232.29: bytes=32 time=142ms TTL=239
Reply from 208.11.232.29: bytes=32 time=139ms TTL=239
Ping statistics for 208.11.232.29:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 136ms, Maximum = 157ms, Average = 143ms
--
Sprint Mobile Broadband PX-500 | Windows XP MCE SP2 | Mobile AMD Athlon 64 4000+ | 1.5GB RAM | ATI Mobile Radeon X600 128MB | 120GB HDD |
|
visitor
join:2001-07-26
Manchester, CT | reply to CMoore2004
Once the IPv6 packets leave sprint who knows what they do. They probably traverse some tunnels or bounce all over before hitting their destination.
Nice to see some an ISP actually roll this out! I may have to look into getting a sprint mobile card.
--
One minute... and Clarkson still sux! |
|
| It appears I was either wrong or something has changed... but all I know is right now the IP6 is using 6to4. |
|
visitor
join:2001-07-26
Manchester, CT | Did the traceroute change? What does it look like on 6to4?
--
One minute... and Clarkson still sux! |
|
