PPPoE reconenction fix - mpd fix ($100)
-
cant we take the vr drivers from FreeBSD 10.x and test it on current pfsense to see if it will actually fix this issue
Possible but might not be trivial: FreeBSD internal interfaces and data structures might have changed significantly requiring considerable work to backport those changes as well or rewrite the vr changes from FreeBSD 8.3 to 10.x to work in FreeBSD 8.3 context.
Best case (assuming familiarity with FreeBSD kernel build procedures): maybe an hour or two to import the 10.x source into a 8.3 build system, recompile and run some basic tests.
Worst case: maybe up to a few months to figure out what changes in FreeBSD internals to backport and do them.
-
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
-
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
-
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
-
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
-
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
-
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?
-
just make a post with ur amount, few of the developers r following this thread so they will know of it
-
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. Seeset 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 toenable
lqr echo'' rather than just ``enable lqr''.http://www.freebsd.org/cgi/man.cgi?query=ppp&sektion=8
-
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.
-
any1 tried enabling echo if it solves it or no?
-
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? -
ok ill try it out and revert back, can u post the link to the commit?
-
https://github.com/pfsense/pfsense-tools/commit/4d298135387ef551ccc6eff62a1705059956c64e
https://github.com/pfsense/pfsense/commit/9510780ffa41bf1b19989b418e9a356702ba5576
-
brilliant, almost after 2.5 years its solved now, plz send me ur paypal id for payment in PM
-
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
-
This should work as before or better in 2.2-RC++
-
@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.
-
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 secondsthe 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 processbear 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
-
I am interested on your system log not your ppp logs.