Upgrade from 12/13 to 12/18 -> PPPoE dead…
-
Yeah, it's still broken for people who have their modem interface assigned.
No changes have happened that would try to fix it though, so it isn't likely to start working for others until a fix gets committed.
-
With 2.0-BETA5 (i386) built on Sat Jan 15 02:40:01 EST 2011
It works! Very cool!
-
Except that there were still no changes that would have impacted that functionality…
You might look closer into why the last two Saturday updates seem to have worked for you but nothing in between. Perhaps the timing on your part has more to do with it than anything we've changed. :-)
-
With 2.0-BETA5 (i386) built on Sat Jan 15 02:40:01 EST 2011
It works! Very cool!
And you have enabled OPTx(WAN) in order to access your modem through that?
-
My setup is
wan (em0) –- pppoe --- dsl router---internet
dsl (opt) (em0) ---------So yes, I have an opt interface connected to my dsl router as well as a pppoe connection for the wan using same phy interface em0
Romain
-
My setup is
wan (em0) –- pppoe --- dsl router---internet
dsl (opt) (em0) ---------So yes, I have an opt interface connected to my dsl router as well as a pppoe connection for the wan using same phy interface em0
Romain
Thanks. I'll check with the latest snap if it works for me now as well….
-
Except that there were still no changes that would have impacted that functionality…
You might look closer into why the last two Saturday updates seem to have worked for you but nothing in between. Perhaps the timing on your part has more to do with it than anything we've changed. :-)
Sure, I will try to investigate why it is working now even if no code changes have been made concerning this issue. Thanks for the info!
-
It is not working (probably because there were no changes at all) with OPT enabled for Modem access on WAN. As soon as I enabled the OPT interfaces my PPPoE was brought down and I had the same problem as always. PPP trying to connect all the time…
Did not even try to do an update then... -
Hi Guys,
Try commenting out line 2620 in /etc/inc/interfaces.inc. (" interface_netgraph_needed($interface); ") (add a // to the front of the line to make it a comment.).
GB
-
Hi Guys,
Try commenting out line 2620 in /etc/inc/interfaces.inc. (" interface_netgraph_needed($interface); ") (add a // to the front of the line to make it a comment.).
GB
Hi m8,
yeah, that works! What does this function do? Is that easy to fix now? I didn't do a firmware upgrade now, but I activated OPT for modem access and rebooted. As soon as my pfSense box was reachable I saw that the PPPoE connection was up as well….
Nice!
-
That function was added as an optimization for very high bandwidth interfaces that don't need netgraph nodes, but apparently, more interfaces need the nodes attached than the function allows.
GB
-
Thanks for the clarification. Can somebody now 'fix' this? Or is this more complicated than commenting that out? Am I right that every update will change that file to the original state?
-
The underlying function needs fixed, not removed. So it's a bit more complex than just commenting out one line.
Until it's fixed in our repo this workaround would have to be repeated after each update.
-
Hmmm try this
http://tinyurl.com/6cfx2ja seems i was doing a check wrong. -
Hi ermal,
no, that doesn't work for me. I removed the // from line 2620 and applied your fix. Still not connecting when booting up. Had to remove my opt interface again and click save on WAN…
-
With update from 01/18 i lost my PPPOE completely. Had more problems while updating packages. After a while of working state PPPOE was lost. And never came back. Nor a downgrade to 01/15 resolved the problem.
Tried that edit from interfaces.inc with no success.
Its an i386 install, XL0 is not assigned (its my WAN.) Only LAN, no opt nor other interfaces present. PPP-log only retries to connect. Only tries to connect show up at the logs. No errors so far, nor success.Packages present: squid, squidguard, lightsquid, cron and OVPN-Exporter. Nothing more.
So at last i was caught too with this failure of PPPOE. :-(
-
Is this still a problem? I'm still running a snap from the 12th, not planning to update unless there's hope for a change (for this or the panic problem)..
-
At least for me, the issue is still there from the latest yesterday's snap.
-
I could get rid of that problem:
Downgraded to snap from 01/15, there i had connect, from this snap i updated (as a test) to snap from 01/20. Still now (snap is from 01/21) its working. Lastly i don't know why, but it works. Strange. I'm happy so.
-
I just updated to last snap from 1/21 and still have to manually connect.
