Is PPPOE working for you guys?
-
jigglywiggly,
I was having the same issue on 2.0. Somehow the interfaces & PPP sections get out of sync or something. I ended up setting all PPPoE interfaces to non PPPoE, saved & applied. Went & deleted all PPP entries, rebooted, checked logs to make sure there were no PPPoE attempts then changed each interface back to PPPoE entering settings on that screen & saving WITHOUT clicking on advanced 'click here' link as that might be what I did to muck it up. Also, I noticed one of my WAN connections requires NULL service namje box to be checked but that is only available on the PPP settings screen itself not on the interface screen. (It says you can leave it blank but it doesn't work for me if left blank).PPPoE on multiple wan's seems to work great in 2.0 once you get past the hurdles (WHATEVER YOU DO, DO NOT PICK THE WRONG INTERFACE ON PPP SCREEN! I did that & pfsense would no longer boot! It'd get to some screen where it was trying to bind to the pppoe & puke with cryptic messages. I ended up having to reinstall pfsense so glad it was a test box.) but seems the web interface still has some work to be done. In meantime trick seems to be to avoid clicking advanced (especially when initially setting up or the linked PPP is foobar), avoid entering values in fields you don't use (DoD & idle timeout fields were a bitch for me once I made mistake of entering 0 & what seemed no going back) and realizing it might require deleting them & starting over like I described above if some stray setting gets saved on accident. :D (That odd logging you posted seems to be tell-tale sign PPP is F'd & needs above to start over)
Bill -
Good news, I've decided to not use pfsense for pppoe at all and just let my modem handle it after reading that post :P
-
I am and it is working reliably now. Was a bit of a pig to setup however, i think it had something to do adding a new pppoE connecting then assigning it to the interface rather than setting the interface to pppoE ( I cant remember the exact screens!)
I do know one thing though, first time round it took upto 15mins to connect. Im not sure if it was something to do with the sessions at the ISP but after days of messing it eventually just connected all by itself.
PS my log looked just like that too. Try tunning tpcdump -i <interface name="">you should see a few PADI packets going by.</interface>
-
Hello,
I've exactly the same behaviour jigglywiggly had in his 3rd message.
Whatever way I use to configure PPPoE gets me to the same result:
ppp: [wan_link0] Link: reconnection attempt 3 in 3 seconds
ppp: [wan_link0] Link: reconnection attempt 3
ppp: [wan_link0] PPPoE: Connecting to '*'
ppp: [wan_link0] PPPoE connection timeout after 9 seconds
ppp: [wan_link0] Link: DOWN event
ppp: [wan_link0] LCP: Down event
I tried by setting the "configure NULL service name" check box on and off.The physical configuration is exactly the same I used before with 1.2.3 (modem in bridge mode, connected to vr1 port of an Alix 2D13 board through HP switches on VLAN 10) and that worked flawlessly.
I've tried various ways to configure this connection:
- directly in the WAN interface (set it to PPPoE, configure)
- indirectly, using the assign method, first create a PPPoE session on vr1, than assign PPPoE(vr1) to WAN
- indirectly through VLAN, create the VLAN tag, assign OPTx to this, create the PPPoE session on OPTx assign PPPoE(OPTx) to WAN)
None of these get further than "PPPoE connection timeout after XX seconds" (interfaces are correctly assigned - I had the second log message of jigglywiggly too).
Nothing else than this laconic error comes in logs.
Could someone come with an hint or give me a direction about what I could try?Thanks
ChristOff -
Hi all,
I've had problems few days ago too with PPPOE, was transferring my old backup file to a new machine.
After going through the logs, i remember that the interfaces were the issues.
And i double checked and found out that the Bridge setting for WAN and LAN was gone on the new machine.
So I went back to the new machine, corrected the interfaces, and added the Bridge. It solved my problem.
-
Thanks for your reply Newgen.
I hadn't any bridge before (and don't understand why I would want one between Wan and Lan, as this is where I should have routing).
Did it solve PPPoE timeout errors for you? -
My PPPOE didn't work at all before I bridge the Wan and Lan interfaces.
So yes, it did solve my problem.
Why not just give it a try and repost logs that you get.Cheers
-
i've tried setting up pppoe on my machine and here is a snippet of the system log after trying to get it working
May 2 15:44:29 php: : rc.newwanip: Informational is starting xl0.
May 2 15:44:29 php: : rc.newwanip: on (IP address: 99.102.185.18) (interface: wan) (real interface: xl0).
May 2 15:44:30 php: : The command 'route add -host 99.102.185.1' returned exit code '1', the output was 'route: writing to routing socket: Invalid argument add host 99.102.185.1: Invalid argument'
May 2 15:44:30 php: : Resyncing configuration for all packages.
May 2 15:44:32 php: : ROUTING: change default route to 99.102.185.1
May 2 15:44:33 check_reload_status: reloading filter
May 2 15:44:33 apinger: Starting Alarm Pinger, apinger(2755) -
I can not get PPPoE to work at all
In my opinion, the setup of wan connections got extremely more complex in 2.0.
Tested yesterdays svn build of 2.0RC1 to see if PPPoE is finally working and it is still not…. :S
Interfaces -> assign -> PPP's -> edit interface which is from 1.2.3
NO INTERFACES ARE SELECTABLE - until I re-select PPPoE AGAIN in the drop down list.
Why does WAN and LAN appear there? thats not a physical interface. :S
Entered the username and pass.But even then, PPPoE is not working:
System log reports this when trying to connect: May 5 22:02:20 - php: : Could not find gateway for interface(wan).Reverted to the iamge i took from 1.2.3. That one is working nicely and one hell of a lot easier to setup PPPoE.
-
Tested yesterdays svn build of 2.0RC1 to see if PPPoE is finally working and it is still not…. :S
It's working perfectly for me on RC1. Interfaces, Wan, PPPoE, enter username/password and choose details, and it's been up without issues. Including over a few firmware updates. :)
-
I have had no problems with pppoe on pfSense 2.0 including changing from pppoe over a physical interface to pppoe over a VLAN. I upgraded from pfSense 1.2.3 but didn't start using ppp until some months after the upgrade.
-
Tested yesterdays svn build of 2.0RC1 to see if PPPoE is finally working and it is still not…. :S
It's working perfectly for me on RC1. Interfaces, Wan, PPPoE, enter username/password and choose details, and it's been up without issues. Including over a few firmware updates. :)
May I ask which build you are running?
I have:
- em0 - Lan
- em1 - wan
What I did was:
1. Interfaces -> assign -> PPP's -> edit interface
2. inside that present (migrated) PPPoE, there is no interface (em0 / em1) selectable.
3. at least not as long as i tick the dropdown menu where PPPoE is selected, and select PPPoE again.
4. then it lists all interfaces (including LAN and WAN…. :S) and I can select em1
5. i then add user and pass for PPPoE, but still. it does not work - the wan stays down - manually trying to connect only results in log as seen in 6. and status = "down"
6. System log reports this when trying to connect: May 5 22:02:20 - php: : Could not find gateway for interface(wan).am I missing some step in setup of PPPoE in 2.0?
-
The new PPP capabilities for MLPPP and other circumstances apparently has left some issues with lacking input validation that allows invalid configurations in a way that some people are screwing up. I've yet to determine exactly what that is.
If it's not working, reset to defaults, assign interfaces after the reboot, log into the web interface on LAN, when going through the setup wizard configure your PPPoE info, and you're done. Don't ever touch PPP-related settings outside of Interfaces>WAN (or whichever interface is your PPPoE WAN) unless you have reason to (such as MLPPP).
-
@cmb:
The new PPP capabilities for MLPPP and other circumstances apparently has left some issues with lacking input validation that allows invalid configurations in a way that some people are screwing up. I've yet to determine exactly what that is.
Can I help you with finding out what causes this?
I have reverted back to an working image of 1.2.3. So I can upgrade to any build of 1.2.0 RC easiely.I can give you the files/info pre and post the upgrade. Just tell me which. :)
-
If you can get a backup of a config that isn't working that could help. You can email it to me (cmb at pfsense dot org) with a link to this thread.
-
@cmb:
If you can get a backup of a config that isn't working that could help. You can email it to me (cmb at pfsense dot org) with a link to this thread.
Will do that doring the weekend when I get back from my business trip. Thanks for your help! :)
-
Here are conf backups of 123 before the upgrade and from 2.0RC after the upgrade. PPPoE was not working after the upgrade - could not connect
If you need any further infos/files please let me know! :)
edit
.zip not allowed as attachment? :S
neiter is .xml….. so i had to rename the backup to .txt. -
Removed the attachments since you posted your ISP password and other things you don't want public to the world, that's why I requested them via email.
There aren't any config issues there, the 2.0 config is fine. Your password isn't the same in the 2.0 config as it is in the 1.2.3 config. Maybe that's the issue.
-
@cmb:
Removed the attachments since you posted your ISP password and other things you don't want public to the world, that's why I requested them via email.
oops thanks!
@cmb:
There aren't any config issues there, the 2.0 config is fine. Your password isn't the same in the 2.0 config as it is in the 1.2.3 config. Maybe that's the issue.
I did not touch the configuration after the upgrade to 2.0. So whatever the password is in the 2.0 config, it was set by the upgrade routine.
Any idea why this happens?After the first upgrade (the conf files were from the 2nd attempt), I did set the PPPoE user and pass again manually - yet the WAN did stay "down" still.
Will have a look again this evening.
Thanks for your help! -
the config upgrade code has no ability to change the password, you had to have changed it at some point.