Fwd: Congrats to AS701

Christopher_Morrow · June 12, 2022, 2:04am

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
inet6 2600:4040:2001:2200:e87:bf36:b6cb:6ce1 prefixlen 64 scopeid 0x0

ping attempt:
64 bytes from 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

Christopher_Morrow · June 12, 2022, 5:55pm

I, for one, am having a hard time finding the proper words to express the joy that I am feeling at this momentous moment!

It’s quite amazing, I think… that it’s taken so long to get to deployment you can actually see on the fios plant
I’d note I can’t see the below on my homestead, but I can at a relative’s (where the ifconfig data is from).

I also can’t tell if the upstream will PD a block to the downstream… and the VZ CPE is ‘not something I want to fiddle with’,
because everytime I have tried at my house I’ve just taken it out behind the woodshed with a maul… and replaced it with
something I CAN configure successfully. (plus… don’t want that TR 069 in my home…)

-chris

Joe_Loiacono1 · June 13, 2022, 2:55pm

FiOS from Maryland (anonymized):

enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.164 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::b104:8f4d:e5b2:e13b prefixlen 64 scopeid 0x20
inet6 2600:4040:b27f:cb00:a9b1:5f59:xxxx:xxxx prefixlen 64 scopeid 0x0
inet6 2600:4040:b27f:cb00:24a8:7b31:xxxx:xxxx prefixlen 64 scopeid 0x0
inet6 2600:4040:b27f:cb00:e1b6:8b83:xxxx:xxxx prefixlen 64 scopeid 0x0
ether d0:67:e5:23:ec:fe txqueuelen 1000 (Ethernet)
RX packets 2518066 bytes 1448982813 (1.4 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2157395 bytes 260073952 (260.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

a@b:~$ ping 2607:f8b0:4004:c09::6a
PING 2607:f8b0:4004:c09::6a(2607:f8b0:4004:c09::6a) 56 data bytes
64 bytes from 2607:f8b0:4004:c09::6a: icmp_seq=1 ttl=59 time=24.0 ms
64 bytes from 2607:f8b0:4004:c09::6a: icmp_seq=2 ttl=59 time=17.6 ms
64 bytes from 2607:f8b0:4004:c09::6a: icmp_seq=3 ttl=59 time=20.4 ms
64 bytes from 2607:f8b0:4004:c09::6a: icmp_seq=4 ttl=59 time=23.4 ms
^C
— 2607:f8b0:4004:c09::6a ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 17.618/21.351/23.983/2.555 ms

Matthew_Huff · June 13, 2022, 3:14pm

Still no IPv6 in Westchester County, NY

Great sign though, maybe NY will get it eventually

Nimrod_Levy · June 13, 2022, 3:18pm

Also, it doesn’t seem to be enabled on ports that have static ipv4

but progress is progress. we’ll take it.

Justin_M_Streiner2 · June 13, 2022, 4:00pm

I might call Verizon and ask about v6 availability as I periodically do. I’ll check if I see anything different on my gear later today. I have a GPON business service with static IPv4 at one location and an older BPON business service with static IPv4 in another location.

Thank you
jms

Christopher_Morrow · June 16, 2022, 1:07am

I might call Verizon and ask about v6 availability as I periodically do. I’ll check if I see anything different on my gear later today. I have a GPON business service with static IPv4 at one location and an older BPON business service with static IPv4 in another location.

As a short and not totally complete update to this problem… A ‘long time listener, first time caller’ sort of person
noted to me off-list that:
“Hey, once upon a time I dealt with hardware/vendor things… and we wouldn’t send ‘RA type’ packets (solicits/etc)
down the customer leg UNLESS they had already sent a RouterSolicitation… on the BNG platform.”

So… I copy/pasta’d some comcast facing config and… low and behold my link sends me a /56 if I ask for one via PD!
for I can’t personally use the v6 (yet) here, but this is super encouraging!

Perhaps this is ‘CPE configuration away’ from working in a bunch more places?

-chris

Dave_Taht · June 16, 2022, 1:54am

I might call Verizon and ask about v6 availability as I periodically do. I'll check if I see anything different on my gear later today. I have a GPON business service with static IPv4 at one location and an older BPON business service with static IPv4 in another location.

As a short and not totally complete update to this problem... A 'long time listener, first time caller' sort of person
noted to me off-list that:
"Hey, once upon a time I dealt with hardware/vendor things... and we wouldn't send 'RA type' packets (solicits/etc)
down the customer leg UNLESS they had already sent a RouterSolicitation... on the BNG platform."

So... I copy/pasta'd some comcast facing config and.. low and behold my link sends me a /56 if I ask for one via PD!
for <reasons that include chris is holding it wrong> I can't personally use the v6 (yet) here, but this is super encouraging!

Perhaps this is 'CPE configuration away' from working in a bunch more places?

Well, in a FIOS location[1] with the most ancient fios provided CPE I
know of (at least 10 years old), connected to a modern day openwrt
router, it's been putting out dhcpv6 solicits with no response for
roughly... 10 years.

It would be great if there was someone to call at FIOS about what gear
will be v6 capable. This router also happens to have my longest
running hurricane electric ipv6 tunnel.

Never did I imagine 10+ years ago that tunnel would still be in operation.

[1] From Dave in my basement – Armed and Dangerous

John_Covici · June 16, 2022, 2:14am

The tech support of Verizon, don't know anything about ipv6. The
business reps have never heard of it, either.

Mailman · June 16, 2022, 1:43pm

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,

John_Von_Essen · June 20, 2022, 6:53pm

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,