@bplein

No, missing or bad RAs will cause clients to lose the prefix, leaving them only with link local addresses. I just checked my network and see RAs every minute or so. Examining the RA may give you a clue to the problem.

@stephenw10 Yes, I decided to just nuke this tread. Not sure how to delete the whole thread but I don't have time to work on this right now.

Thanks for the suggestion.

maybe "Get IPv6 through IPv4"

@Bob-Dig Did some more testing and the problem was probably an interface problem with hyper-v, everything is good now.

FINALLY, success!

After retrying what should have worked the first time, but didn't, I can report I have a /56 and proper delegations to the different segments.

The problem was the ISP, even after a modem reboot, would be inconsistent issuing IPv6 configs. It was 24 hours of tweaking and rebooting.

Thanks for the advice, it did help to narrow down the options.

@pwood999 said in BT Ultrafast IPv6 not working through PfSense:

no easy way to talk to somebody that actually understands !!

That has nothing to do with the current situation! 😉

@Gilera said in Issues with IPv6 PD over PPPoE IPv4:

Learning everyday about ipv6........@JKnott, why do i only get a link local ipv6 address on the WAN? I do not have that option selected.

You do in that screen capture you posted. That's why I mentioned it.

So I finished my testing somewhat successful.
I divided that one and only /64 Prefix from my pesky ISP into some /80s. All my PCs, physical and virtual (Windows 10, Ubuntu Server 18.04) worked fine with that /80s, tested from inside and outside.
My older Asus-Router, configured as an AP, my Android10-Phone, connected to that AP, and my Dell MuFu-Printer, connected via Ethernet, stayed on IPv4 only.
Not the worst outcome I think.
So it is doable, but not for every device.

NPt with that ULA seemed to work also for one interface, for one other it wasn't at the time of testing, so I skiped this test, to later find out, that there was this bad static-route... So my conclusion, although not thoroughly tested, it would be working with ULA and NPt the same as with direct public IPv6 Prefixes. 👍

@Napsterbater im getting a /56 subnet. That shouldn't be the problem.

@JKnott No. I meant my ISP-WAN-IPv6-Addresse, which is more or less dynamic and I find the support for something like that in pfSense not as good as it could be and I am rumbling about that here from time to time...😉

Now I got all those IP-Addresses from HE and all those PTR possibilities but not enough machines for it to use. All servers need there own machine to fully take advantage of PTR is what I meant.

@Cathal1201 said in IPv6 Policy Routing and OpenVPN:

Delete for testing the source and test it. When it works, "HOUSEVLAN net" delivers the wrong IPv6 Net.

What do you mean?

Configure "*" as Source and not "HOUSEVLAN net", test it. If it works, Problem is within "HOUSEVLAN Net". If not, rewind it back to "HOUSEVLAN net".

Link Local are often use to route, but that is not that clear to me as I could explain it to you.

Try this first:
Ok, think about the Gateway. Did it know, where the network of your desktop is? You reach Opt1 because pfsense is your default gateway. You reach OPT1_VPNV6 from OPT1 because its the same network. You reach OPT1_VPNV6 from desktop because your default gateway knows the OPT1_VPNV6 Network, BUT OPT1_VPNV6 don't know about the Network of your desktop. The answer is send to gateways default gateway. This is often the problem with IPv4 and I guess it is IPv6 too.

@Derelict Thanks for quickly pointing out my error.

I reconfigured the DHCPv6 server address range as suggested. So far it seems to be more reliable at getting an IPv6 address from the cable modem after a reboot of pfSense, but only experience over a number of weeks will tell for sure.

I have noticed that pfSense boots up and receives an IPv4 address immediately. The IPv6 addresses for the WAN, LAN, and devices on the LAN take a good 3 - 4 minutes to appear. Which has confused me at times, but I do think this is the correct configuration.

I saw the prefix delegation option does not have a "not used" selection in the drop down menu, so there will always be a number there, in my case I left it at /48. I think without a prefix delegation range specified, it is unused.

b1622cdd-5328-4f27-9e53-93e16e300b63-image.png

@JKnott

Further on this, the base prefix and prefix length are provided as part of the DHCPv6-PD process. The prefix ID is provided on the LAN config page. Why can the two not be used, if necessary, to automatically provide the first prefix?

Hi

Just wanted to add also saw this issue during an upgrade from 2.4.4_3 to 2.4.5, I had previously unchecked "Register DHCP leases in the DNS Resolver" due to loads of restarts on the DNS Resolver service. On upgrading to 2.4.5 (I think unrelated to the upgrade, it was just because of the restart) I found an issue with my VoIP phone over IPv6 failing to register. Various trouble shooting later I ended up testing from a Windows PC using NSLOOKUP which picked up the DNS server on the IPv6 address but it was timing out and returning no results.

A Goggle brought me here, so as per OP I restarted the DNS Resolver and NSLOOKUP started returning addresses, and low and behold the VoIP phone registered back up. So definitely a bug somewhere.

Regards

Phil

Just wanted to give an update on the issue.

I wrote to my ISP explaining the problem. I didn't get an answer, but the following day, my IPv6 connection got miraculously rock solid (since 5 days now), whereas I hadn't touched the system.

A big thanks to all the people on this forum who helped trying to find a solution 👍

@riften Yep, I get the same behavior from the Arris BGW210-700.

@JKnott said in Getting upstream delegating router to create a route to pfSense gateway:

@AaronL

That is surprising, given that Comcast has long promoted IPv6. However, what you can do is capture the DHCPv6 packets. Set up Packet Capture to capture ICMPv6 on the WAN port. Then disconnect/reconnect the WAN cable. This should result in capturing the DHCPv6 packets. Download the capture and open it with Wireshark. The advertise and reply XID lines should show the assigned prefix.

Yeah, that is the first thing I did. The DHCPv6 conversation works great, and goes exactly how it should. (That's not entirely true; it gives out T1 and T2 values that dhcp6cd thinks are 'too short,' but as far as I can tell, that's not causing any actual trouble.)

The problem is that a route matching the assigned prefix doesn't seem to get added on the cablemodem, which I can also see clearly in Wireshark from the neighbor discovery packets.

Because Comcast has had a reputation for making an effort on IPv6, I want to push on this as hard as I can: this is really something that should be right, and from an engineering standpoint, is probably pretty straightforward to fix.