Upgrade from 12/13 to 12/18 -> PPPoE dead…
-
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.
-
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.
Also with your WAN as an additional OPT interface for modem access?
-
No. WAN was not and is not as additional Interface assigned.
Uh, now i see, the old snap to which i reverted was NOT 01/15, it was 01/07! Sorry for that wrong info!!!!!
-
I never had problems with PPPoE when I disabled the additional OPT…
-
i'll try with assigning the WAN as OPT and report back.
report:
I assigned my WAN-if as OPT, but nothing more. Didn't assign anything to that if.
rebooted pfSense.
After reboot my PPPOE connected as normal. No problems. Connection was made automatically.At advanced options of my PPPOE nothing is activated. So no "Dial on demand", no "idle tieout", nothing ticked.
My WAN-if is xl0, an old 3com in a dell home-pc. Its an onboard-card. Hope that helps. If you want some more testing from my side, tell me. What i see, the problems with PPPOE are in my case gone. -
I just updated to last snap from 1/21 and still have to manually connect.
Are you using OPTX interface(s) for modem management? I just committed an update that will prevent detachment of netgraph nodes on interfaces that are used by PPPoE and also configured as an OPTX interface (netgraph nodes are necessary on interfaces that are used by PPPoE/PPTP/L2TP/MLPPP)
The way the code is was written before, it would detach the netgraph node from the underlying interface if you assigned that same physical interface to OPTX.
Warning . . . my update is untested since I don't have access to my PPPoE link right now (I'm away from home). . .
@_igor_: the problem doesn't have anything to do with whether your WAN link is called WAN or OPTx, it's related to having PPPoE configured on a physical interface (e.g. em0) and having OPTx configured on the same physical interface (e.g. em0).
In future posts, everyone please state if you have configured the same physical interface for both PPPoE/MLPPP/PPTP/L2TP (WAN) and OPTx(static/dynamic) (e.g. for modem management.)
Thanks,
GB -
OPT6-OPT13 (vlans on em0) – mlppp WAN + static (modem subnets)
Are you using OPTX interface(s) for modem management?
Yes. I have no choice because said interfaces are vlan interfaces, and they aren't eligible for inclusion in the mlppp bundle without first assigning them IP info and activating them.
I just committed an update that will prevent detachment of netgraph nodes on interfaces that are used by PPPoE and also configured as an OPTX interface (netgraph nodes are necessary on interfaces that are used by PPPoE/PPTP/L2TP/MLPPP)
So if I understand you correctly your fix won't work for me because I'm using mlppp. Is that correct?
I'll try your fix if you think there's a chance of it working, or I can get you LAN access to this install if you want to investigate some. The biggest inconvenience there is that it would have to be between midnight and 7 am MST, as I have a lot of daytime users.
