PPPoE reconenction fix - mpd fix ($100)
-
sooner or later more ppl will have this issue once isp switch to unisphere BRAS or they upgrade its software or they implement one session per id restrictions
bytheway i have posted this on mpd forum as well but just one reply where i was asked for logs
http://sourceforge.net/projects/mpd/forums/forum/44692/topic/6720934 -
there was some progress on this matter with the mpd developers and one way they showed to delay sending the PADT when modem is down was by setting set link keep-alive to a higher number and i did that and before mpd could renegotiate a new connection that modem came up but still the connection wouldn't continue and this gives me a strong feeling its the interface drivers but for time being still coordinating with mpd developers
-
the other ppl having this issue or had this issue in the past, can u confirm ur using a alix box as well?
-
Its not an mpd issue it is a netgraph issue.
I told you that my priorities are set and will come back to this when i can.For the mpd developers tell them that seems ng_ether has this issues with attaching/detaching interfaces or ng_iface.
Though there are some patches specifc to pfSense that might be needed to be tested as well. -
ok fine, no1 was replying so i thought it was forgotten completely.
bytheway few suggestions on the mpd forum helped a bit,regarding PADT packet which used to be sent when modem was down so they said to increase set link keep-alive value and so i did but if alix was connected to modem directly it wouldnt help but if connected through a switch then mpd would continue connection once modem was up again and i also tried setting the standard value of 60 for it and in that case also it would connect but after some time and had to goto interface and hit connect in which case mpd was killed and a fresh instance started. i have generated log for both and will keep with me till required.
meanwhile ill reply on mpd forum about it not being a mpd issue
-
bytheway mpd developers replied this
And what those pfSense-specific patches are? I personally run mpd as PPPoE client using stock FreeBSD 8.3-STABLE and vr1 interface at home and have no netgraph-related problems with it
-
they mentioned this as well
Ethernet card driver vr(4) is known to have major problems with traffic restoration after physical link down/up. This problem have nothing to do with mpd/netgraph. You need to contact FreeBSD developers or replace your hardware to get other type of NIC. Also, read this:
http://lists.freebsd.org/pipermail/freebsd-net/2012-August/033127.html
-
How I fixed it:
Changed my USB Ethernet adapter for a different chipset, PCI Ethernet adapter. Voila!Zentyal, ClearOS and even pfSense failed to reconnect while using a Linksys USB200M, but I've had this same problem using another USB adapter (Intellinet, different chipset… I don't remember which). Maybe it's tied to USB adapters?
-
I just installed pfsense (2.1-BETA1-4g-i386-nanobsd-20130507-1652.img.gz) on my Alix2d3 and I'm experiencing the same issue. Any news on a fix or workaround?
-
Ummm OK, here is my experience…
Yesterday my box crashed and burned :) So I build a new one from an old PC...It has 2 NICs. 1 realtek (vr0) and one Intel (em0).
Now, if WAN is on Realtek card it will never reconnect. But if on Intel card (em0) it will reconnect with no problem at all...
Before that I had 4 Intel 100 cards (fxp). It also worked like a charm.So my suggestion for pppoe user is, use Intel NIC for WAN and you should be just fine.
I do believe this is NOT mpd bug but driver bug.My 2 cents…
-
so considering a driver bug, how much would it cost to fix it or do the drivers need to be fixed from chipset manufacturer or freebsd?
-
Considering the multitude of Alix boards here not having any such problem, cannot see how's this a generic Realtek issue.
-
Considering the multitude of Alix boards here not having any such problem, cannot see how's this a generic Realtek issue.
Don't Alix boards have VIA NICs (not Realtek)?
-
yes they use VIA and im desperately ready to pay to get this fixed
-
Errr… let me try again since the message apparently got lost:
It has 2 NICs. 1 realtek (vr0) and one Intel (em0).
Now, if WAN is on Realtek card it will never reconnect. But if on Intel card (em0) it will reconnect with no problem at all…So, which is it?
-
Errr… let me try again since the message apparently got lost:
It has 2 NICs. 1 realtek (vr0) and one Intel (em0).
Now, if WAN is on Realtek card it will never reconnect. But if on Intel card (em0) it will reconnect with no problem at all…So, which is it?
alix boxes dont have realtek or intel nics at all, all r VIA chipset
-
via show as vr and realtek show as rl i guess
-
Yep, so… I'd wager Realtek really had nothing to do with the issue for that guy at least.
-
For whatever reason it only seems to be certain specific combinations of vr NICs + specific ISP/DSLAM equipment. Most people have no problems, but those that do seem to be isolated to vr NICs in that situation. We've had others report that in those cases adding a USB NIC, or swapping the NIC if it's not ALIX, has fixed it.
The ticket is still open here:
http://redmine.pfsense.org/issues/1943 -
realtek work fine for me always on same isp but this vr is an issue with almsot 4 different isps i have tested in 2 countries
