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

    New PPPoE backend, some feedback

    Scheduled Pinned Locked Moved Development
    255 Posts 20 Posters 45.4k Views 17 Watching
    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.
    • stephenw10S Offline
      stephenw10 Netgate Administrator
      last edited by

      Hmm that's an interesting setup. I don't think I've ever seen that before. I assume it was working previously with mpd5/negraph?

      Can you say which ISP that is?

      1 Reply Last reply Reply Quote 0
      • A Offline
        azalea
        last edited by

        I assume it was working previously with mpd5/negraph?

        Yes, it is working with mpd5/negraph. And it is working with if_pppoe for IPv4, but not for IPv6.

        Can you say which ISP that is?

        ISP is "plala" in Japan. To be precise, it is a combination of a network enabler (NTT FLET'S) and an ISP (plala).

        The separation of IPv4 and IPv6 is a specification of "NTT FLET'S". The purpose of this specification is to allow users to choose between IPv4 and IPv6 ISPs separately. I choose plala for both IPv4 and IPv6.

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

          Hmm, so I assume the IPv6 only pppoe connection does not have Use IPv4 connectivity as parent interface set?

          Do you see anything logged from the dhcp6c client?

          I suspect it never gets triggered if there is no IPv4 address ever set. 🤔

          1 Reply Last reply Reply Quote 0
          • A Offline
            azalea
            last edited by

            I suspect it never gets triggered if there is no IPv4 address ever set.

            PPP is a protocol that can support IPv4-only, IPv6-only, IPv4 and IPv6.

            Hmm, so I assume the IPv6 only pppoe connection does not have Use IPv4 connectivity as parent interface set?

            "Use IPv4 connectivity as parent interface" is required. However, for "IPv6 only pppoe connection", "Use IPv4 connectivity as parent interface" means "Use IPv6 connectivity as parent interface". Therefore, in the PPP configuration for "IPv4 connectivity", set the IPv6 username and IPv6 password.

            This PPP configuration is used to construct PPPoE tunnels for IPv6 and not to set IPv4 address. ("Use IPv4 connectivity" reminds you of IPv4 address settings, but that's not the case.)

            In fact, IPv6CP is accepted and IPCP is rejected in PPPoE negotiation, so IPv6 Link Local is set, PPPoE is connected, but IPv4 address is not set.

            Below is the PPP log where IPCP was rejected.

            PPP log

mpd5:
ppp 	23292 	[wan] IPCP: protocol was rejected by peer

if_pppoe:
if_pppoe: pppoe0: lcp input(opened): <proto-rej id=0x1 len=28
if_pppoe: pppoe0: lcp: RXJ+ (proto-rej) for proto 0x8021 (ipcp/req-sent)

            For reference, there is information related to "Use IPv4 connectivity as parent interface".

            OPNsense (25.1 and later) has revised the architecture, and "IPv6 only pppoe connection" no longer requires "Use IPv4 connectivity as parent interface". "IPv6 only pppoe connection" is directly linked to a PPPoE connection.
            -> Restructure PPP to allow complex IPv6-only deployments with all implications

            Do you see anything logged from the dhcp6c client?

            Below is the log when using if_pppoe. There is no difference from mpd5.

            DHCP log

Sep 4 04:16:24 	dhcp6c 	36830 	failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Sep 4 04:16:24 	dhcp6c 	36830 	failed initialize control message authentication
Sep 4 04:16:24 	dhcp6c 	36830 	skip opening control port
Sep 4 04:16:25 	dhcp6c 	36979 	Sending Solicit
Sep 4 04:16:26 	dhcp6c 	36979 	Sending Request
Sep 4 04:16:26 	dhcp6c 	36979 	dhcp6c Received REQUEST
Sep 4 04:16:26 	dhcp6c 	36979 	add an address [IPv6 Address]/64 on em1

            I'll check the PPP log in debug mode, so please take a little time.

            w0wW 1 Reply Last reply Reply Quote 0
            • w0wW Offline
              w0w @azalea
              last edited by w0w

              @azalea
              This doesn’t look like a problem with PPPoE or DHCPv6 itself.
              It seems more like dpinger isn’t starting for some known reason. Your log shows that you successfully obtained an IPv6 address, so I assume that if you go to System → Routing, edit your IPv6 PPPoE gateway, and disable gateway monitoring, your IPv6 should work again. This looks similar to the issue described here: https://forum.netgate.com/topic/198627/struggling-to-get-if_pppoe-kernel-module-working

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

                Hmm, that dhcpv6 log looks like the client is being triggered and that it is pulling a lease. Is that not the case?

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

                  @stephenw10

                  Since the 'new pfSense versions', which in general are working OK, the status of my IPV6-gateway is shown as unkown. Which is not dramatic since IPV6 is working, but not OK as well.

                  I still hope it will be fixed.

                  e7f25342-cd78-471a-b4d8-f40d6b4a81b1-image.png

                  Note:
                  Running the latest pfSense+ version

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

                    Yup there are more IPv6 fixes coming.

                    1 Reply Last reply Reply Quote 0
                    • P Offline
                      Phil2025 @louis2
                      last edited by

                      @louis2 Yes several of us are having this issue. A fix seems to be to go to: Status - Gateways - then click the recycle button to restart the Gateway service, it should then switch to online.

                      40cda19d-00df-4fb7-bfae-7a166768f3ee-image.png

                      1 Reply Last reply Reply Quote 0
                      • A Offline
                        azalea
                        last edited by azalea

                        In my first report, I reported "IPv6 Address is set but not reachable", but found a condition to obtain global reachability.
                        (I checked the global response in pfSense's "Diagnostics > Ping".)

                        My ISP has a limit on the number of PPPoE sessions available. My ISP won't allow me to open a new PPPoE session until it knows the previous one has been closed. Also, if I disconnect a PPPoE session without manually closing it, my ISP takes about 5 minutes to recognize that the PPPoE session has been closed.

                        These specifications make the following difference:

                        (a) If I reboot pfSense with manually closing the PPPoE session, pppoe0 links up and the IPv6 address is set before "Bootup complete".
                        (b) If I reboot pfSense without manually closing the PPPoE session, pppoe0 links up and the IPv6 address is set after "Bootup complete".

                        In case (a), the ping passed, but in case (b), the ping failed.

                        When I checked "Use if_pppoe kernel module for PPPoE client" to enable if_pppoe, this fell under case (b). As a result, the ping failed.

                        Here are some other facts I have confirmed:
                        [PPP log]
                        Each time a PPPoE session is established, the message "failed to set default route 17" may or may not be displayed.

                        • The message is not displayed after bootup.
                        • The message is displayed after executing the "ifconfig pppoe0 down/up" command.
                        • The message is not displayed after clicking the "Disconnect/Connect" button in Interfaces Status.

                        Every time a PPPoE session is established, the message "failed to clear IP address: 49" is displayed.

                        [Interfaces Status]
                        The "Gateway IPv6" item is not always displayed. It is not blank. The item itself does not exist.
                        The "Gateway IPv6" undisplayed issue is unrelated to the message "failed to set default route 17" displayed/undisplayed issue.
                        The "Gateway IPv6" undisplayed issue is unrelated to Ping pass/fail. In case (a), Ping passes.

                        [DHCP log]
                        Basically, the message "add an address [IPv6 Address]/64 on em1" is displayed each time a PPPoE session is established.

                        • The message is displayed before or after "Bootup complete" and the IPv6 address is set.
                        • The message is displayed after executing the "ifconfig pppoe0 down/up" command and the IPv6 address is set.
                        • However, after clicking the "Disconnect/Connect" button in Interfaces Status, "Sending Solicit" is displayed repeatedly, no message is displayed, and the IPv6 address is not set. After that, even after executing the "ifconfig pppoe0 down/up" command, "Sending Solicit" is displayed repeatedly, no message is displayed, and the IPv6 address is not set. If I reboot again, the message is displayed and the IPv6 address is set.

                        [Ping]
                        In case (a), the ping passes regardless of whether the "failed to set default route 17" message is displayed or not.
                        In case (a), the ping passes regardless of the dpinger Status (Running/Stopped).
                        In case (a), the ping passes regardless of the Gateways Status (Online/Pending).
                        In case (a), the ping passes even after executing the "ifconfig pppoe0 down/up" command.

                        [Gateways/dpinger]
                        When dpinger Status is Stopped, nothing is displayed in the Gateways Log.
                        If I set Gateway's IPv6 Link Local to "Monitor IP", the dpinger Status is displayed as Running. Then, "send_interval" and so on is displayed in the Gateways Log.
                        The dpinger status (Running/Stopped) is unrelated to Ping pass/fail. Ping pass/fail is determined by case (a)/case (b).
                        The Gateways Status (Online/Pending) is unrelated to Ping pass/fail. Ping pass/fail is determined by case (a)/case (b).

                        Based on the facts presented, I assume that the issue of "Gateway IPv6" not being set and the issue of ping failure are independent issues.

                        P 1 Reply Last reply Reply Quote 2
                        • stephenw10S Offline
                          stephenw10 Netgate Administrator
                          last edited by

                          So you also see failures in IPv6 when using mpd5/netgraph?

                          Do IPv4 pings (general connectivity) succeed in both cases? Jusr varies the IPv6 response?

                          1 Reply Last reply Reply Quote 0
                          • P Offline
                            perrin @azalea
                            last edited by

                            @azalea said in New PPPoE backend, some feedback:

                            failed to set default route 17

                            i am having the exact same issue with the if_pppoe failed setting the default route and failed getting an IPv6 config. Never had any problems with this using MPD.

                            The issue is occurring when you disconnect, reconnect the interface or disable/enable it. upon a clean boot, everything works as expected

                            the only solution to regain connectivity is to reboot the firewall. it will not work otherwise. did not try to unload/reload the kernel module due to lack of knowledge on BSD.

                            stephenw10S 1 Reply Last reply Reply Quote 0
                            • w0wW Offline
                              w0w
                              last edited by w0w

                              In my case, enabling "Request only an IPv6 prefix" gives me a more stable IPv6 connection, and the WAN interface now consistently gets an IPv6 address as well.
                              There have definitely been some changes on the ISP’s side too, because it suddenly started losing the IPv6 connection while IPv4 was still working fine. Enabling this option fixed the issue — my IPv6 connection is now stable.

                              And yes, as I’ve mentioned before, I had the same problem: it wouldn’t get an IPv6 address after a reconnection, but everything worked fine after rebooting the firewall.

                              Here is a screenshot of my final settings.
                              1000033288.jpg

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

                                @perrin said in New PPPoE backend, some feedback:

                                i am having the exact same issue with the if_pppoe failed setting the default route and failed getting an IPv6 config.

                                This happens when it first connects? Just at random during runtime?

                                P 1 Reply Last reply Reply Quote 0
                                • P Offline
                                  perrin @stephenw10
                                  last edited by perrin

                                  @stephenw10 it always happens whenever you manually reconnect (via status/interfaces) the interface or disable / enable the interface. Upon reboot / first connect everything works fine

                                  To me it seems that there is a case where if_pppoe gets in some sort of stale state which can only be solved by rebooting

                                  it came to my attention when i was developing the pppoe_ha package. in that process I was disabling/enabling the interface often and noted the connectivity loss.

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

                                    What does pppcfg show in that situation?

                                    If you enable debugging (ifconfig pppoe0 debug) what does it show?

                                    If you manually reconnect the parent NIC dies that allow it to connect?

                                    P 1 Reply Last reply Reply Quote 0
                                    • P Offline
                                      perrin @stephenw10
                                      last edited by

                                      @stephenw10 I will try that as soon as possible when I can afford some downtime. Was not aware of these debug options. Will keep you posted and update the thread asap.

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

                                        Be aware that the debug option currently will spam the console. So be ready to run ifconfig pppoe0 -debug 😉

                                        1 Reply Last reply Reply Quote 0
                                        • P Offline
                                          perrin
                                          last edited by perrin

                                          I tried it this moring before working hours but i could not reliably reproduce the stale state.

                                          Didn't have much time to test but i tried a few enable/disable interfaces and pause/resume of the virtual machine of the primary firewall so that the failover occurs and pppoe needs to reconnect.
                                          This morning everything worked as expected.

                                          A few notes on my side: Both firewalls only had an uptime of less than a day. so it might be that the issue only occurs on longer uptime, maybe also if something happens on the provider side in regards to the pppoe session.

                                          Also i did reconfigure the dhcp v6 settings accoring to the post of @wow which seemed to make the IPv6 stuff (more) stable than before.

                                          The only things i've seen from the (debug) logs which kind of are hinting towards an error are the following lines:

                                          Sep 19 07:55:53 	kernel 		if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:55:42 	kernel 		if_pppoe: pppoe0: pap failure
Sep 19 07:55:41 	kernel 		if_pppoe: pppoe0: failed to clear IP address: 49

                                          we can safely ignore the pap failure in my case as this must be due to the failover i was testing. in this case the provider thinks the pppoe session for my user is still active (on the other firewall) so i get a few pap failures in failover until the provider closes the stale session of the other firewall.
                                          I've seen the other errors (default route/ip address) previously though and those might be related to some error.

                                          anyway I will do another test in a couple of days and keep you posted...

                                          edit: i extracted the relevant parts of the pppoe debug log. don't know if that is any help, but i am posting it anyway:

                                          [25.07.1-RELEASE][root@pfSense.xxxxxxxxxx]/root: bzcat /var/log/ppp.log.* | grep "Sep 19" | grep -v output
Sep 19 07:43:00 pfSense newsyslog[73829]: logfile turned over due to size>500K
Sep 19 07:43:05 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x3 len=8
Sep 19 07:43:05 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:43:15 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x4 len=8
Sep 19 07:43:15 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:43:25 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x5 len=8
Sep 19 07:43:25 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:43:35 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x6 len=8
Sep 19 07:43:35 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:43:45 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x7 len=8
Sep 19 07:43:45 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: lcp close(opened)
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: lcp opened->closing
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: phase terminate
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipcp down(opened)
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipcp opened->starting
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipcp close(starting)
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipcp starting->initial
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipv6cp down(opened)
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipv6cp opened->starting
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipv6cp close(starting)
Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->initial
Sep 19 07:43:48 pfSense kernel: if_pppoe: pppoe0: pap failure
Sep 19 07:43:58 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:44:00 pfSense newsyslog[82494]: logfile turned over due to size>500K
Sep 19 07:35:30 pfSense newsyslog[52425]: logfile turned over due to size>500K
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: LCP keepalive timeout
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp close(opened)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp opened->closing
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase terminate
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipcp down(opened)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipcp opened->starting
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipcp close(starting)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipcp starting->initial
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipv6cp down(opened)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipv6cp opened->starting
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipv6cp close(starting)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->initial
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp closing->stopped
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: timeout
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: disconnecting
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp down(stopped)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp stopped->starting
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase establish
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: Down event (carrier loss), taking interface down.if_pppoe: pppoe0: lcp close(starting)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp starting->initial
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase dead
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: session 0x1bd connected
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp open(initial)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp initial->starting
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase establish
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp up(starting)
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp starting->req-sent
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp input(req-sent): <conf-req id=0xb7 len=18
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp parse opts:
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp parse opt values:
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp req-sent->ack-sent
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp input(ack-sent): <conf-ack id=0x16 len=14
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp ack-sent->opened
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp tlu
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: up
Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase authenticate
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: pap success
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: phase network
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp open(initial)
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp initial->starting
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp open(initial)
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp initial->starting
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp up(starting)
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp starting->req-sent
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp up(starting)
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->req-sent
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp input(req-sent): <conf-req id=0x99 len=10
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp parse opts:
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp parse opt values:
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp req-sent->ack-sent
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp input(ack-sent): <conf-nak id=0x18 len=22
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp nak opts:
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp input(req-sent): <conf-req id=0x40 len=14
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp parse opts:
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp parse opt values:
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp req-sent->ack-sent
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp input(ack-sent): <conf-ack id=0x1a len=22
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp ack-sent->opened
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp tlu
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp input(ack-sent): <conf-ack id=0x19 len=14
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp ack-sent->opened
Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp tlu
Sep 19 07:35:55 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x0 len=8
Sep 19 07:35:55 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:36:06 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x1 len=8
Sep 19 07:36:06 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:36:15 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x2 len=8
Sep 19 07:36:15 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:36:25 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x3 len=8
Sep 19 07:36:25 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:36:35 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x4 len=8
Sep 19 07:36:35 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: LCP keepalive timeout
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp close(opened)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp opened->closing
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase terminate
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipcp down(opened)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipcp opened->starting
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipcp close(starting)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipcp starting->initial
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipv6cp down(opened)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipv6cp opened->starting
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipv6cp close(starting)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->initial
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp closing->stopped
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: timeout
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: disconnecting
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp down(stopped)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp stopped->starting
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase establish
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: Down event (carrier loss), taking interface down.if_pppoe: pppoe0: lcp close(starting)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp starting->initial
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase dead
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: session 0x1bd connected
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp open(initial)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp initial->starting
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase establish
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp up(starting)
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp starting->req-sent
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp input(req-sent): <conf-req id=0x36 len=18
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp parse opts:
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp parse opt values:
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp req-sent->ack-sent
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp input(ack-sent): <conf-ack id=0x1f len=14
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp ack-sent->opened
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp tlu
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: up
Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase authenticate
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: pap success
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: phase network
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp open(initial)
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp initial->starting
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp open(initial)
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp initial->starting
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp up(starting)
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp starting->req-sent
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp up(starting)
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->req-sent
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp input(req-sent): <conf-req id=0x22 len=10
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp parse opts:
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp parse opt values:
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp req-sent->ack-sent
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp input(ack-sent): <conf-nak id=0x21 len=22
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp nak opts:
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp input(req-sent): <conf-req id=0x36 len=14
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp parse opts:
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp parse opt values:
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp req-sent->ack-sent
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp input(ack-sent): <conf-ack id=0x23 len=22
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp ack-sent->opened
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp tlu
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp input(ack-sent): <conf-ack id=0x22 len=14
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp ack-sent->opened
Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp tlu
Sep 19 07:42:35 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x0 len=8
Sep 19 07:42:35 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:42:45 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x1 len=8
Sep 19 07:42:45 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:42:55 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x2 len=8
Sep 19 07:42:55 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:43:00 pfSense newsyslog[73829]: logfile turned over due to size>500K
Sep 19 07:25:28 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:27:28 pfSense kernel: if_pppoe: pppoe0: failed to clear IP address: 49
Sep 19 07:27:29 pfSense kernel: if_pppoe: pppoe0: pap failure
Sep 19 07:31:18 pfSense kernel: if_pppoe: pppoe0: LCP keepalive timeout
Sep 19 07:31:18 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:31:18 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17
Sep 19 07:34:59 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x7 len=8
Sep 19 07:34:59 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep
Sep 19 07:35:30 pfSense newsyslog[52425]: logfile turned over due to size>500K
                                          1 Reply Last reply Reply Quote 0
                                          • w0wW Offline
                                            w0w
                                            last edited by

                                            Possible that another problem found and maybe solved :)
                                            I want to note that the problem shows only with the new if_pppoe; with mpd5 all VIP addresses come up successfully.
                                            I tried to study why on my HA primary sometimes the system boots with VIP addresses on LAN not initialized. It looks like we have again a race condition.

                                            Even if PPPoE is configured at the end using the function

                                            /* setup PPPoE and PPTP (this will bring up if_pppoe) -edited by me */
vpn_setup();

                                            called from /etc/rc.bootup, in my case interfaces often do not have time to get all VIPs. I have many ports, they flap several times (down/up), and this coincides with the moment when PPPoE brings the link up successfully. At this moment it seems the VIP configuration stays unfinished. From experiments I noticed usually only one VIP gets configurated.

                                            I am not sure if this is the correct solution, but I added into /etc/rc.bootup the line

                                            interfaces_vips_configure("");

                                            before

                                            /* setup PPPoE and PPTP (this will bring up if_pppoe) */
vpn_setup();

                                            This tends system to wait interfaces_vips_configure is completed.
                                            After that it looks OK. All VIPs are present and CARP works too.

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