Is PPPOE working for you guys?
-
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.
-
@cmb:
the config upgrade code has no ability to change the password, you had to have changed it at some point.
Here is what I did:
1. restored an image (TrueImage) of 1.2.3 final
2. started PC
3. 1.2.3 was working - WAN was up
4. downloaded latest build of 2.0RC
5. created/exported a backup of 1.2.3 config
6. upgraded to 2.0 RC
7. after upgrdae was done, PfSense started up
8. WAN was down
9. pressed "connect" in the interfaces dialog
10. WAN stayed down
11. created/exported a backup of 2.0 RC config
12. attached both config backups to this thread
13. restored an image (TrueImage) of 1.2.3 finalAt no point, I even entered the WAN configuration of 2.0RC when I did the upgrade to export the logs. :-/
Additional information:
The WAN-PPPoE user and password was changed by my ISP ~8 months ago.
Is it possible that this old info is still stored "somewhere" in 1.2.3 and the upgrade takes that instead of the new one which is configured and working in 1.2.3? -
aaaaaand just did it one more time.
1. working 1.2.3 setup
2. upgraded to pfSense-Full-Update-2.0-RC1-i386-20110518-1955.tgz
3. upgrade finishes
4. WAN stays downas i said, I did not touch any config at all.
what now? -
Can you e-mail me the before and after configuration from latest try?
jimp (at) pfsense <dot>org.
I committed some fixes a few weeks ago for the PPPoE WAN upgrade, it worked in my (admittedly limited) testing.</dot>
-
If you have an empty 'Service name' in your configuration try to check 'Configure a NULL Service name' on the PPPs configuration page. It is not available on the WAN configuration page so it's easy to miss it.
-
If you have an empty 'Service name' in your configuration try to check 'Configure a NULL Service name' on the PPPs configuration page. It is not available on the WAN configuration page so it's easy to miss it.
That is correct, the 1.2.3 config does not have an service name set - my ISP does not require that.
Will have a look at this option in 2.0.@jimp
I will have a look at this service name option and get back to you then. :)Thanks for your help guys!
