Clients no not have IPv6

Ok so I plugged my laptop directly to the ONT with an ethernet cable.
Here is the network info it got
Untitled-ipv6

Also I ran the ipv6 test:

Pinging the aws media server worked, although it did through ipv4:

 ping media-share-2.s3.dualstack.us-west-1.amazonaws.com

Pinging s3.dualstack.us-west-1.amazonaws.com [52.219.117.128] with 32 bytes of data:
Reply from 52.219.117.128: bytes=32 time=69ms TTL=242
Reply from 52.219.117.128: bytes=32 time=70ms TTL=242
Reply from 52.219.117.128: bytes=32 time=67ms TTL=242

Ping statistics for 52.219.117.128:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 67ms, Maximum = 70ms, Average = 68ms

So based on this, verizon doesn't really offer ipv6 in fios? Should I disable ipv6 in my router so I can have access to those services trying to reach servers with ipv6?

Verizon FiOS does offer IPv6 in many markets, as of the first half of 2023. I'm not sure which one you're in, but there's a long thread at DSLreports about it:

Also this one about configuring non-Verizon routers:

Your screen shot of a WAN6 interface shows that it did get a prefix delegated (IPv6-PD shows).
Do note that Verizon does not assign an IPv6 address directly to connected routers, so if you want the WAN interface to have its own IPv6 you'll have to configure that. Hints in this post and the subsequent replies: https://www.dslreports.com/forum/r33468239-

1 Like

Thanks for the links. I'm in Northern VA, from what I read most of the area has IPv6. But how can I know for sure if I have IPv6 or not since Verizon is not helping at all? After plugging my laptop to the ONT and not getting IPv6 connectivity, I suppose this is a sign that trying to configure my router is pointless?

If you install tcpdump on the router, you can see any IPv6 router advertisements and any DHCPv6 traffic. I don’t use VLANs, so I’m not certain if you need eth0 or eth0.2 in the command line below.

opkg update; opkg install tcpdump
tcpdump -v -n -i eth0.2 '(icmp6 and ip6[40] == 134) or (udp and port 547)'

While tcpdump is running in one SSH session, run ifup wan6 in another SSH session. You should see UDP traffic between ports 547 and 546.

If IPv6 is available from FiOS, you'll see router advertisements about every 5 minutes, that's the part with (icmp6 and ip6[40] == 134) in the tcpdump filter

1 Like

Should I enable back ipv6 in the lan interface and the wan6 interface to observe this traffic in tcpdump?

Actually that looks like what would be on the OpenWrt router. Does the client PC have an IP6 address (GUA, i.e. starting with 2 or 3 and in the same /64 as lan)?

You can comment out ula_prefix in the router network config as there is no need for ULAs here.

Then try some traceroute6 tests from the router and from the PC. If it makes a few hops into the ISP and then gets lost it's almost certainly an ISP problem.

It does, see Clients no not have IPv6 - #6 by bomberb17
Very confusing...

I would leave IPv6 enabled to keep digging with tcpdump as suggested.
At the same time you can disable AAAA name resolution in dnsmasq settings to prevent clients from contacting IPv6 addresses.