Messages

Thanks for your reply. I'll try to explain the reasons again:

I have a DHCP server in the internal LAN that assigns ULAs to clients in certain VLANs. Some of these networks also have GUAs. IPv4 addresses are also assigned, but they are not affected by the problem. The problem is that I don't want to have GUAs in all networks and, secondly, I want the clients to be permanently accessible via the ULAs assigned by the DHCP. This is not possible with the provider's dynamic addresses, for example, and in some cases is also undesirable.

[The problem]

Hi all,

I've run into a problem with OPNsense 25.2 and it still exists in 25.7 (all patch levels so far), when using a PPPoE WAN connection (VDSL, bridged modem).

The setup is quite typical here (Germany/Europe):

• VDSL modem in bridge mode (DrayTek Vigor 167)
• WAN over PPPoE on VLAN 10
• Provider requires VLAN 20 for VoIP
• OPNsense is doing the PPPoE login and should also provide stable IPv6 addresses to the internal LANs

The problem

As soon as I enable DHCPv6 on the PPPoE interface (e.g. to request a prefix), the DHCPv6 Relay service stops working.

The log shows:

Code Select Expand

Notice dhcrelay fatal in dhcrelay6: interface '%pppoe0' not found
Sometimes this log entry doesn't even appear, but the service never starts in this situation.

• There is no entry in the general system log, only under Services: DHCRelay: Log File.
• ps axww shows nothing because the relay process never starts if PPPoE + DHCPv6 is enabled.

With PPPoE active + DHCPv6 enabled → dhcp6relay does not run, internal networks receive no IPv6.

• Disabling PPPoE / deleting the WAN interface → dhcrelay6 works again.
• Without DHCPv6 enabled on PPPoE, the relay runs.

So the bug persists until the WAN/PPPoE is removed.

Without DHCPv6 enabled on PPPoE, the relay runs.

Code Select Expand

root    72882   0.0  0.1 13768  2456  -  Is   22:09      0:00.00 daemon: /usr/local/sbin/dhcrelay6[72932] (daemon)
_dhcp   72932   0.0  0.1 13680  2424  -  I    22:09      0:00.00 /usr/local/sbin/dhcrelay6 -d -o -i vtnet2 df00:1234:1234:140::2%vtnet1
The example comes from a new installation with a VM and Proxmox. I created this to be able to reproduce the problem cleanly; my productive OPNSense runs on real hardware. The problem is identical on both machines.

Reproduced the problem

Create a VLAN under:

Interfaces: Devices: VLAN

Create a PPPoE interface that uses the VLAN created above.

Interfaces: Devices: Point-to-Point

Under

Interfaces: Assignments,

create an interface that uses the PPPoE device. Click on the newly created interface and select "Enable Interface." Now select DHCPv6 under "IPv6 Configuration Type" and save. If you now restart opnsense or turn the ipv6 relay off and on again, the dhcp relay option for ipv6 is no longer functional.

Expected behavior

dhcrelay6 should run correctly on a PPPoE WAN interface with DHCPv6 enabled.
Instead of the invalid placeholder %pppoe0, it should use the actual interface name.

Additional notes

• If I start dhcrelay6 manually with the correct parameters, the relay works exactly as expected.
• This confirms that it is not a FreeBSD/PPPoE limitation, but a problem in how OPNsense generates the service parameters.

Why this matters

• Many ISPs here deliver IPv6 only via DHCPv6 on PPPoE.
• Prefix Delegation with "Track Interface" works, but it does not provide stable internal IPv6 addresses (prefix may change).
• For stable addressing, DHCPv6 Relay to an internal DHCPv6 server is the correct approach — but it's currently broken.

Questions to the community

• Has anyone else run into this with PPPoE WAN?
• Can anyone else reproduce this with PPPoE WAN + DHCPv6 relay?
• Is there already a known fix or patch?
• Should I open a new GitHub issue, or is this bug already tracked somewhere?

Notes

• With a FritzBox doing the PPPoE and IPv6, relay works fine.
• Only OPNsense directly on PPPoE triggers the %pppoe placeholder issue.

I am aware of alternatives like prefix delegation / track interface or using a FritzBox in front.
For my use case these are not options, I specifically need a working DHCPv6 relay behind PPPoE.
Please let's keep the focus on confirming and reproducing the %pppoe interface bug in dhcrelay6.

Thanks for any feedback — and if you see the same behavior, please confirm so we can get this properly tracked/fixed.