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

    PPPOE disconnect

    General pfSense Questions
    4
    14
    4.9k
    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.
    • B
      bdaniel7
      last edited by

      Hello,

      I'm running pfSense 2.2.6 x64 on a Gigabyte GA-N3050N-D3H motherboard with
      Intel(R) Celeron(R) CPU N3050 @ 1.60GHz
      Current: 1600 MHz, Max: 1601 MHz
      2 CPUs: 1 package(s) x 2 core(s)

      4 GB of RAM

      The network cards:

      
re0@pci0:1:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x0c hdr=0x00
re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0xe000-0xe0ff mem 0x81300000-0x81300fff,0xa0100000-0xa0103fff irq 16 at device 0.0 on pci1
rgephy0: <rtl8251 1000base-t="" media="" interface="">PHY 1 on miibus0

re1@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x0c hdr=0x00
re1: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0xd000-0xd0ff mem 0x81200000-0x81200fff,0xa0000000-0xa0003fff irq 17 at device 0.0 on pci2
rgephy1: <rtl8251 1000base-t="" media="" interface="">PHY 1 on miibus1</rtl8251></realtek></rtl8251></realtek>

      And during high speed transfers, like when doing a speed test, the pppoe disconnects and won't reconnect unless I reboot the router.

      This is the log:

      
