PPPoE reconenction fix - mpd fix ($100)
-
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
-
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
It works with a switch in between?
-
ys because that way the port never goes down, the issue is when its connected to the isp fiber optic modem and that power offs which results in the port going completely down or some wierd state after which when on the packets from mpd never reach the isp at all inspite of port being on again
-
Sounds like a $5 solution….
-
switch solves the issue but isnt the proper solution.
its like some1 saying adding a switch to a switch to make a network connection for a PC but all u end up with is unnecessary switches when the PC can connect to the first switch directly or a better eg would be like adding a switch to connect 2 cat5 cables when u can simply plug in a coupler
-
It might not be a proper solution, however, lets be realistic here. This probably will not ever get solved. Assumes a whole LOT more detail on the HW involved plus - I'm afraid - involves getting developers to get their hands on that very HW/ISP connectivity for testing/debugging. So, however harsh that may sound - certainly not a question of a $100 bounty.
-
the reason this thread is still active because the developer has the redmine ticket still open as well as ermal last time said he would come back to this issue so was just checking as that post was quiet some time ago.
if its never going to be fixed then they might simply close this bounty as well as the redmine ticket once and for all
-
It's worth leaving open yet, there is a chance it may work again once we get 2.2 snapshots going on FreeBSD 10.x, newer driver set an all.
-
any eta on when thats going to happen?
the weird thing about this issue is that even the most crappiest routers in the market dont suffer this issue so it all cant be blamed on the DSLAM, if it was that then most other routers would also suffer that
-
No ETA on usable 10.x images. Could be months.
And the problem is a combination of factors - Specific Modem/ISP/DSLAM + Specific driver
-
to what i noticed is its just VIA drivers because it works fine with realtek, the isp modem i tested were 3 different types, zhone, huawei and cisco and it was same on all three, via chipset causing it, dslam which i tested was unisphere and the other was some unknown brand so the dslam, modem changed in all situations but alix was common so it suffered, i have 2 other pfsense full installs on the same isp using realtek and they work fine and always connect everytime
-
Wow, I missed this thread :)
Sorry for late reply…
Yes, vr0 had problems, DSLAM is UNISPHERE...
Dlink, realtek, intel and broadcom nics all worked great...
VIA on-motherboard NICs failed to connect...I tested all possibilities, from power outages to just cable disconnect and vr0 failed every time and others worked just fine EVERY time...
Regards,
Greg -
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 or no rather than wait for months for this to resolve coz its already over 2 years now
-
Well, I replaced my nics with Intel ones and that was it….
I needed stable system and Intel gave me that... -
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.
