5G Home IPV6 not routing to google or cloudflare in Los Angeles

kberg

Restarted the 5G CPE a couple of time and got different ipv6 address with same result.
root@gw:~# traceroute -n www.google.com
traceroute to www.google.com (2607:f8b0:4007:809::2004), 30 hops max, 72 byte packets
1 2600:1012:a000:26d0:0:10:85ee:4e40 8.550 ms 7.015 ms 5.807 ms
2 * * *
3 * * *
4 2001:4888:64:200e:620:25:0:2 7.671 ms 10.518 ms 9.802 ms
5 * * *
6 2001:4888:6f:2d92:620:1:0:1 19.076 ms * 12.250 ms
7 2001:4888:64:1020:620:1:0:11 13.434 ms * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

kberg

I am running that traceroute from my firewall, so the next hop is actually a verizon network device's ipv6 address, which is why it's 9ms away. My ipv6 address changes everytime i restart networking on the firewall, so I'm not too worried about sharing their router's ipv6 address.
The verizon cell tower is right in front of my house ( ~40ft ), ipv4 appears to behave properly, I get a ~2Gbps/200Mbps according to fast.com. I don't use their router so i don't have access to signal stength.
IPV6 has been working for months, this just started happening yesterday out of the blue. ( if you ignore the fact that verizon doesn't provide a /56 like they do for their FIOS, I can only get a /64 which requires me to do NAT6 and defeat the purpose of IPV6's extended address range, but that's a different problem )
After many more reboot of their LV65. I even factory reset it last night, without success.
It started working again this afternoon, I can now ping and access www.google.com via ipv6.
Not sure if they A. fixed the issue or B. just got lucky and got a routable ipv6 range.

I expected the traceroute to reach google's ipv6 address, not get lost verizon's network:
traceroute to www.google.com (2607:f8b0:4007:80a::2004), 30 hops max, 72 byte packets
1 2600:1012::::::x (2600:1012::::::x) 8.586 ms
2 *
3 *
4 2001:4888:64:200e:620:25:0:2 (2001:4888:64:200e:620:25:0:2) 10.269 ms
5 *
6 2001:4888:6f:2d92:620:1:0:1 (2001:4888:6f:2d92:620:1:0:1) 11.494 ms
7 *
8 *
9 *
10 *
11 2001:4860:0:1::20d4 (2001:4860:0:1::20d4) 9.931 ms
12 lax02s22-in-x04.1e100.net (2607:f8b0:4007:80a::2004) 11.401 ms

Also https://test-ipv6.com/ is now all happy and green, I guess this can be marked as resolved.