Any IPv6 on Gigabit Fiber news?

Internet access discussion, including Fusion, IP Broadband, and Gigabit Fiber!
32 posts Page 3 of 4
by FBIPV6 » Mon Feb 24, 2020 8:11 am
It's been more than the few weeks since last post Any good news yet?
by jjmacleod » Thu Mar 12, 2020 6:46 pm
Bump. Native IPv6 isn't rocket science.
by ewhac » Fri Mar 13, 2020 12:36 pm
jjmacleod wrote:
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?

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.
by enig123 » Sat Mar 21, 2020 4:19 pm
Anyone got any form of ipv6 working so far? I didn't get lucky trying the 6rd one which is about 2 years behind.
by properh » Mon Mar 23, 2020 3:26 pm
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:3c01::f03c:91ff:fe37:1c9f
traceroute to 2600:3c01::f03c:91ff:fe37:1c9f (2600:3c01::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:6:3949:1 4.044 ms 4.023 ms 4.003 ms
6 2600:3c01:3333:4::2 4.303 ms 2.478 ms 2.454 ms
7 2600:3c01::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 2600:1700:87f1:410::5
traceroute to 2600:1700:87f1:410::5 (2600:1700:87f1:410::5) from 2600:3c01::f03c:91ff:fe37:1c9f, 30 hops max, 24 byte packets
1 2600:3c01::8678:acff:fe0d:a641 0.972 ms 0.824 ms 0.849 ms
2 2600:3c01:3333:4::1 3.87 ms 0.491 ms 1.434 ms
3 2001:5a0:1000:500::a1 0.88 ms 1.187 ms 1.068 ms
4 2001:1890:1fff:415:192:205:37:69 5.293 ms 3.878 ms 4.061 ms
5 2001:1890:ff:ffff:12:122:114:6 6.049 ms 7.874 ms 8.009 ms
6 2001:1890:ff:ffff:12:122:158:25 7.257 ms 7.781 ms 8.043 ms
7 2001:1890:ff: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.
by parker_day » Mon Mar 23, 2020 3:59 pm
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.


Is this using the 6rd tunnel?
by properh » Tue Mar 24, 2020 8:36 am
No, this is using the native IP that is coming on the fiber.
by julianoster » Thu Mar 26, 2020 4:43 pm
This seems to be an AT&T IP address, however. I guess you don't have the "native" Sonic fiber?
by bobrk » Thu Apr 02, 2020 6:52 pm
julianoster wrote:
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.
by dubbly » Sun Apr 12, 2020 2:53 pm
Any info on this in San Francisco?
32 posts Page 3 of 4

Who is online

In total there are 16 users online :: 2 registered, 0 hidden and 14 guests (based on users active over the past 5 minutes)
Most users ever online was 487 on Tue May 05, 2020 2:07 pm

Users browsing this forum: Bing [Bot], Google [Bot] and 14 guests