Setting up IPv6 on PPPPoE, what happened to "Use IPv4 connectivity"

Started by errolt, November 11, 2025, 05:23:38 PM

Previous topic - Next topic
Hi All,

I moved my firewall from PFsense to OPNsense.

In PFsense I got my IPv6 configured. I had to set "Use IPv4 connectivity" under the DHCPv6 setting to get it to work. I don't see that setting in OPNsense, although other forum posts DOES mention the setting. What happened to it and where do I set it now?

As a side note, my WAN connection isn't getting an IPv6 IP, but my LAN network is getting the correct IPv6 setting via Track Interface(ie, LAN is issuing IPv6 from the pool I got from my ISP). But my WAN interface isn't accessible from my public IPv6 IP.


Ok, looks like it is using the wrong gateway?

This forum doesn't allow uploading images...

My WAN interface got these IPv6s:

2c0f:f030:20b:4a:7e5a:1cff:fe72:c831/64
fe80::7e5a:1cff:fe72:c831/64

And it is using this gateway:
fe80::f2:5d09

How do I fix this?

1. The forum does support adding images, but only via the "reply" function, not with "quick reply".
2. Take a look at this. Some ISPs only hand out a prefix, which you can use now on WAN.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

Ahh, you can't click the "add image" button, as that can only link to a remote image, you have to drag it in...

I get a /56 range from my ISP. And was told to select "Request only an IPv6 prefix."

It looks like I do get an IPv6 address for my WAN interface, but the wrong gateway is selected.
You cannot view this attachment.


And that is why I get a private gateway on the dashboard:
You cannot view this attachment.

This worked fine in PFsense, so nothing wrong with ISP.

You first said you did not get an IPv6 on WAN, but now you get one, that is O.K.

I do not see what is wrong with that gateway. It may well be a LL adress like fe80::f2:5d09 and the gateway monitoring says it can be pinged, so what is the problem?

Please show your WAN configuration page and expand the gateway column in the pictures. Also, please show your LAN addresses.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

Looks good. You get a WAN address via SLAAC and a delegated /56 via DHCPv6. Pretty typical for PPPoE. Gateway also looks good, gateway monitoring works.

Is there an actual issue? What doesn't work?

"Use IPv4 connectivity" has always been kind of misleading. This just meant that IPv6 uses the PPP interface, too, not the parent interface. That's the default now, so no need to look for this setting.

Cheers
Maurice
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).

> "Use IPv4 connectivity" has always been kind of misleading. This just meant that IPv6 uses the PPP interface, too, not the parent interface. That's the default now, so no need to look for this setting.

Code wise the bad thing about that setting has always been that enabling it is the implicit standard of the code, but the setting was designed as opt-in making the default non-standard and bloating the interface code with it.

On top of that the old disabled default can easily be achieved by assigning the parent interface and setting it to DHCPv6.

So as of 25.1 you have both the correct default for 99% of the use cases and still have the possibility to use the old-style setup if you need to. Though I'm not sure anybody actually needed that judging by the lack of feedback on this particular point.


Cheers,
Franco

Agreed that the current implementation is much cleaner, both code wise as well as from the user perspective. Because...

Quote from: franco on November 12, 2025, 01:37:57 PMThough I'm not sure anybody actually needed that judging by the lack of feedback on this particular point.

... that's absolutely true. The combination of IPv4 over PPPoE + IPv6 over plain Ethernet is super rare and I'm not even sure why it would make sense.
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).