Verizon Fios and IPV6, Which Settings Work?
-
@mkomar I think my brother had the same thing last week - he got IPv6 addresses, but no routing. My parents had it happen a few months ago too. (Both are in Montgomery County, MD. I'm a few miles north of them in a different CO area, and it's been working for me for many months, so I'm guessing some of the CO's don't have routing set up properly.)
-
@kohenkatz sounds good. I'm in Culpeper, VA.
-
Hi everyone,
Just adding my 2 cents to this discussion to report that I was able to get IPv6 working with Verizon FIOS out of New York City today (Manhattan, Battery Park City). The settings I used were pretty much the ones that have already been discussed here at length, but it took quite a bit of toiling, turning them off and back on a few times, and even a reboot at one point, before my test VLAN's DHCP6 server started successfully assigning v6 IPs to its clients.
And, even after that, my clients were still unable to route any traffic on that VLAN, they were essentially cut off. So at first I made sure the DNS resolver was properly listening on the VLAN's interface, that no firewall rules were blocking traffic, and finally the change that tipped the balance was setting router mode to Assisted in Router Advertisements.
I think the only other thing I did, that probably deviates from the general guidance here, is setting the DHCP6 DUID to "DUID-LL: Based on Link-layer Address" in System -> Advanced -> Networking -> IPv6 Options, using my WAN's MAC address (with my WAN interface being the one connected directly to the FIOS ONT).
Hope that helps people here still struggling with FIOS and IPv6!
PS: Needless to say, I'm all ears if anyone here more knowledgable on IPv6 than me (just about anyone) has some strong advice against how I set up my connection, thanks!
-
A little extra info I learned today when tweaking my IPv6 settings that might be of interest to this forum.
When trying to get IPv6 working on my LAN interface, I made the cardinal sin of disabling it in an attempt to avoid rebooting the router for the config to take, and of course locked myself out of the GUI. That forced me to reassign interfaces on the console to regain access, which in turn caused me to spend the entire day restoring my configuration to a working state (interface assignments, VLANs, firewall rules, etc.).
That, of course, broke my fledgling IPv6 setup completely, and at some point attempting to restore it (and after checking everything else was configured as expected, e.g. interface assignments, firewall rules, DCHP6 settings, DNS Forwarder, etc.) I enabled the "Advanced Configuration" option for the DHCP6 client on my WAN interface, to make sure the correct Prefix Interface was selected, but without configuring any other advanced option. Well, until I disabled that (and without changing anything else), none of my LAN clients were getting any IPv6 assignments, and I was back almost to square 1; but when I did disable it, in desperation, all my LAN clients immediately got their IPv6 addresses!
Hope that helps at least some desperate, IPv6 neophytes souls such as myself!
-
@jmpalacios said in Verizon Fios and IPV6, Which Settings Work?:
I think the only other thing I did, that probably deviates from the general guidance here, is setting the DHCP6 DUID to "DUID-LL: Based on Link-layer Address" in System -> Advanced -> Networking -> IPv6 Options, using my WAN's MAC address (with my WAN interface being the one connected directly to the FIOS ONT).
I agree, I've had to set this as well, although I think I used DUID-LLT instead. In fact I've found that the DUID needs to be updated for IPv6 every time the WAN interface MAC address changes (for instance by changing the WAN interface to a different network port on the firewall), otherwise no new IPv6 prefix would be assigned.
-
@tman222 Well, if I'm not mistaken, the intention is precisely for the prefix to change as little as possible, hence my use of a fixed identifier.
Or am I misunderstanding the purpose of DUID, and/or the way it should be used?
-
@jmpalacios said in Verizon Fios and IPV6, Which Settings Work?:
Well, if I'm not mistaken, the intention is precisely for the prefix to change as little as possible, hence my use of a fixed identifier
That's my understanding too.
-
@JKnott Well, in that case, using a time-based component would cause it to change every time it's renewed. I can of course see several cases in which that would be desirable, but my use-case is not one of those, hence leaving out the time-based component from the DUID.
-
Just wanted to shout out to all those on this thread. I have IPv6 working over FiOS in NYC now with my pfsense CE 2.6.0 setup. Now to migrate my rules to v6.
-
I recently upgraded to Verizon Fios 2Gbit service and it looks like I lost IPv6 capability in the process. The settings described in this thread had been working fine on the prior 1Gbit service, but with the new service I'm unable to get a IPv6 prefix delegated to me (using the same settings). Enabling debug mode on dhcpv6 I see the solicit (RS) going out, but unfortunately no advertisements (RA) follow. Does anyone with the 2Gbit Fios service have IPv6 working for them? The service is still relatively new so perhaps that capability (IPv6) is not yet enabled and will be made available later on. Thanks in advance.
-
@MikeV7896 Just want to say thank you,followed your settings and it works.
-
M madbrain referenced this topic on
