PPPoE won't reconnect after link loss
|Affected version:||2.0||Affected Architecture:||amd64|
Attached are four files. Here's how I got them:
1. Boot system fresh. PPPoE connected.
2.clog /var/log/system.log | egrep '(mpd|ppp)' > ppp_working.txt
cp /var/etc/mpd_wan.conf mpd_wan_working.conf.txt
3. Pull plug on WAN NIC. Wait 2 minutes. Re-plug. (WAN not connecting)
4.clog /var/log/system.log | egrep '(mpd|ppp)' > ppp_not_working.txt
cp /var/etc/mpd_wan.conf mpd_wan_not_working.conf.txt
5. Reboot to working WAN.
Null Service Name is checked.
#1 Updated by David Burgess about 1 year ago
I commented out the line:
/usr/sbin/ngctl shutdown $1
from the file
as recommended by jimp in the linked forum thread and this fixed the problem. Updating pfsense to 2.0.1 overwrote my changes however and so the problem returned. I don't know what this line is supposed to, but from my little centre of the universe it appears it should just be removed from future releases.
#4 Updated by Bipin Chandra 8 months ago
works in link loss situations and i think it should be implemented rather having to apply patch after every update
#5 Updated by Andrew Stuart 6 months ago
I too can confirm this works for a family member running on 2.0.1. In their case, if they never established a connection for example, the modem wasn't powered on when pfSense booted, it will never attempt to connect.
#6 Updated by Renato Botelho 4 months ago
Is it still happening on recent snapshots? I couldn't reproduce it, every time I re-plugged the wan cabble, pppoe reconnected fine.
#9 Updated by Bipin Chandra 4 months ago
this is a very old issue, a big long thread on this since ages http://forum.pfsense.org/index.php/topic,41061.0.html
#10 Updated by Bipin Chandra 4 months ago
the issue is some driver related and Unisphere BRAS which more and more isp r using which uses some flood protection or some security so many ppl suffering this and the worst thing is every other cheap router in the market reconnects fine except pfsense, i personally tried this in 2 different countries with different isp
there r 3 situations:
- unplug wan cable and if connected within link loss trigger timeout then connection continues
- unplug wan cable and wait till complete link loss, approx 2mins and then reconnect cable and a new connection is negotiated but it wont reconnect
- reset isp modem and when its up pfsense needs to renegotiate and reconnect but falls, results in reconnect loop and never comes up until pfsense is rebooted
Bipin, if you've identified that Unisphere BRAS is used by all the ISPs you've tried and had problems with, then perhaps you should also discuss your finding with the developers of mpd at http://mpd.sourceforge.net/
#12 Updated by Bipin Chandra 4 months ago
i did post at the freebsd forum and also somewhere on mpd long time back but hardly any1 replied, few suggestions were posted regarding mpd config change which dont help at all
#13 Updated by bkraptor - 4 months ago
I tested with the following build and the issue is not present for me any more:
built on Thu Jan 24 07:40:32 EST 2013
#14 Updated by David Burgess 4 months ago
- File reconnect_log.txt added
built on Mon Jan 21 16:42:50 EST 2013
After unplugging then replugging the WAN interface (actually, this pfsense has only one physical NIC, with multiple LANs and WANs via vlans), the pppoe connection comes active again, but some problems remain:
- The most recent entries in the PPP log (webUI) appear to indicate that the link is still down, even though it is up (attached).
- My LAN interface has a rule that defines a failover gateway on a non-ppp interface. Even after the WAN pppoe interface is back up, pfsense continues to use the failover WAN for the LAN gateway. I disabled the failover interface and pfsense then routed the LAN traffic through the main WAN pppoe interface correctly, but as soon as I re-enabled the failover interface, pfsense again started routing LAN traffic through the failover interface. It is as if pfsense does not see the WAN as up, although traffic from other LANs appears to be passing through the WAN as normal.
- I received a notification from pfsense by email: "Gateways status could not be determined, considering all as up/active. (Group: [failover_group])"
- The Diagnostic>States page shows no existing state for the failover WAN, even while I am pinging or doing a traceroute through it from the LAN. Is this normal?
I don't know if these problems are related to this bug, but they are new problems to me and I only observe them when the WAN goes down.
#17 Updated by Bipin Chandra 3 months ago
here is the thread at mpd forum, doesnt seem like a mpd issue but some network drivers
#18 Updated by Andrea Soster about 1 month ago
I have the same problem with one of my firewall in china, I'm connected to a huawei SmartAX MA5620-8 -> there's a fiber connected to it and then an ethernet cable to pfsense. The provider is China Unicom. The box is an alix 2D13 running 2.0.2 i386
After some time the PPP connection drops and it's unable to reconnect, the only solution is to reboot the machine and the DSL comes back.
Which king of debug shall I provide the next time it happens?
I spoke to Jim Pingle on chat and he told me to save ppp log,mpd config files (where is it?), "ngctl list". Anything else?
Please note that I have already commented out the line:
/usr/sbin/ngctl shutdown $1
from the file
but nothing changed
Let me know, thanks