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

    PPPoE reconenction fix - mpd fix ($100)

    Scheduled Pinned Locked Moved Expired/Withdrawn Bounties
    243 Posts 24 Posters 185.1k 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.
    • X
      xbipin
      last edited by

      how about just check the drivers code and see the changes and cherry pick them which possibly might solve this network port stuck in a limbo state

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Given how widespread the Alix install base is - pleeease, no. No backporting of vr drivers from FreeBSD 10.x to 2.1. While I can understand that it sucks for affected people

        • this can apparently be extremely easily worked around by putting a switch between the pfsense box and the modem,
        • this clearly affects a tiny percentage of users with specific NIC/modem/DSLAM combo on PPPoE specifically.

        => certainly not worth the risk of breaking everyone else

        1 Reply Last reply Reply Quote 0
        • X
          xbipin
          last edited by

          lets just leave it to the developers to decide, what they can do is provide the drivers separately to install so every1 dont need to use this

          1 Reply Last reply Reply Quote 0
          • V
            vtas
            last edited by

            I have this issue and it occurs more frequently since updating to 2.0.3-RELEASE (i386).

            I doubt a switch is going to make any difference in my case because I am running pfsense in a VM that effectively has an always up (virtual) switch, connected to a physical Intel E1000 card port patched straight into a routerboard (all gear on battery) so I am not getting disconnected because of a layer 1 issue.

            I'm a bit lost at how to proceed. Running a script to tear down the interface and bring it back up if it's up and experiencing no throughput (but it is present) seems like the best bet

            1 Reply Last reply Reply Quote 0
            • X
              xbipin
              last edited by

              thats the only way to get back the link going, if u read few posts back, some1 did design a script for this and it actually worked, atleast to some extend

              y dont everyone add some amount to this so some1 can develop a fix for this, probably a newer driver might solve it

              1 Reply Last reply Reply Quote 0
              • V
                vtas
                last edited by

                @xbipin:

                thats the only way to get back the link going, if u read few posts back, some1 did design a script for this and it actually worked, atleast to some extend

                y dont everyone add some amount to this so some1 can develop a fix for this, probably a newer driver might solve it

                Thanks for the tip about the script. How can the bounty be added to apart from just making a note in my post?

                1 Reply Last reply Reply Quote 0
                • X
                  xbipin
                  last edited by

                  just make a post with ur amount, few of the developers r following this thread so they will know of it

                  1 Reply Last reply Reply Quote 0
                  • R
                    ronjns
                    last edited by

                    I had similar issue with FreeBSD 9.1 RELEASE and pppoe('8'). The fix was to 'enable echo' in ppp.conf.

                    echo
                        Default: Disabled.  When this option is enabled, ppp will send
                        LCP ECHO requests to the peer at the frequency defined by
                        echoperiod''.  Note, LQR requests will supersede LCP ECHO     requests if enabled and negotiated.  See set lqrperiod'' below
                        for details.

                    Prior to ppp version 3.4.2, echo'' was considered enabled if     lqr was enabled and negotiated, otherwise it was considered dis-     abled.  For the same behaviour, it is now necessary to enable
                        lqr echo'' rather than just ``enable lqr''.

                    http://www.freebsd.org/cgi/man.cgi?query=ppp&sektion=8

                    1 Reply Last reply Reply Quote 0
                    • S
                      senser
                      last edited by

                      I am wondering if this thread is about fixing the issue that I have (excuse my ignorance, but this thread is quite long):

                      When I unplug the cable to my DSL modem (Alix, pfSense 2.1) and plug it back in, I cannot establish the pppoe connection again (a reboot will fix it, haven't tried anything else, sorry). If I disable the pppoe connection in pfSense prior to reconnecting the cable, I can establish the pppoe connection again.

                      We use the mighty pf, we cannot be fooled.

                      1 Reply Last reply Reply Quote 0
                      • X
                        xbipin
                        last edited by

                        any1 tried enabling echo if it solves it or no?

                        1 Reply Last reply Reply Quote 0
                        • E
                          eri--
                          last edited by

                          Ok coming back to this after some time.

                          I think i have solved the issue here and tomorrow snapshots should have a fix.
                          Can you test and let me know?

                          1 Reply Last reply Reply Quote 0
                          • X
                            xbipin
                            last edited by

                            ok ill try it out and revert back, can u post the link to the commit?

                            1 Reply Last reply Reply Quote 0
                            • E
                              eri--
                              last edited by

                              https://github.com/pfsense/pfsense-tools/commit/4d298135387ef551ccc6eff62a1705059956c64e

                              https://github.com/pfsense/pfsense/commit/9510780ffa41bf1b19989b418e9a356702ba5576

                              1 Reply Last reply Reply Quote 0
                              • X
                                xbipin
                                last edited by

                                brilliant, almost after 2.5 years its solved now, plz send me ur paypal id for payment in PM

                                1 Reply Last reply Reply Quote 0
                                • X
                                  xbipin
                                  last edited by

                                  the bug has appeared in 2.2 RC again and pppoe wont reconenct at all untill u reboot it, log is the same, just endless loops of connection attempts

                                  1 Reply Last reply Reply Quote 0
                                  • E
                                    eri--
                                    last edited by

                                    This should work as before or better in 2.2-RC++

                                    1 Reply Last reply Reply Quote 0
                                    • X
                                      xbipin
                                      last edited by

                                      @ermal:

                                      This should work as before or better in 2.2-RC++

                                      well after the last changes u made the situation is same for me, if i unplug or modem goes down and up, then it wont connect at all in hours also, only way to make it connect is reboot.

                                      1 Reply Last reply Reply Quote 0
                                      • X
                                        xbipin
                                        last edited by

                                        here r the logs with the latest snap

                                        Jan 13 10:20:24 	ppp: [wan_link0] LCP: no reply to 2 echo request(s)
Jan 13 10:20:34 	ppp: [wan_link0] LCP: no reply to 3 echo request(s)
Jan 13 10:20:44 	ppp: [wan_link0] LCP: no reply to 4 echo request(s)
Jan 13 10:20:54 	ppp: [wan_link0] LCP: no reply to 5 echo request(s)
Jan 13 10:20:54 	ppp: [wan_link0] LCP: peer not responding to echo requests
Jan 13 10:20:54 	ppp: [wan_link0] LCP: state change Opened --> Stopping
Jan 13 10:20:54 	ppp: [wan_link0] Link: Leave bundle "wan"
Jan 13 10:20:54 	ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Jan 13 10:20:54 	ppp: [wan] IPCP: Close event
Jan 13 10:20:54 	ppp: [wan] IPCP: state change Opened --> Closing
Jan 13 10:20:54 	ppp: [wan] IPCP: SendTerminateReq #4
Jan 13 10:20:54 	ppp: [wan] IPCP: LayerDown
Jan 13 10:20:55 	ppp: [wan] IFACE: Delete route 0.0.0.0/0 2.48.4.1 failed: No such process
Jan 13 10:20:55 	ppp: [wan] IFACE: Down event
Jan 13 10:20:55 	ppp: [wan] IFACE: Rename interface pppoe0 to pppoe0
Jan 13 10:20:55 	ppp: [wan] IPV6CP: Close event
Jan 13 10:20:55 	ppp: [wan] IPV6CP: state change Stopped --> Closed
Jan 13 10:20:55 	ppp: [wan] IPCP: Down event
Jan 13 10:20:55 	ppp: [wan] IPCP: LayerFinish
Jan 13 10:20:55 	ppp: [wan] Bundle: No NCPs left. Closing links...
Jan 13 10:20:55 	ppp: [wan] IPCP: state change Closing --> Initial
Jan 13 10:20:55 	ppp: [wan] IPV6CP: Down event
Jan 13 10:20:55 	ppp: [wan] IPV6CP: state change Closed --> Initial
Jan 13 10:20:55 	ppp: [wan_link0] LCP: SendTerminateReq #3
Jan 13 10:20:55 	ppp: [wan_link0] LCP: LayerDown
Jan 13 10:21:00 	ppp: [wan_link0] LCP: SendTerminateReq #4
Jan 13 10:21:02 	ppp: [wan_link0] LCP: state change Stopping --> Stopped
Jan 13 10:21:02 	ppp: [wan_link0] LCP: LayerFinish
Jan 13 10:21:02 	ppp: [wan_link0] PPPoE: connection closed
Jan 13 10:21:02 	ppp: [wan_link0] Link: DOWN event
Jan 13 10:21:02 	ppp: [wan_link0] LCP: Down event
Jan 13 10:21:02 	ppp: [wan_link0] LCP: state change Stopped --> Starting
Jan 13 10:21:02 	ppp: [wan_link0] LCP: LayerStart
Jan 13 10:21:02 	ppp: [wan_link0] Link: reconnection attempt 1 in 4 seconds

                                        the system log does show the interface a down and then later a linkup message but it just wont reconnect and more interesting is y does the below fail

                                        Jan 13 10:20:55 	ppp: [wan] IFACE: Delete route 0.0.0.0/0 2.48.4.1 failed: No such process

                                        bear in mind that FTTH modem the isp has given here, when u connect the wan cable coming out of it to any machine, by default it wont get any ip at all, in windows it would try and then fail and revert to 169.x.x.x, the machine would just say cable connected but no ip on it, not even any private ip

                                        1 Reply Last reply Reply Quote 0
                                        • E
                                          eri--
                                          last edited by

                                          I am interested on your system log not your ppp logs.

                                          1 Reply Last reply Reply Quote 0
                                          • X
                                            xbipin
                                            last edited by

                                            here u go, included both the logs

                                            system log

                                            Jan 15 10:07:38 	syslogd: kernel boot file is /boot/kernel/kernel
Jan 15 10:07:46 	kernel: vr1: link state changed to DOWN
Jan 15 10:08:43 	check_reload_status: Restarting ipsec tunnels
Jan 15 10:08:43 	check_reload_status: Restarting OpenVPN tunnels/interfaces
Jan 15 10:08:43 	check_reload_status: Reloading filter
Jan 15 10:08:46 	php-fpm[56184]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN.
Jan 15 10:08:46 	php-fpm[56184]: /rc.openvpn: OpenVPN: Resync client1 ExpressVPN
Jan 15 10:08:49 	php-fpm[56184]: /rc.openvpn: OpenVPN ID client1 PID 20721 still running, killing.
Jan 15 10:08:49 	kernel: ovpnc1: link state changed to DOWN
Jan 15 10:08:50 	check_reload_status: Reloading filter
Jan 15 10:08:53 	php-fpm[41289]: /rc.dyndns.update: phpDynDNS (firewall.domain.com): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jan 15 10:08:55 	php: rc.kill_states: rc.kill_states: Removing states for IP 86.99.125.32/32
Jan 15 10:08:55 	check_reload_status: Rewriting resolv.conf
Jan 15 10:08:59 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:08:59 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:08:59 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:08:59 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:00 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:00 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:00 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:00 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:00 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:00 	php-fpm[55844]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:02 	check_reload_status: Linkup starting vr1
Jan 15 10:09:02 	kernel: vr1: link state changed to UP
Jan 15 10:09:07 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:07 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:07 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:07 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:07 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:07 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:07 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:07 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:08 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:08 	php-fpm[56184]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Jan 15 10:09:15 	check_reload_status: Restarting ipsec tunnels
Jan 15 10:09:20 	check_reload_status: updating dyndns wan

                                            ppp logs

                                            Jan 15 10:08:34 	ppp: [wan_link0] LCP: no reply to 3 echo request(s)
Jan 15 10:08:44 	ppp: [wan_link0] LCP: no reply to 4 echo request(s)
Jan 15 10:08:54 	ppp: [wan_link0] LCP: no reply to 5 echo request(s)
Jan 15 10:08:54 	ppp: [wan_link0] LCP: peer not responding to echo requests
Jan 15 10:08:54 	ppp: [wan_link0] LCP: state change Opened --> Stopping
Jan 15 10:08:54 	ppp: [wan_link0] Link: Leave bundle "wan"
Jan 15 10:08:54 	ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Jan 15 10:08:54 	ppp: [wan] IPCP: Close event
Jan 15 10:08:54 	ppp: [wan] IPCP: state change Opened --> Closing
Jan 15 10:08:54 	ppp: [wan] IPCP: SendTerminateReq #4
Jan 15 10:08:54 	ppp: [wan] IPCP: LayerDown
Jan 15 10:08:55 	ppp: [wan] IFACE: Delete route 0.0.0.0/0 2.48.4.1 failed: No such process
Jan 15 10:08:55 	ppp: [wan] IFACE: Down event
Jan 15 10:08:55 	ppp: [wan] IFACE: Rename interface pppoe0 to pppoe0
Jan 15 10:08:55 	ppp: [wan] IPV6CP: Close event
Jan 15 10:08:55 	ppp: [wan] IPV6CP: state change Stopped --> Closed
Jan 15 10:08:55 	ppp: [wan] IPCP: Down event
Jan 15 10:08:55 	ppp: [wan] IPCP: LayerFinish
Jan 15 10:08:55 	ppp: [wan] Bundle: No NCPs left. Closing links...
Jan 15 10:08:55 	ppp: [wan] IPCP: state change Closing --> Initial
Jan 15 10:08:55 	ppp: [wan] IPV6CP: Down event
Jan 15 10:08:55 	ppp: [wan] IPV6CP: state change Closed --> Initial
Jan 15 10:08:55 	ppp: [wan_link0] LCP: SendTerminateReq #3
Jan 15 10:08:55 	ppp: [wan_link0] LCP: LayerDown
Jan 15 10:08:58 	ppp: [wan_link0] LCP: SendTerminateReq #4
Jan 15 10:09:00 	ppp: [wan_link0] LCP: state change Stopping --> Stopped
Jan 15 10:09:00 	ppp: [wan_link0] LCP: LayerFinish
Jan 15 10:09:00 	ppp: [wan_link0] PPPoE: connection closed
Jan 15 10:09:00 	ppp: [wan_link0] Link: DOWN event
Jan 15 10:09:00 	ppp: [wan_link0] LCP: Down event
Jan 15 10:09:00 	ppp: [wan_link0] LCP: state change Stopped --> Starting
Jan 15 10:09:00 	ppp: [wan_link0] LCP: LayerStart
Jan 15 10:09:00 	ppp: [wan_link0] Link: reconnection attempt 1 in 1 seconds
Jan 15 10:09:01 	ppp: [wan_link0] Link: reconnection attempt 1
Jan 15 10:09:01 	ppp: [wan_link0] PPPoE: Connecting to ''
Jan 15 10:09:05 	ppp: Multi-link PPP daemon for FreeBSD
Jan 15 10:09:05 	ppp:
Jan 15 10:09:05 	ppp: process 67927 started, version 5.7 (root@pfsense-22-i386-builder 13:22 18-Nov-2014)
Jan 15 10:09:05 	ppp: caught fatal signal TERM
Jan 15 10:09:05 	ppp: [wan] IFACE: Close event
Jan 15 10:09:05 	ppp: [wan] IPCP: Close event
Jan 15 10:09:05 	ppp: [wan] IPV6CP: Close event
Jan 15 10:09:05 	ppp: waiting for process 6370 to die...
Jan 15 10:09:06 	ppp: waiting for process 6370 to die...
Jan 15 10:09:07 	ppp: [wan] Bundle: Shutdown
Jan 15 10:09:07 	ppp: [wan_link0] Link: Shutdown
Jan 15 10:09:07 	ppp: process 6370 terminated
Jan 15 10:09:07 	ppp: web: web is not running
Jan 15 10:09:07 	ppp: [wan] Bundle: Interface ng0 created
Jan 15 10:09:07 	ppp: [wan_link0] Link: OPEN event
Jan 15 10:09:07 	ppp: [wan_link0] LCP: Open event
Jan 15 10:09:07 	ppp: [wan_link0] LCP: state change Initial --> Starting
Jan 15 10:09:07 	ppp: [wan_link0] LCP: LayerStart
Jan 15 10:09:07 	ppp: [wan_link0] PPPoE: Connecting to ''
Jan 15 10:09:16 	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jan 15 10:09:16 	ppp: [wan_link0] Link: DOWN event
Jan 15 10:09:16 	ppp: [wan_link0] LCP: Down event
Jan 15 10:09:16 	ppp: [wan_link0] Link: reconnection attempt 1 in 3 seconds
Jan 15 10:09:19 	ppp: [wan_link0] Link: reconnection attempt 1
Jan 15 10:09:19 	ppp: [wan_link0] PPPoE: Connecting to ''
Jan 15 10:09:28 	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jan 15 10:09:28 	ppp: [wan_link0] Link: DOWN event
Jan 15 10:09:28 	ppp: [wan_link0] LCP: Down event
Jan 15 10:09:28 	ppp: [wan_link0] Link: reconnection attempt 2 in 4 seconds
Jan 15 10:09:32 	ppp: [wan_link0] Link: reconnection attempt 2
Jan 15 10:09:32 	ppp: [wan_link0] PPPoE: Connecting to ''
Jan 15 10:09:41 	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jan 15 10:09:41 	ppp: [wan_link0] Link: DOWN event
Jan 15 10:09:41 	ppp: [wan_link0] LCP: Down event
Jan 15 10:09:41 	ppp: [wan_link0] Link: reconnection attempt 3 in 2 seconds
Jan 15 10:09:43 	ppp: [wan_link0] Link: reconnection attempt 3
Jan 15 10:09:43 	ppp: [wan_link0] PPPoE: Connecting to ''
Jan 15 10:09:52 	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jan 15 10:09:52 	ppp: [wan_link0] Link: DOWN event
Jan 15 10:09:52 	ppp: [wan_link0] LCP: Down event
Jan 15 10:09:52 	ppp: [wan_link0] Link: reconnection attempt 4 in 4 seconds
Jan 15 10:09:56 	ppp: [wan_link0] Link: reconnection attempt 4
Jan 15 10:09:56 	ppp: [wan_link0] PPPoE: Connecting to ''
Jan 15 10:10:05 	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jan 15 10:10:05 	ppp: [wan_link0] Link: DOWN event
Jan 15 10:10:05 	ppp: [wan_link0] LCP: Down event
Jan 15 10:10:05 	ppp: [wan_link0] Link: reconnection attempt 5 in 2 seconds
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.