No IPv6 after upgrade to 23.01

maverickws

@jimp I really appreciate the report, thank you. You guys address the issue description way better than me.

mhillmann

@jimp We have another twist to the already acknowledged regression: our ISP refuses to delegate a prefix shorter than a /64, but grants as many(?) /64 prefix delegations as we request as long as the IA-PD identifier is unique. This gives roughly the same result as requesting a shorter PD and splitting it up on the track interface, but regrettably there is no way to inform unique IAID´s from the IA-PD request to individual track interfaces in order to create an association between the granted PD and the local interfaces onto which these PD´s should be assigned. The implied logic in pfSense is that we only get one PD of a certain length and associate it to the routing interface via its name, not the IAID. It might be useful to consider this use case too, as I have read somewhere that even ATT has this use policy.
The following should be possible and not restricted/blocked by the pfSense configuration (0 and 1 are the IAID's):
interface ix2 {
send ia-na 0;
send ia-pd 0;
send ia-pd 1;
script "/var/etc/dhcp6c_opt13_script.sh";
};
id-assoc na 0 { };
id-assoc pd 0 {
prefix-interface ix2.666 {
sla-id 0;
sla-len 0;
};
};
id-assoc pd 1 {
prefix-interface ix2.667 {
sla-id 0;
sla-len 0;
};
};

jimp

That is completely unrelated to the problem here and wouldn't have changed in 23.01. It belongs in a separate thread.

mhillmann

@jimp sorry, my mistake. I´ve started a new thread already.

maverickws

@jimp said in No IPv6 after upgrade to 23.01:

https://redmine.pfsense.org/issues/14072

I was thinking as a solution, what about having an option that when selected executes the script even if the ISP doesn't have a correct config, and when unselected has the supposed to be correct behaviour? Would that work?

mhillmann

@maverickws I believe this would be equivalent to always run the script, as it uses the same script for both flags already.

maverickws

@mhillmann yeah but I mean if we assume the current behaviour is the correct behaviour and by default should be so, it would make sense, imo, the option to override the default behaviour and then run the script regardless. (so when that option is selected, always run the script)

mhillmann

@maverickws I agree, this may be the best option.

ddbnj

@maverickws said in No IPv6 after upgrade to 23.01:

https://forum.netgate.com/post/1088842

Well, it took me 22 days to realize that ipv6 is no longer working since upgrading.

It seems that a problem has been identified. Has a workaround been proposed? All of my google home devices (which use SLAAC) are no longer working reliably. If I turn off IPV6 on that VLAN, it works.

Thanks,

Devan

jpwoodbu

Take with a grain of salt... I was suffering from this issue and enabled the DHCPv6 server on my LAN interface and that seemed to fix it.

I thought I had the DHCPv6 server enabled on my LAN interface before upgrading to 23.01, but I found it not enabled when troubleshooting this issue.

Just thought I would share in case this helps anyone.

ddbnj

@jpwoodbu
Thanks.

I checked on DSL reports and a few NJ users are reporting IPv6 outages. I just removed all traces of IPv6 from pfsense and called it a day. I'll try again in a year. IPv6 really didn't offer any noticeable benefits but introduced much more instability, mostly from Verizon.

compuguy

@ddbnj Its not just NJ FiOS users. I'm in NoVA and IPv6 isn't working for me either.

nighthawk1967

I will say it's not your Isp because i can use the ips router and ipv6 works .Pfsense version 22 works fine just can't install packages because the package manager is out of date ,So is there going to going to be fix any time this year ?
The no help is not good for anyone
The ipv6 problem is not funny !!

compuguy

@nighthawk1967 I disagree with that. I have a Mikrotik on another FiOS network that should support IPv6. I'm pretty sure that's doesn't have ipv6 working either...

MikeV7896

@compuguy said in No IPv6 after upgrade to 23.01:

@ddbnj Its not just NJ FiOS users. I'm in NoVA and IPv6 isn't working for me either.

Yep... after some overnight maintenance early Tuesday morning, I've lost my IPv6 connectivity in Northern VA. Clearly Verizon has changed something, but it sounds like pfSense may need to change something also... looking forward to whenever the patch is available for the fix!!

compuguy

@compuguy said in No IPv6 after upgrade to 23.01:

@nighthawk1967 ~~I disagree with that. I have a Mikrotik on another FiOS network that should support IPv6. I'm pretty sure that's doesn't have ipv6 working either...~~

Update: Looks like the Mikrotik router is having no issues and is able to pull a IPv6 prefix from Verizon. This seems to be a PFsense 23.01 bug/issue only....

Gertjan

@compuguy said in No IPv6 after upgrade to 23.01:

This seems to be a PFsense 23.01 bug/issue only...

My setup / background :
Before January 2023, my ISP - my Internet connection was just IPv4. I was a static IP, so that's fine to me.
But no IPv6what so ever.
So, around 2014 ( ? ) I decided to create a he.net tunnelbroker account, as they give a free /48 for "live" with local access points all over the planet.
I tend to think these guys somewhat created the IPv6 RFCs.

January 2023 : fiber was installed. That was the end of 24 Mbits/sec VDSL : here comes 800+ Mbits up/down.
And a new fiber ONT integrated ISP router.
That didn't route the '6in4' protocol, so that was the end of my he.net free IPv6 access.
The positive side of this was that their local POP in paris, for me, would not route that kind of bandwith to me, so their Ipv6 would cripple my overall Internet access.
And the new USP box offers IPv6 for it's LAN devices.
And even better : it hands over /64 prefixs (delegations) to router type LAN (ISP router point of view) devices, like pfSense.

And yes : my pfSense DHCP6 client does receive a (one) /64 for my pfSense LAN.
Not really perfect yet, as I have several LAN using IPv6 and my ISP router is buggy : it can gve more prefixes (64) but it then fails to route over IPv6. So only one it will be.

I had some insight in what actually happens between my ISP router and pfSense with some severe tcpdump sessions.

Then some one one a french forum ( ! ) pointed me to Multiple IPv6 Prefix Delegation over AT&T Residential Gateway for pfSense 2.4.5 so I crafted my own dhcp6 client config file, put the dhcp6 client into debug mode, and saw what happened written on the screen (logs).

Ok, nice, the router is somewhat buggy. The ISP made huge progress : a /56 for every user, and prefixes are handed over to devices that asks for one, or more of them.
But : not perfect yet, for me.

Of course, in France, about 16 million users use the same ISP (Orange) and 10 million have fiber. And I'm the only one using multiple IPv6 LANs ..... ?

Now, to join the subject of this thread : our ISPs are not perfect yet.
But I use 23.01 on a 4100, and IPv6 works for me, Phones, PC's, printers etc do get a routable IPv6 from pfSense. I'm not using the tracker mode, but the DHCP6 server with static IPv6.

jasonreg

@maverickws said in No IPv6 after upgrade to 23.01:

@steveits I'm attributed a /56 prefix;

WAN configured as DHCP6
LAN, IoT and DOM (all local networks, IoT and DOM are VLANS) configured as tracking WAN interface for IPv6

Each interface gets a /64 prefix delegation size.

How did you get all the local networks tracking the LAN? I can get one network doing this but when I try to setup another network/VLAN I get an error that tracking is already established and in use (or something along these lines).

Bob.Dig

@jasonreg You have to use another prefix ID. And they don't track LAN but your WAN.

Gertjan

@jasonreg

This :

doesn't mean you will get more then one prefix.
--- I think ---

With that (image) setting, I get 1 prefix, so I can select one (from 0 to 0) as an interface to track (on one LAN interface).

I wanted to have several prefixes, so I used the forum thread sited above as a guideline.

I created this file /root/att-rg-dhcpv6-pd.conf :

interface ix3 {
        send ia-na 0;
        send ia-pd 0;
        send ia-pd 1;
        send ia-pd 2;
        send ia-pd 3;
        send ia-pd 4;
        send ia-pd 5;
        send ia-pd 6;
        send ia-pd 7;
        request domain-name-servers;
        request domain-name;
        script "/var/etc/dhcp6c_wan_script.sh";
};
id-assoc na 0 { };
id-assoc pd 0 {
        prefix-interface igc0 {
                sla-id 0;
                sla-len 0;
        };
};
id-assoc pd 1 {
        prefix-interface igc2 {
                sla-id 0;
                sla-len 0;
        };
};
id-assoc pd 2 { };
id-assoc pd 3 { };
id-assoc pd 4 { };
id-assoc pd 5 { };
id-assoc pd 6 { };
id-assoc pd 7 { };

where ix3 is my WAN interface.
igc0 is my LAN interface
igc1 is my second LAN interface

I've used this file like this :

A then, looking at thedhcp6client log lines, the magic happend :
I saw 2 /64 prefixes handed over buy my ISP upstream router, and could use Tracking on two LAN interfaces, the first had the index 0 and the other the index 1.
( and then things still failed for me, but that's another story )

Btw : I do not pretend that I fully understand what the config file does.