Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    New PPPoE backend, some feedback

    Scheduled Pinned Locked Moved Development
    216 Posts 17 Posters 23.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      louis2 @stephenw10
      last edited by louis2

      @stephenw10

      Hum .. I had to think about the rout-able IPV6 in the picture higher up, so I looked at my PPOE overview.

      8fcd750c-15d1-45b5-8807-b2245b9babb2-image.png

      As you can see in my case there is an link local address, which does not surprise me. And I checked it is pingable

      2e473c4e-41f7-4205-80b8-2858579ce2a9-image.png

      not from some other lan of course!! It is a link local address 😊

      1 Reply Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @benbng
        last edited by

        @benbng I wonder, why you have a MTU of 1500 with PPPoE, usually it is lower.

        B 1 Reply Last reply Reply Quote 0
        • L
          louis2
          last edited by

          @benbng

          I wonder does the IPV6 address in your TROOLI interface to your IPV6 range or is it an address in the providers infrastructure at the providers side of the PPOE !??

          B 1 Reply Last reply Reply Quote 0
          • B
            benbng @stephenw10
            last edited by

            @stephenw10 logs below as requested.

            mpd
            mpdsystem.txt
            mpddhcp6c.txt

            if_pppoe with Do not wait for a RA checked
            ifpppoesystem.txt
            ifpppoedhcp6c.txt

            if_pppoe with Do not wait for a RA unchecked
            ifpppoesystemnora.txt
            ifpppoedhcp6cnora.txt

            I can confirm IPv4 connectivity is working from clients using both mpd and if_pppoe. When using if_pppoe the firewall itself has IPv6 connectivity (with addresses outside of my ISP's network) however any internal client traffic that matches a firewall rule with the IPv6 gateway is not routed, certainly looks like something to do with pfSense gateways as opposed to a routing/PPP/DHCP issue.

            Let me know if I can provide any additional logs.

            stephenw10S 1 Reply Last reply Reply Quote 0
            • B
              benbng @Bob.Dig
              last edited by

              @Bob-Dig there was some talk about this towards the start of the thread; a number of ISPs within the UK support https://datatracker.ietf.org/doc/html/rfc4638 which accounts for the PPPoE overhead and enables devices to use an MTU of 1500 without having to resort to MSS clamping or any of that fun.

              1 Reply Last reply Reply Quote 0
              • B
                benbng @louis2
                last edited by

                @louis2 sorry which address are you referring to? The IPv6 Address is on the provider's side and allocated from the DHCPv6 request, the Gateway IPv6 address is the ISP's router's link-local address which you can find when looking at your dhcp6c logs (for an entry similar to receive advertise from fe80::a:b:c:d%pppoex)

                L 1 Reply Last reply Reply Quote 0
                • L
                  louis2 @benbng
                  last edited by

                  @benbng

                  That is what I did expect, but wanted to know for sure.
                  Thanx

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator @benbng
                    last edited by

                    @benbng said in New PPPoE backend, some feedback:

                    any internal client traffic that matches a firewall rule with the IPv6 gateway is not routed,

                    That is the expected behaviour if the gateway is marked as offline. I assume that's not the default IPv6 gateway? If it is I'd expect anything passed without a gateway set to still be able to use it.

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      benbng @stephenw10
                      last edited by

                      @stephenw10 it should be the default, because it's marked as pending though it doesn't show this as you can see in my earlier screenshots.

                      Interestingly the gateway doesn't seem to get populated as the monitor IP; is this supposed to be set within one of the scripts that has been changed as part of the 2.8.0 release?

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        If the gateway is off line any policy routing rules will either by applied without a gateway or omitted entirely depending on the Advanced Firewall Rule setting.

                        Any client IPv6 traffic that is passed without a gateway set should just follow the default route in which case it should work.

                        But that's not really the issue here, it's that dpinger ever starts on the link-local gateway for some reason. 🤔

                        L 1 Reply Last reply Reply Quote 0
                        • L
                          louis2 @stephenw10
                          last edited by

                          @stephenw10

                          ?? What is wrong about that ?? And why is my IPV6 gateway still showing as unkown, where it is working perfectly ??

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            Unclear at this point. There certainly seems to be some combination of variables that prevents dpinger starting with a link-local gateway. I'm not sure what that is yet because it works fine on my own WAN and everything I've tested.

                            1 Reply Last reply Reply Quote 0
                            • B
                              benbng
                              last edited by

                              I noticed that when using if_pppoe the file containing the gateway address at location /tmp/pppoe1_routerv6 was missing; this file is supposed to be created by the rtsold script within /var/etc (and then used by function get_interface_gateway_v6.)

                              I manually created this file (taking the gateway address from the default route) and then under Diagnostics > Command Prompt ran PHP Command: setup_gateways_monitor(); after this my IPv6 gateway shows as Online, however despite the fact it is the default gateway for IPv6 it is still not forwarding traffic.

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                Hmm, good catch. Do you see the policy routing rules in the ruleset? (/tmp/rules.debug) Do they have the gateway on them?

                                1 Reply Last reply Reply Quote 0
                                • B
                                  benbng
                                  last edited by

                                  Ah thanks for that, I did a filter reload (via Status > Filter Reload) and it's routing now!

                                  Something I have noticed is my ISP doesn't seem to be sending a Router Advertisement:
                                  f6436d6d-e2d0-4802-b03f-1bd4b8bd5d26-image.png

                                  Could the rtsold behaviour be different when using if_pppoe in this situation? This is quite old but I wonder if it could potentially be related? https://redmine.pfsense.org/issues/14072

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Hmm, it could. The RA behaviour of different ISPs seems to vary significantly.

                                    Mine sends an RA each time the pppoe link connects. And only then. Which makes everything work just fine!

                                    RobbieTTR 1 Reply Last reply Reply Quote 0
                                    • RobbieTTR
                                      RobbieTT @stephenw10
                                      last edited by

                                      @stephenw10 said in New PPPoE backend, some feedback:

                                      Hmm, it could. The RA behaviour of different ISPs seems to vary significantly.

                                      Mine sends an RA each time the pppoe link connects. And only then. Which makes everything work just fine!

                                      Is that an actual RA or solicited?

                                      The variance of ISPs is probably the point and perhaps requires more care with if_pppoe. As it is:

                                      2025-06-09 20:09:04.501728+01:00	php	57356	/usr/local/sbin/ppp-ipv6: Starting rtsold process on wan(pppoe0)
2025-06-09 20:09:04.501539+01:00	php	57356	/usr/local/sbin/ppp-ipv6: Starting DHCP6 client for interfaces pppoe0
2025-06-09 20:09:04.469732+01:00	php	57356	/usr/local/sbin/ppp-ipv6: Accept router advertisements on interface pppoe0
2025-06-09 20:09:04.046407+01:00	kernel	-	pppoe0: link state changed to UP

                                      As soon as the pppoe link is up if_pppoe is always set to accept RAs and then (with not wait for RAs set) is directed to start the rtsold process. Perhaps asking the system to respond to both even with 'do not wait' set is asking for trouble?

                                      ☕️

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        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.

                                        1 Reply Last reply Reply Quote 0
                                        • B
                                          benbng
                                          last edited by

                                          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?

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

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

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.