New PPPoE backend, some feedback

stephenw10

It could be since I only see it after the parent pppoe connects:

Jun 8 06:45:47 	rtsold 	82638 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
Jun 8 06:27:57 	rtsold 	13619 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
May 28 16:24:04 	rtsold 	99252 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
May 28 15:30:10 	rtsold 	87300 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
May 26 05:02:01 	rtsold 	64029 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
May 18 17:11:41 	rtsold 	50394 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
May 16 19:31:17 	rtsold 	53108 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
May 14 04:24:39 	rtsold 	49956 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
May 10 20:01:04 	rtsold 	60529 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
May 6 20:36:28 	rtsold 	99065 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
Apr 30 15:01:59 	rtsold 	55432 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
Apr 30 14:34:11 	rtsold 	12977 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
Apr 30 14:03:08 	rtsold 	20686 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)
Apr 28 14:09:46 	rtsold 	73063 	Received RA specifying route fe80::2621:24ff:fed9:623f for interface opt4(pppoe1)

I don't see anything logged either way but I wouldn't expect to.

benbng

Looking through my logs I see no events from rtsold as you do and having reviewed the rtsold man page I strongly suspect that in my case the supplement script will never run since an RA doesn't appear to be sent from my ISP.

I have noticed within /var/etc/mpd_opt10.conf the following line: set iface up-script /usr/local/sbin/ppp-linkup and within this script I can see: echo "${REMOTE_IP}" > "/tmp/${IF}_routerv6" I'm guessing this could be missing for if_pppoe?

stephenw10

if_pppoe uses pppoe-handler instead of those scripts:
https://github.com/pfsense/pfsense/blob/master/src/usr/local/sbin/pppoe-handler#L50

benbng

Can you see a tunnel6 value when you execute the following PHP command: print_r(get_interface_addresses("pppoe1"));?

I cannot:

Array
(
    [status] => up
    [multicast] => 1
    [pointtopoint] => 1
    [simplex] => 1
    [iftype] => other
    [mtu] => 1500
    [caps] => Array
        (
            [flags] => 0
        )

    [encaps] => Array
        (
            [flags] => 0
        )

    [ipaddr] => 98.96.169.137
    [subnetbits] => 32
    [subnet] => 255.255.255.255
    [tunnel] => 199.15.239.1
    [ipaddr6] => 2001:db8:abcd:0012::1
    [subnetbits6] => 128
)

stephenw10

I do, yes:

Array
(
    [status] => up
    [multicast] => 1
    [pointtopoint] => 1
    [simplex] => 1
    [linkstateup] => 1
    [iftype] => other
    [mtu] => 1500
    [caps] => Array
        (
            [flags] => 0
        )

    [encaps] => Array
        (
            [flags] => 0
        )

    [ipaddr] => 86.191.x.x
    [subnetbits] => 32
    [subnet] => 255.255.255.255
    [tunnel] => 172.16.13.252
)

No IPv6 value because it's PD only.

benbng

I can't see tunnel6 in the output you shared, I guess that won't be an issue for you since the rtsold script is creating /tmp/if_routerv6 but in my case since the rtsold script isn't firing the only way would be if that value is returned as per: https://github.com/pfsense/pfsense/blob/master/src/usr/local/sbin/pppoe-handler#L51

So is this a bug when using ISPs that don't send an RA using if_pppoe?

stephenw10

It could be. There's certainly significant variation between ISPs RA handling.

louis2

@stephenw10

Stephen, I wonder if it is perhaps a good idea to create a special version of the pppoe module which generates some debug logging's.

If you make that available as a patch I would more than happy to (temporarely) install and test it.

stephenw10

You can enable debug mode on the interface but I don't think it will help with this. The IPv6 connection all runs on top of the PPPoE once it comes up. Anything different should be visible there.

benbng

In my opinion the logic for setting the IPv6 gateway could be improved in the pppoe_add_addrv6 function (within pppoe-handler) since it currently appears ineffective regardless of whether a RA is received since a tunnel6 value is not returned for the PPPoE interface

louis2

@stephenw10

I think there are probably multiple issues under the hood.

However one of them is IMHO simple to fix, that is the fact that the status of the IPV6 connection on the dashboard is not at all correct.

If you go to status interfaces there is the correct
IPv6 Link Local address. In my case at the moment
fe80::2a0:c9ff:fe22:60aa%pppoe0

And I can ping that address using pfsense ping tool using WAN as origin.

It feels like peanuts to use a ping to that address to check the availability of the IPV6-connecition.

So why not solve this part of the problem !??

RobbieTT

@louis2

Not sure what you mean. My dashboard / Gateways looks like this for reference:

2025-06-11 at 11.36.59.png

️

stephenw10

Yup me too. LL gateway works just fine for me. Which doesn't really help much.

But I think @benbng may be on to something there. Check the values in the pppoe files in /tmp. Perhaps you don't have a /tmp/pppoe0_defaultgwv6 file at all?

RobbieTT

@stephenw10

Perhaps, as the status > interface page should have 2 link local addresses listed; one for the router and one for the default gateway (as per the file in /tmp/). Pinging its own link local would give a result in µs and the default gateway address would be in ms.

I think we need to see what @benbng is looking at.

️

louis2

@RobbieTT

Mine is like this (since the new ppoe)

However IPV6 is working

With the old PPOE after some time the IPV6 looked to be gone, but it was still working. There is a ticket related to that old item.

However I think it is the same item.

And I did complain a couple of times that the indicated IPV6 times in the gui where IMHO also too high not correct.

And in my option all those sings are related to the same wrong way of checking the IPV6 interface

benbng

@louis2 can you see if you have any luck bringing up the IPv6 gateway with the following?

Diagnostics > Command Prompt (Shell Command): netstat -6rWn | grep ::/0 | awk '{print $2}' > /tmp/pppoe0_routerv6
Diagnostics > Command Prompt (PHP Command): setup_gateways_monitor();
Status > Filter Reload (Reload Filter)

stephenw10

Those of you seeing the pending gateway are you all seeing it correctly if you switch back to mpd5?

I think we have a good handle on the problem here if so. Working on the correct fix.

benbng

@stephenw10 yep no issues when using mpd5 (with no changes to config) on CE 2.8.0

Glad to hear things are being looked into, let me know if I can test anything/provide any more logs.

marcosm

@benbng Here's a patch you can test on 2.8.0 to work around the lack of RA issue:
https://nc.netgate.com/nextcloud/s/bt2fWWjdzT4KFHy

benbng

@marcosm I've applied that and it's working great, thank you!