Apr 1 20:56:54	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:54	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:56:54	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:56:54	ppp: [wan_link0] LCP: Open event
Apr 1 20:56:54	ppp: [wan_link0] Link: OPEN event
Apr 1 20:56:54	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:56:54	ppp: web: web is not running
Apr 1 20:56:53	ppp: process 47666 terminated
Apr 1 20:56:53	ppp: [wan_link0] Link: Shutdown
Apr 1 20:56:53	ppp: waiting for process 47666 to die...
Apr 1 20:56:53	ppp: [wan] Bundle: Shutdown
Apr 1 20:56:52	ppp: waiting for process 47666 to die...
Apr 1 20:56:51	ppp: waiting for process 47666 to die...
Apr 1 20:56:51	ppp: [wan] IPV6CP: Close event
Apr 1 20:56:51	ppp: [wan] IPCP: Close event
Apr 1 20:56:51	ppp: [wan] IFACE: Close event
Apr 1 20:56:51	ppp: caught fatal signal TERM
Apr 1 20:56:51	ppp: process 60882 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:56:51	ppp:
Apr 1 20:56:51	ppp: Multi-link PPP daemon for FreeBSD
Apr 1 20:56:47	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:47	ppp: [wan_link0] Link: reconnection attempt 1
Apr 1 20:56:44	ppp: [wan_link0] Link: reconnection attempt 1 in 3 seconds
Apr 1 20:56:44	ppp: [wan_link0] LCP: Down event
Apr 1 20:56:44	ppp: [wan_link0] Link: DOWN event
Apr 1 20:56:44	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Apr 1 20:56:35	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:35	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:56:35	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:56:35	ppp: [wan_link0] LCP: Open event
Apr 1 20:56:35	ppp: [wan_link0] Link: OPEN event
Apr 1 20:56:35	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:56:35	ppp: web: web is not running
Apr 1 20:56:35	ppp: process 11520 terminated
Apr 1 20:56:35	ppp: [wan_link0] Link: Shutdown
Apr 1 20:56:35	ppp: [wan] Bundle: Shutdown
Apr 1 20:56:34	ppp: waiting for process 11520 to die...
Apr 1 20:56:33	ppp: [wan] IPV6CP: Close event
Apr 1 20:56:33	ppp: [wan] IPCP: Close event
Apr 1 20:56:33	ppp: [wan] IFACE: Close event
Apr 1 20:56:33	ppp: caught fatal signal TERM
Apr 1 20:56:33	ppp: waiting for process 11520 to die...
Apr 1 20:56:33	ppp: process 47666 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:56:33	ppp:
Apr 1 20:56:33	ppp: Multi-link PPP daemon for FreeBSD
Apr 1 20:56:29	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:29	ppp: [wan_link0] Link: reconnection attempt 1
Apr 1 20:56:27	ppp: [wan_link0] Link: reconnection attempt 1 in 2 seconds
Apr 1 20:56:27	ppp: [wan_link0] LCP: Down event
Apr 1 20:56:27	ppp: [wan_link0] Link: DOWN event
Apr 1 20:56:27	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Apr 1 20:56:18	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:18	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:56:18	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:56:18	ppp: [wan_link0] LCP: Open event
Apr 1 20:56:18	ppp: [wan_link0] Link: OPEN event
Apr 1 20:56:18	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:56:18	ppp: web: web is not running
Apr 1 20:56:18	ppp: process 84181 terminated
Apr 1 20:56:18	ppp: [wan_link0] Link: Shutdown
Apr 1 20:56:18	ppp: [wan] Bundle: Shutdown
Apr 1 20:56:17	ppp: waiting for process 84181 to die...
Apr 1 20:56:16	ppp: waiting for process 84181 to die...
Apr 1 20:56:16	ppp: [wan] IPV6CP: Close event
Apr 1 20:56:16	ppp: [wan] IPCP: Close event
Apr 1 20:56:16	ppp: [wan] IFACE: Close event
Apr 1 20:56:16	ppp: caught fatal signal TERM
Apr 1 20:56:16	ppp: process 11520 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:56:16	ppp:
Apr 1 20:56:16	ppp: Multi-link PPP daemon for FreeBSD
Apr 1 20:56:14	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:14	ppp: [wan_link0] Link: reconnection attempt 1
Apr 1 20:56:10	ppp: [wan_link0] Link: reconnection attempt 1 in 4 seconds
Apr 1 20:56:10	ppp: [wan_link0] LCP: Down event
Apr 1 20:56:10	ppp: [wan_link0] Link: DOWN event
Apr 1 20:56:10	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Apr 1 20:56:01	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:01	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:56:01	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:56:01	ppp: [wan_link0] LCP: Open event
Apr 1 20:56:01	ppp: [wan_link0] Link: OPEN event
Apr 1 20:56:01	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:56:01	ppp: web: web is not running
Apr 1 20:56:01	ppp: process 30022 terminated
Apr 1 20:56:01	ppp: [wan_link0] Link: Shutdown
Apr 1 20:56:01	ppp: [wan] Bundle: Shutdown
Apr 1 20:56:00	ppp: waiting for process 30022 to die...
Apr 1 20:55:59	ppp: [wan] IPV6CP: Close event
Apr 1 20:55:59	ppp: [wan] IPCP: Close event
Apr 1 20:55:59	ppp: [wan] IFACE: Close event
Apr 1 20:55:59	ppp: caught fatal signal TERM
Apr 1 20:55:59	ppp: waiting for process 30022 to die...
Apr 1 20:55:59	ppp: process 84181 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:55:59	ppp:
Apr 1 20:55:59	ppp: Multi-link PPP daemon for FreeBSD
Apr 1 20:55:55	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:55:55	ppp: [wan_link0] Link: reconnection attempt 1
Apr 1 20:55:53	ppp: [wan_link0] Link: reconnection attempt 1 in 2 seconds
Apr 1 20:55:53	ppp: [wan_link0] LCP: Down event
Apr 1 20:55:53	ppp: [wan_link0] Link: DOWN event
Apr 1 20:55:53	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Apr 1 20:55:44	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:55:44	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:55:44	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:55:44	ppp: [wan_link0] LCP: Open event
Apr 1 20:55:44	ppp: [wan_link0] Link: OPEN event
Apr 1 20:55:44	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:55:44	ppp: web: web is not running
Apr 1 20:55:44	ppp: process 5937 terminated
Apr 1 20:55:44	ppp: [wan_link0] Link: Shutdown
Apr 1 20:55:44	ppp: [wan] Bundle: Shutdown
Apr 1 20:55:43	ppp: waiting for process 5937 to die...
Apr 1 20:55:42	ppp: waiting for process 5937 to die...
Apr 1 20:55:42	ppp: [wan] IFACE: Rename interface pppoe0 to pppoe0
Apr 1 20:55:42	ppp: [wan] IFACE: Down event
Apr 1 20:55:41	ppp: [wan] IPV6CP: LayerDown
Apr 1 20:55:41	ppp: [wan] IPV6CP: SendTerminateReq #3
Apr 1 20:55:41	ppp: [wan] IPV6CP: state change Opened --> Closing
Apr 1 20:55:41	ppp: [wan] IPV6CP: Close event
Apr 1 20:55:41	ppp: [wan] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address
Apr 1 20:55:41	ppp: [wan] IFACE: Delete route 0.0.0.0/0 10.0.0.1 failed: No such process
Apr 1 20:55:41	ppp: [wan] IPCP: LayerDown
Apr 1 20:55:41	ppp: [wan] IPCP: SendTerminateReq #4
Apr 1 20:55:41	ppp: [wan] IPCP: state change Opened --> Closing
Apr 1 20:55:41	ppp: [wan] IPCP: Close event
Apr 1 20:55:41	ppp: [wan] IFACE: Close event
Apr 1 20:55:41	ppp: waiting for process 5937 to die...
Apr 1 20:55:41	ppp: process 30022 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:55:41	ppp:
Apr 1 20:55:41	ppp: Multi-link PPP daemon for FreeBSD

      Any ideas as to why this would happen?
      I purchased this board because it doesn't need a CPU fan and I had the hdd and ram from a laptop.

      Could it be caused by the provider? Or the cpu is too slow?

      Thank you,
      Daniel

      1 Reply Last reply Reply Quote 0
      • A
        alextz
        last edited by

        Same stuff here with it's brother GA-N3150-D3V. It only happens when powerD is in Adaptive. In HiAdaptive when I do a speedtest I can see the loss in gateways going to 3-5% but no disconnection.

        I can post a video if necessary.

        1 Reply Last reply Reply Quote 0
        • A
          alextz
          last edited by

          18 hours later when I try a speedtest in 5 seconds the connection is dropped.
          I do not know what is going wrong here.

          1 Reply Last reply Reply Quote 0
          • A
            alextz
            last edited by

            Tried PPPoe with linux kernel (ipfire, arch linux) and after 24h+ on each everything is working perfectly.

            Can we troubleshoot this on pfsense?

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              Try with a pfSense 2.3 snapshot, it's most likely some interaction between FreeBSD and that board/BIOS if tweaking powerd brings out the problem.

              Next step is to reproduce the problem with your hardware on plain FreeBSD 10.3 and if it also shows the problem there, then report it directly to FreeBSD.

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

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

                I ran a live image with OPNsense 16.1.8-amd64/FreeBSD 10.2-RELEASE-p14/OpenSSL 1.0.2g on the same hardware and I did several speed tests and it worked without a problem.

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  Apples and oranges (Different FreeBSD version bases) – compare against pfSense 2.3.

                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

                  1 Reply Last reply Reply Quote 0
                  • A
                    alextz
                    last edited by

                    I did that and it does not work. Pfsense 2.2.6 or 2.3 do not work with this hardware correctly.

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

                      @jimp:

                      Apples and oranges (Different FreeBSD version bases) – compare against pfSense 2.3.

                      I understand, I wanted to check if the hardware is too slow.

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

                        I have updated to 2.3-RC (amd64) built on Wed Apr 06 05:34:38 CDT 2016 /FreeBSD 10.3-RELEASE
                        The GUI certainly looks better.
                        And the extra help info next to the settings is very welcome.

                        But the problem is still there.

                        1 Reply Last reply Reply Quote 0
                        • A
                          alextz
                          last edited by

                          Tried FreeBSD 10.3 with PPPoe and it stays up without any problem for 48h+. The problem is in pfSense itself somewhere.

                          1 Reply Last reply Reply Quote 0
                          • T
                            TugBoat
                            last edited by

                            I have a quite different hardware configuration:

                            pfsense 2.2.6 under ESXi 6.0U2 (ie. virtualised)

                            what I am seeing looks very similar in that the PPPoE disconnects frequently, and the disconnections appear to be load related. When there was little/no Internet usage (ie. nobody at home) the PPPoE link stayed up for 4 days. When the net starts getting used a lot it is up/down a lot - sometimes a few minutes apart. The log shows something like:

                            Apr 26 08:07:44 router ppp: [wan] IFACE: Up event
                            Apr 26 08:07:44 router ppp: [wan] IFACE: Rename interface ng0 to pppoe0
                            Apr 26 08:16:21 router ppp: Multi-link PPP daemon for FreeBSD
                            Apr 26 08:16:21 router ppp:
                            Apr 26 08:16:21 router ppp: process 52834 started, version 5.7 (root@pfSense_REL
                            ENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
                            Apr 26 08:16:21 router ppp: waiting for process 14050 to die…
                            Apr 26 08:16:21 router ppp: caught fatal signal TERM
                            Apr 26 08:16:21 router ppp: [wan] IFACE: Close event

                            I don't think that this is related to virtualisation. I also have a copy of pfsense 2.2.5 running under ESXi 5.5U3 and the PPPoE links stay up fine with no TERM signals encountered. I suppose it could relate to the 6.0U2 vs 5.5U3 for ESXi, however, given that these other reports are here I suspect it is more likely a 2.2.6 issue.

                            I think I will run up a 2.2.5 pfsense and see whether it has the same problems.

                            Tim

                            1 Reply Last reply Reply Quote 0
                            • T
                              TugBoat
                              last edited by

                              I have now tried 2.2.5/2.2.6/2.3 and all releases show similar behaviour in my vmware environment.

                              The 2.2.5 release does not include the "caught fatal signal TERM" in the logs, however, in all other respects the logs look the same.

                              So I have a working production configuration: pfsense 2.2.5 / ESXi 5.5U3 /  Dell T320 server / TP-Link TD-8817 modem

                              The configuration with the PPPoE Disconnect issue is: ESXi 6.0U2 / Intel NUC / Apple USB Ethernet for PPPoe / TP-Link TD-8817 modem

                              So, I suppose my next investigation is to switch to using VLANs to obtain multiple network links and thus delete the USB Ethernet. The USB Ethernet connections get a lot of bad press, so perhaps it is the source of my problem.

                              1 Reply Last reply Reply Quote 0
                              • T
                                TugBoat
                                last edited by

                                Well, it looks like my problems with PPPoE are related to the use of the USB Ethernet adapter for the PPPoE link.

                                A) I moved the USB Ethernet to a 'charging' USB port on the Intel NUC. The 'charging' USB ports can supply up to 1.5A (or there abouts). The result of this was to significantly improve the stability of the PPPoE. However, there were still still multiple PPPoE dropouts with the 'caught signal TERM' message in the logs over the next 24 hours.

                                B) I then moved the PPPoE traffic onto a VLAN on the main Ethernet port. I have left the USB Ethernet plugged in and attached to pfsense - however, it is not being used for anything. The result of this is that there have been no PPPoE outages due to the 'caught signal TERM', all outages have been loss of LCP echo on the link. Link uptime is significantly better.

                                So, in summary, I have no idea of exactly where the 'problem' is with the USB Ethernet adapter, but it certainly looks like attempting to use it for a PPPoe link does not work. So my attempt to work around only having a single Ethernet port on the NUC by using a USB Ethernet for the PPPoE wasn't the best idea.

                                Tim

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