Upgrade from 12/13 to 12/18 -> PPPoE dead…
-
Can confirm this now. Did an update to the latest 1/10 snap and disabled my vr1 interface for modem access before. Now the PPPoE connection comes up perfectly fine…
-
So far the only people having confirmed the issue in this thread also have their physical interface assigned to access the modem for convenience.
Depends on your definition of convenience. You cannot assign a vlan interface to pppoe (at least not mlppp, anyway) without first activating that interface. So in my case, convenience means not building/buying hardware with 9 NICs (8 for modems, 1 for internal vlans).
The workaround works, but is a little bush-league for something that is going RC. What if pfsense is rebooted for some reason and I don't have LAN access? Yeah, I have battery backup, but things happen. Yeah pfsense is stable, but sometimes things just lock. Yeah, this is beta and we expect hiccups along the road, but at some point (and it looks like that point is rapidly approaching) 2.0 will be RC and then release, so that excuse will shortly not be an excuse.
I'm not complaining that this is an issue today. I'm using beta and I can live with the warts. I'm just saying that we'd be wrong to sweep this under the carpet on the cusp of a release. I wish I had more skill to help, but for now all I can do is provide feedback and test proposed fixes. God speed.
-
Well nobody said it wasn't being worked on. :-)
It's being worked on, but if someone is saying it's a critical bug for them at this very moment, there are workarounds.
-
The workaround works, but is a little bush-league for something that is going RC. What if pfsense is rebooted for some reason and I don't have LAN access? Yeah, I have battery backup, but things happen. Yeah pfsense is stable, but sometimes things just lock. Yeah, this is beta and we expect hiccups along the road, but at some point (and it looks like that point is rapidly approaching) 2.0 will be RC and then release, so that excuse will shortly not be an excuse.
As for this, others have said it does connect if you wait a few minutes. Seems if that is the same for others it's not quite as critical as others are painting it. Yes, it's a problem that needs solved, but it isn't like it's dead in the water.
-
As for this, others have said it does connect if you wait a few minutes. Seems if that is the same for others it's not quite as critical as others are painting it. Yes, it's a problem that needs solved, but it isn't like it's dead in the water.
That's what I figured, and I'm happy with that. Thanks for clarifying.
-
with 2.0-BETA5 (i386) built on Mon Jan 10 13:14:45 EST 2011
I had to manually click on the 'connect' button to start pppoe.Just to let you know.
Thanks -
Build 2.0-BETA5 (i386) built on Mon Jan 10 22:34:12 EST 2011 didn't automatically connect my PPPoE link, although I only waited 10 minutes.
I have now disabled the OPTn interface I was using to access my bridged modem, and have successfully followed the steps at http://doc.pfsense.org/index.php/How_can_i_access_my_PPPoE_Modem_on_WAN to access my modem.
pfSense is an excellent product, and my thanks to the people who support and improve it through these forums for all of their help.
-
autoreconnect appears to do so, just that it may take a couple of minutes… maybe its just me, i dont know
-
It just takes some minutes if you have enabled your WAN interface as OPT…
-
my wan interface isnt opt. no funny stuff now. just pppoe and thats it.
i do have opt1, but thats on another interface.
-
With php: 2.0-BETA5 (i386) built on Tue Jan 11 14:19:18 EST 2011
Jan 11 20:58:50 ppp: [wan_link0] Link: reconnection attempt 131 in 2 seconds Jan 11 20:58:50 ppp: [wan_link0] LCP: Down event Jan 11 20:58:50 ppp: [wan_link0] Link: DOWN event Jan 11 20:58:50 ppp: [wan_link0] can't remove hook mpd10010-0 from node "[17]:": No such file or directory Jan 11 20:58:50 ppp: [wan_link0] PPPoE: can't connect "[17]:"->"mpd10010-0" and "[15]:"->"left": No such file or directoryGot to use the 'connect' button to have my wan/pppoe link working.
Strange because the release from the 8th worked for me.
-
Still having the issue with the release from the 13th. So far, the last that works for me was the release from the 8th of january
Romain -
Try to do a complete reinstall with the latest snap. It works for a long time now here on my Alix…
-
Try to do a complete reinstall with the latest snap. It works for a long time now here on my Alix…
Didn't you remove your modem access opt interface though?
-
Yes I did and that why it is working…
-
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
