I had to log in to my FiOS provided CPE (Verizon Quantum Gateway) and enable IPv6. It’s off by default. This is what I see in Reston, VA: Ethernet adapter Ethernet: Connection-specific DNS Suffix . : fios-router.home Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM Physical Address. . . . . . . . . : 6C-C2-17-EE-EE-6D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2600:4040:2b48:ce00:25e4:9527:2f2b:e571(Preferred) Temporary IPv6 Address. . . . . . : 2600:4040:2b48:ce00:3411:b0a4:e9e7:e28f(Preferred) Link-local IPv6 Address . . . . . : fe80::25e4:9527:2f2b:e571%18(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.2.146(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, June 16, 2022 8:48:52 AM Lease Expires . . . . . . . . . . : Friday, June 17, 2022 8:48:51 AM Default Gateway . . . . . . . . . : fe80::4a5d:36ff:fecc:fe42%18 192.168.2.254 DHCP Server . . . . . . . . . . . : 192.168.2.254 DHCPv6 IAID . . . . . . . . . . . : 57459223 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-20-9D-C9-6C-C2-17-EE-EE-6D DNS Servers . . . . . . . . . . . : 2600:4040:2b48:ce00::1 192.168.2.254 2600:4040:2b48:ce00::1 NetBIOS over Tcpip. . . . . . . . : Enabled Connection-specific DNS Suffix Search List : fios-router.home My Netgear router/WAP is set to autodetect IPv6 and sees it as passthrough. IPv4 is double NAT, but I have the v4 interface on the Netgear set to a static IP and the Verizon router is configured to treat that address as a DMZ and passes all traffic directly to it (theoretically unmolested). I used to have it set to bridge mode for that port so it was only a single NAT, but every time the VZ supplied router rebooted, I’d have to manually go back and fix it, so I compromised and set as a DMZ instead. In the interest of not putting my house directly on the internet without protection, I do have all v6 traffic using the FiOS router’s firewall since I’m not convinced that the Netgear is properly firewalling that traffic due to the mode. Thanks, -- Jamie Bowden Senior Computer Network Technologist II O: +1 703.842.3848 C: +1 703.403.9745 jamie.s.bowden@raytheon.com<mailto:jamie.s.bowden@raytheon.com> jamie.s.bowden@rtx.com<mailto:jamie.s.bowden@rtx.com> Raytheon Intelligence & Space Digital Technology 1100 Wilson Blvd. Suite 2000 Arlington, VA 22209 RTX.com<https://www.rtx.com/> | LinkedIn<https://www.linkedin.com/company/raytheontechnologies> | Twitter<https://twitter.com/raytheontech> | Instagram<https://www.instagram.com/raytheontechnologies> Upcoming PTO: June 22, 2022 July 4-8, 2022 From: NANOG <nanog-bounces+jamie.s.bowden=raytheon.com@nanog.org> On Behalf Of Christopher Morrow Sent: Saturday, June 11, 2022 10:05 PM To: nanog list <nanog@nanog.org> Subject: [External] Fwd: Congrats to AS701 Looks like FIOS customers may be getting ipv6 deployed toward them, finally: ifconfig snippet from local machine: inet6 2600:4040:2001:2200:73d2:6bcc:1e6b:43a1 prefixlen 64 scopeid 0x0<global> inet6 2600:4040:2001:2200:e87:bf36:b6cb:6ce1 prefixlen 64 scopeid 0x0<global> ping attempt: 64 bytes from bh-in-f106.1e100.net<http://bh-in-f106.1e100.net> (2607:f8b0:4004:c09::6a): icmp_seq=1 ttl=59 time=8.71 ms 8ms from mclean, va to ashburn, va isn't wondrous, but at least it's ipv6 (and marginally faster than ipv4) Congrats to the 701 folk for deploying more widely! (note: I don't know exactly when this started, nor how wide it really is, but progress here is welcomed by myself at least :) ) -chris