It's been more than the few weeks since last post Any good news yet?
Any IPv6 on Gigabit Fiber news?
Internet access discussion, including Fusion, IP Broadband, and Gigabit Fiber!
41 posts
Page 3 of 5
Bump. Native IPv6 isn't rocket science.
No, but it could be a huge capital investment, not to mention disruptive to existing service. Oh, and while it may not be rocket science, it is a security issue for subscribers -- your firewall may be nicely setup to defend against most IPv4 attacks, but is your IPv6 config anything more than pass-through?jjmacleod wrote:Bump. Native IPv6 isn't rocket science.
But Dane has been extremely circumspect on biz-ops details, so all we're left with is speculation. I have a bunch of wild theories, but they are nothing more than that.
Anyone got any form of ipv6 working so far? I didn't get lucky trying the 6rd one which is about 2 years behind.
It is half-working on my Sonic fiber. That is, I can go out on IPv6 just fine, but I cannot come in. For example, going to a VM I have looks like this:
# traceroute6 -n 2600:f03c:91ff:fe37:1c9f
traceroute to 2600:f03c:91ff:fe37:1c9f (2600:f03c:91ff:fe37:1c9f), 30 hops max, 80 byte packets
1 2604:a880:2:d0:ffff:ffff:ffff:fff2 6.725 ms 2604:a880:2:d0:ffff:ffff:ffff:fff1 2.932 ms 2604:a880:2:d0:ffff:ffff:ffff:fff2 6.645 ms
2 2604:a880:ffff:8::1:12 2.925 ms 2604:a880:ffff:8::1:18 2.902 ms 2604:a880:ffff:8::1:1e 2.865 ms
3 2604:a880:ffff:8::1:e 2.833 ms 2604:a880:ffff:8::1:a 2.826 ms 2604:a880:ffff:8::1:c 2.789 ms
4 2604:a880:ffff:12::15 4.138 ms 2604:a880:ffff:12::11 4.170 ms 4.131 ms
5 2001:504:0:1:0:61 4.044 ms 4.023 ms 4.003 ms
6 26003333:4::2 4.303 ms 2.478 ms 2.454 ms
7 2600:f03c:91ff:fe37:1c9f 2.419 ms 2.406 ms 2.390 ms
#
But going from the VM to me stops one hop before it gets to my house:
# traceroute6 -n 260087f1:410::5
traceroute to 260087f1:410::5 (260087f1:410::5) from 2600:f03c:91ff:fe37:1c9f, 30 hops max, 24 byte packets
1 2600:8678:acff:fe0d:a641 0.972 ms 0.824 ms 0.849 ms
2 26003333:4::1 3.87 ms 0.491 ms 1.434 ms
3 2001:5a0500::a1 0.88 ms 1.187 ms 1.068 ms
4 20011fff:415:192:205:37:69 5.293 ms 3.878 ms 4.061 ms
5 2001ff:ffff:12:122:114:6 6.049 ms 7.874 ms 8.009 ms
6 2001ff:ffff:12:122:158:25 7.257 ms 7.781 ms 8.043 ms
7 2001ff:e0a4:12:83:47:138 6.543 ms 6.168 ms 6.141 ms
8 2001:506:6000:112:76:229:61:29 9.809 ms 7.261 ms 17.829 ms
9 * * *
10 * * *^C
#
Sonic tech support told me to post this here because it is monitored by Sonic's engineers, so I hope this is helpful.
# traceroute6 -n 2600:f03c:91ff:fe37:1c9f
traceroute to 2600:f03c:91ff:fe37:1c9f (2600:f03c:91ff:fe37:1c9f), 30 hops max, 80 byte packets
1 2604:a880:2:d0:ffff:ffff:ffff:fff2 6.725 ms 2604:a880:2:d0:ffff:ffff:ffff:fff1 2.932 ms 2604:a880:2:d0:ffff:ffff:ffff:fff2 6.645 ms
2 2604:a880:ffff:8::1:12 2.925 ms 2604:a880:ffff:8::1:18 2.902 ms 2604:a880:ffff:8::1:1e 2.865 ms
3 2604:a880:ffff:8::1:e 2.833 ms 2604:a880:ffff:8::1:a 2.826 ms 2604:a880:ffff:8::1:c 2.789 ms
4 2604:a880:ffff:12::15 4.138 ms 2604:a880:ffff:12::11 4.170 ms 4.131 ms
5 2001:504:0:1:0:61 4.044 ms 4.023 ms 4.003 ms
6 26003333:4::2 4.303 ms 2.478 ms 2.454 ms
7 2600:f03c:91ff:fe37:1c9f 2.419 ms 2.406 ms 2.390 ms
#
But going from the VM to me stops one hop before it gets to my house:
# traceroute6 -n 260087f1:410::5
traceroute to 260087f1:410::5 (260087f1:410::5) from 2600:f03c:91ff:fe37:1c9f, 30 hops max, 24 byte packets
1 2600:8678:acff:fe0d:a641 0.972 ms 0.824 ms 0.849 ms
2 26003333:4::1 3.87 ms 0.491 ms 1.434 ms
3 2001:5a0500::a1 0.88 ms 1.187 ms 1.068 ms
4 20011fff:415:192:205:37:69 5.293 ms 3.878 ms 4.061 ms
5 2001ff:ffff:12:122:114:6 6.049 ms 7.874 ms 8.009 ms
6 2001ff:ffff:12:122:158:25 7.257 ms 7.781 ms 8.043 ms
7 2001ff:e0a4:12:83:47:138 6.543 ms 6.168 ms 6.141 ms
8 2001:506:6000:112:76:229:61:29 9.809 ms 7.261 ms 17.829 ms
9 * * *
10 * * *^C
#
Sonic tech support told me to post this here because it is monitored by Sonic's engineers, so I hope this is helpful.
Is this using the 6rd tunnel?properh wrote:It is half-working on my Sonic fiber. That is, I can go out on IPv6 just fine, but I cannot come in.
No, this is using the native IP that is coming on the fiber.
This seems to be an AT&T IP address, however. I guess you don't have the "native" Sonic fiber?
I'd bet on that. I have Sonic fiber over ATT and it supports IPV6 just fine.julianoster wrote:This seems to be an AT&T IP address, however. I guess you don't have the "native" Sonic fiber?
Any info on this in San Francisco?
41 posts
Page 3 of 5
Who is online
In total there are 161 users online :: 2 registered, 0 hidden and 159 guests (based on users active over the past 5 minutes)
Most users ever online was 999 on Mon May 10, 2021 1:02 am
Users browsing this forum: Google [Bot], Majestic-12 [Bot] and 159 guests
Most users ever online was 999 on Mon May 10, 2021 1:02 am
Users browsing this forum: Google [Bot], Majestic-12 [Bot] and 159 guests