PPPoE Disconnects
-
My internet connection drops randomly at least once per day and the only way I have been able to restore it is to reboot my PfSense router. Basically, I lose my dynamic IP address and PfSense cannot obtain a new address without a reboot (I have tried reconnecting via the PPPoE "Connect" button under "Interfaces"–"WAN Interface" but it does not work). There must be a way of reconnecting without having to reboot--this is a little like using a sledge hammer to nail a tack on the wall. Is anyone aware of another way of fixing this annoying problem??? :'(
-
What version of pfSense?
Please post a segment of the PPP log file showing events leading up to and after one of the "Connect" attempts.
-
I use the latest version of PfSense-embedded.
Here is a copy of the relevant portion of my PPP log before and after a fall:
Mar 29 21:58:10 ppp: [wan] 10.8.66.1 is OK
Mar 29 21:58:10 ppp: [wan] IPCP: SendConfigAck #215
Mar 29 21:58:10 ppp: [wan] IPADDR 10.8.66.1
Mar 29 21:58:10 ppp: [wan] IPCP: state change Ack-Rcvd –> Opened
Mar 29 21:58:10 ppp: [wan] IPCP: LayerUp
Mar 29 21:58:10 ppp: [wan] 79.176.16.93 -> 10.8.66.1
Mar 29 21:58:10 ppp: [wan] IFACE: Up event
Mar 29 22:41:03 ppp: [wan_link0] LCP: no reply to 1 echo request(s)
Mar 29 22:41:13 ppp: [wan_link0] LCP: no reply to 2 echo request(s)
Mar 29 22:41:23 ppp: [wan_link0] LCP: no reply to 3 echo request(s)
Mar 29 22:41:33 ppp: [wan_link0] LCP: no reply to 4 echo request(s)
Mar 29 22:41:43 ppp: [wan_link0] LCP: no reply to 5 echo request(s)
Mar 29 22:41:43 ppp: [wan_link0] LCP: peer not responding to echo requests
Mar 29 22:41:43 ppp: [wan_link0] LCP: state change Opened –> Stopping
Mar 29 22:41:43 ppp: [wan_link0] Link: Leave bundle "wan"
Mar 29 22:41:43 ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Mar 29 22:41:43 ppp: [wan] IPCP: Close event
Mar 29 22:41:43 ppp: [wan] IPCP: state change Opened –> Closing
Mar 29 22:41:43 ppp: [wan] IPCP: SendTerminateReq #4
Mar 29 22:41:43 ppp: [wan] IPCP: LayerDown
Mar 29 22:41:43 ppp: [wan] IFACE: Down event
Mar 29 22:41:43 ppp: [wan] IPCP: Down event
Mar 29 22:41:43 ppp: [wan] IPCP: LayerFinish
Mar 29 22:41:43 ppp: [wan] Bundle: No NCPs left. Closing links…
Mar 29 22:41:43 ppp: [wan] IPCP: state change Closing –> Initial
Mar 29 22:41:43 ppp: [wan_link0] LCP: SendTerminateReq #2
Mar 29 22:41:43 ppp: [wan_link0] LCP: LayerDown
Mar 29 22:41:45 ppp: [wan_link0] LCP: SendTerminateReq #3
Mar 29 22:41:47 ppp: [wan_link0] LCP: state change Stopping –> Stopped
Mar 29 22:41:47 ppp: [wan_link0] LCP: LayerFinish
Mar 29 22:41:47 ppp: [wan_link0] PPPoE: connection closed
Mar 29 22:41:47 ppp: [wan_link0] Link: DOWN event
Mar 29 22:41:47 ppp: [wan_link0] LCP: Down event
Mar 29 22:41:47 ppp: [wan_link0] LCP: state change Stopped –> Starting
Mar 29 22:41:47 ppp: [wan_link0] LCP: LayerStart
Mar 29 22:41:47 ppp: [wan_link0] Link: reconnection attempt 1 in 3 seconds
Mar 29 22:41:50 ppp: [wan_link0] Link: reconnection attempt 1
Mar 29 22:41:50 ppp: [wan_link0] PPPoE: Connecting to ''
Mar 29 22:41:59 ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Mar 29 22:41:59 ppp: [wan_link0] Link: DOWN event
Mar 29 22:41:59 ppp: [wan_link0] LCP: Down event
Mar 29 22:41:59 ppp: [wan_link0] Link: reconnection attempt 2 in 1 seconds
Mar 29 22:42:00 ppp: [wan_link0] Link: reconnection attempt 2
Mar 29 22:42:00 ppp: [wan_link0] PPPoE: Connecting to ''
Mar 29 22:42:09 ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Mar 29 22:42:09 ppp: [wan_link0] Link: DOWN event
Mar 29 22:42:09 ppp: [wan_link0] LCP: Down event
Mar 29 22:42:09 ppp: [wan_link0] Link: reconnection attempt 3 in 2 seconds
Mar 29 22:42:11 ppp: [wan_link0] Link: reconnection attempt 3
Mar 29 22:42:11 ppp: [wan_link0] PPPoE: Connecting to ''
Mar 29 22:42:20 ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Mar 29 22:42:20 ppp: [wan_link0] Link: DOWN event
Mar 29 22:42:20 ppp: [wan_link0] LCP: Down event -
I use the latest version of PfSense-embedded.
Please report the specific version and build (e.g. from the box's home page). "latest version" could mean "latest 2.1 development snapshot build", "latest version I saw" etc. That you are only now reporting a problem apparently seen over 4 weeks ago might suggest you have a particularly idiosyncratic view of "latest" :)
Here is a copy of the relevant portion of my PPP log before and after a fall:
The log suggests the PPPoE server has stopped conversing with your pfSense, especially
Mar 29 22:41:03 ppp: [wan_link0] LCP: no reply to 1 echo request(s)
Mar 29 22:41:13 ppp: [wan_link0] LCP: no reply to 2 echo request(s)
Mar 29 22:41:23 ppp: [wan_link0] LCP: no reply to 3 echo request(s)
Mar 29 22:41:33 ppp: [wan_link0] LCP: no reply to 4 echo request(s)
Mar 29 22:41:43 ppp: [wan_link0] LCP: no reply to 5 echo request(s)
Mar 29 22:41:43 ppp: [wan_link0] LCP: peer not responding to echo requestsYour modem "blew up"? A backhoe went through the telco fibre?
If this behaviour is fairly current, maybe your ISP tech support might be able to give some insight if you posed a question along the lines of "My router is (was?) not getting any response to PPP ECHO requests. Is your equipment seeing them?"
Did the PPP link service recover "by itself"? Did it recover after a pfSense reboot?
-
2.0.1-RELEASE (amd64)
built on Tue Dec 13 14:25:00 EST 2011
FreeBSD 8.1-RELEASE-p6Yes, that is the point–I have to reboot PfSense to get PPPoE to connect again.
I just set the MTU and MSS in PfSense to 1492 and 1452 respectively--I thought I had it set on my computer but I did not--and now I am able to run the speed test at speedtest.net without a PPPoE disconnect (I ran the test 12 times in a row without a problem); previous to this change it would disconnect me every time. I hope this may be my fix but it may not cure the random disconnects. We shall see what happens.
-
There appears to be a bug in my version of PfSense. On the WAN interface, set for PPPoE, it does not allow you to save a "0" setting for "Idle timeout." You can save such a setting if you enter the value via the Setup Wizard, however, editing the WAN page appears to dump the setting. One can imagine what kind of problems this bug creates.
:(