Is PPPOE working for you guys?
-
@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!
-
Actually it was just misconfigured, fixed the configuration, but still a no go
Apr 7 16:35:43 ppp: [opt2_link0] PPPoE connection timeout after 9 seconds Apr 7 16:35:43 ppp: [opt2_link0] Link: DOWN event Apr 7 16:35:43 ppp: [opt2_link0] LCP: Down event Apr 7 16:35:43 ppp: [opt2_link0] Link: reconnection attempt 1 in 4 seconds Apr 7 16:35:47 ppp: [opt2_link0] Link: reconnection attempt 1 Apr 7 16:35:47 ppp: [opt2_link0] PPPoE: Connecting to '*' Apr 7 16:35:56 ppp: [opt2_link0] PPPoE connection timeout after 9 seconds Apr 7 16:35:56 ppp: [opt2_link0] Link: DOWN event Apr 7 16:35:56 ppp: [opt2_link0] LCP: Down event Apr 7 16:35:56 ppp: [opt2_link0] Link: reconnection attempt 2 in 3 seconds Apr 7 16:35:59 ppp: [opt2_link0] Link: reconnection attempt 2 Apr 7 16:35:59 ppp: [opt2_link0] PPPoE: Connecting to '*' Apr 7 16:36:08 ppp: [opt2_link0] PPPoE connection timeout after 9 seconds Apr 7 16:36:08 ppp: [opt2_link0] Link: DOWN event Apr 7 16:36:08 ppp: [opt2_link0] LCP: Down event Apr 7 16:36:08 ppp: [opt2_link0] Link: reconnection attempt 3 in 3 seconds Apr 7 16:36:11 ppp: [opt2_link0] Link: reconnection attempt 3 Apr 7 16:36:11 ppp: [opt2_link0] PPPoE: Connecting to '*' Apr 7 16:36:20 ppp: [opt2_link0] PPPoE connection timeout after 9 seconds Apr 7 16:36:20 ppp: [opt2_link0] Link: DOWN event Apr 7 16:36:20 ppp: [opt2_link0] LCP: Down event Apr 7 16:36:20 ppp: [opt2_link0] Link: reconnection attempt 4 in 1 seconds Apr 7 16:36:21 ppp: [opt2_link0] Link: reconnection attempt 4 Apr 7 16:36:21 ppp: [opt2_link0] PPPoE: Connecting to '*' Apr 7 16:36:30 ppp: [opt2_link0] PPPoE connection timeout after 9 secondsTried rebooting pfsense and everything…
EDIT: Tried pfsense 1.2.3 livecd, and PPPOE is not an option of the interface I want... I think I rmemeber reading somewhere only the WAN interface can be PPPOE in pfsense 1.2.3
Just tried an old ass linksys router, and that worked. Shame pfsense, shame.
I have the same problem on RC1, just on WAN in my case .
Pfsense was connected about 13-14 hours and then got same error as this person above.
I unplugged WAN cable and connected it to notebook and was able to connect to internet using PPPOE on this notebook.
Then plugged again WAN cable to pfsense box and it connected without problems , so seems unplugging ethernet cable worked.
But it shouldn't be like that , I am not bot to stay near router 24h and unplug cable when needed >:( -
More info - WAN working now!
I have just upgraded by pfsense 1.2.3 install to “pfSense-Full-Update-2.0-RC1-i386-20110521-2001”.
After the upgrdae, my WAN connection stayed down. I did some more digging and found the cause – or fix. Enabeling the “configure null servicename” option brings my WAN connection back to life.Even though I found a way to get it working, I’d be very happy if you could have a look at my step-by-step description below.
I did spot a few errors, and a rather big useability problem, realted to that null service name option.1.went to “Interfaces –> “WAN”
2.username and password were present
3.servicename field was empty (as in my 1.2.3 config) – imo. inconsitent config screen, “Configure a NULL Service name” missing
4.IDLE timout was empty
5.entered “Advanced MLPPP”
6.Linktype PPPoE –> Correct
7.Link interface –> em1 –> correct
8.username and password present
9.service name –> empty as in my 1.2.3 config
10.enabled “Configure a NULL Service name”
11.pressed “save”
12.“Idle Timeout not configured”
13.opened “advanced options” and entered “0”
14.pressed “save” again"
15.“interface not assigned”….. this was set to em1
16.selected interface “em1” again
17.pressed “save”
18.went over to “status – interfaces”
19.WAN “down”
20.pressed “connect”
21.now wan is finally up and i got an IP!
22.went back to “Interfaces –> “WAN”
23.“Idle Timeout” –> empty, even though I configured “0” beforeI see several problems in 2.0 RC1 after the upgrade:
Step 15: the interface assigment got lost when trying to save the config without the “Idle Timeout” set
Step 23: the “Idle Timeout” is empty, even though it was set to “0”
“Idle Timeout”: when the field is empty, shouldnt that be simply detected as “0” = dissabled? – far better useability imo.“configure null servicename”:
- not available inside “Interfaces WAN” – user can not be expected to know that it is only inside the advanced screen
- not automatically enabled after an upgrade from 1.2.3 where the servicename was empty – root cause of my issue
But the better question is why there even is such an option now in 2.0? Without knowing the reason why you added this option, I can only say that in my opinion, that option should be removed, and PfSense should detect the emtpy servicename field and enable the behaviour which “configure null servicename” would trigger. This option only causes huge useability issues right now. Especialy with the "inconsitent" config screens.
I fear that once 2.0 gets final, you will get a lot more reports from users who upgrade from 1.2.* and end up with a "down" wan because of this "problem".
I hope that my feedback is of use for you to improve PfSense even further. :)
regards,
Chris -
Some of this is copied from the e-mail I sent back to you, but others may find it useful as well:
Leaving the service name blank sends no service name to the ISP at all. Sending a null service name sends a name and that name is blank. You can check that by looking at /var/etc/mpd_<interfacename>.conf with the option checked/unchecked. Those are two distinct things.
The option isn't there on the main PPPoE config screen because that is an "advanced" (read: not normally needed) option and it is different than leaving the service name blank. Some services may not work with sending the null service name, but there may not be a good way to tell.
As for why it worked on 1.2.3 and not on 2.0, it may be the difference in the MPD version used on both systems.
The errors you saw when changing options there is definitely not normal though, but that is a separate issue from what you are seeing here. We usually discourage editing any settings on the PPP tab but in your case you have to.
It would also help to see your /var/etc/mpd_<interfacename>.conf files when it is broken and when it works, with the username/password blanked
out of course.</interfacename></interfacename> -
Actually it was just misconfigured, fixed the configuration, but still a no go
Apr 7 16:35:43 ppp: [opt2_link0] PPPoE connection timeout after 9 seconds Apr 7 16:35:43 ppp: [opt2_link0] Link: DOWN event Apr 7 16:35:43 ppp: [opt2_link0] LCP: Down event Apr 7 16:35:43 ppp: [opt2_link0] Link: reconnection attempt 1 in 4 seconds Apr 7 16:35:47 ppp: [opt2_link0] Link: reconnection attempt 1 Apr 7 16:35:47 ppp: [opt2_link0] PPPoE: Connecting to '*' Apr 7 16:35:56 ppp: [opt2_link0] PPPoE connection timeout after 9 seconds Apr 7 16:35:56 ppp: [opt2_link0] Link: DOWN event Apr 7 16:35:56 ppp: [opt2_link0] LCP: Down event Apr 7 16:35:56 ppp: [opt2_link0] Link: reconnection attempt 2 in 3 seconds Apr 7 16:35:59 ppp: [opt2_link0] Link: reconnection attempt 2 Apr 7 16:35:59 ppp: [opt2_link0] PPPoE: Connecting to '*' Apr 7 16:36:08 ppp: [opt2_link0] PPPoE connection timeout after 9 seconds Apr 7 16:36:08 ppp: [opt2_link0] Link: DOWN event Apr 7 16:36:08 ppp: [opt2_link0] LCP: Down event Apr 7 16:36:08 ppp: [opt2_link0] Link: reconnection attempt 3 in 3 seconds Apr 7 16:36:11 ppp: [opt2_link0] Link: reconnection attempt 3 Apr 7 16:36:11 ppp: [opt2_link0] PPPoE: Connecting to '*' Apr 7 16:36:20 ppp: [opt2_link0] PPPoE connection timeout after 9 seconds Apr 7 16:36:20 ppp: [opt2_link0] Link: DOWN event Apr 7 16:36:20 ppp: [opt2_link0] LCP: Down event Apr 7 16:36:20 ppp: [opt2_link0] Link: reconnection attempt 4 in 1 seconds Apr 7 16:36:21 ppp: [opt2_link0] Link: reconnection attempt 4 Apr 7 16:36:21 ppp: [opt2_link0] PPPoE: Connecting to '*' Apr 7 16:36:30 ppp: [opt2_link0] PPPoE connection timeout after 9 secondsTried rebooting pfsense and everything…
EDIT: Tried pfsense 1.2.3 livecd, and PPPOE is not an option of the interface I want... I think I rmemeber reading somewhere only the WAN interface can be PPPOE in pfsense 1.2.3
Just tried an old ass linksys router, and that worked. Shame pfsense, shame.
I have the same problem on RC1, just on WAN in my case .
Pfsense was connected about 13-14 hours and then got same error as this person above.
I unplugged WAN cable and connected it to notebook and was able to connect to internet using PPPOE on this notebook.
Then plugged again WAN cable to pfsense box and it connected without problems , so seems unplugging ethernet cable worked.
But it shouldn't be like that , I am not bot to stay near router 24h and unplug cable when needed >:(exact same above issue, haven't been able to solve it till date, any help? actually mu alix connects to the isp fiber optic device using pppoe, now suppose for some reason i unplug the fiber optic device or it reboots or something like that then pfsense wont connect and keep going in loops and the only way to make it connect is by rebooting only.
-
basically when pfsense boots, the steps it follows to connect to pppoe seem different than when a link is brought down and then it loops trying to reconnect and thats where i think this bug is and many like me suffer coz in older version, lower than pfsense v2, it used to work perfectly fine and it did also reconnect fine so basically the link was up at all times and recovered from a failure.
-
should it be considered that this cant be solved at all?
-
There is always the possibility that it can be solved, we just need more detail. If the behavior is different when it first logs in vs when it reconnects, the logs should be different as well.
-
im always ready to provide details but ill need some commands etc so i can post the results to u.
actually when pf reboots, that time it connects perfectly fine without any issues at all but if my fiber optic device from isp reboots or if i click the disconnect from the web gui then it wont connect and the connection attempt keeps going in loops.
i can provide the access to my box if u require or u can simply tell me the commands etc to run so i can get u those results based on the replicated scenario.
-
No real commands to run. Check /var/etc/mpd_<interfacename>.conf when it works and when it doesn't, post them here (with your username and password removed/redacted). Also check the system logs when it works and when it doesn't, there should be log entries there about what it's doing.</interfacename>
-
No real commands to run. Check /var/etc/mpd_<interfacename>.conf when it works and when it doesn't, post them here (with your username and password removed/redacted). Also check the system logs when it works and when it doesn't, there should be log entries there about what it's doing.</interfacename>
the configuration wise i tried with that nulls ervice name etc but like i said, on reboot of pfsense it conencts fine but after that if i do it manually or happens by isp then the reconnection attempt just keeps looping, this issue is since the change of mpd and i personally feel there is some difference in the way it connects during boot compared to if done manually or happens due to disconnection.
the conf file is as below which i have used since a long time, used to work with older mpd in v1.2.3
startup: # configure the console set console close # configure the web server set web close default: pppoeclient: create bundle static wan set iface name pppoe0 set iface route default set iface disable on-demand set iface idle 0 set iface enable tcpmssfix set iface up-script /usr/local/sbin/ppp-linkup set iface down-script /usr/local/sbin/ppp-linkdown set ipcp ranges 0.0.0.0/0 0.0.0.0/0 set ipcp no vjcomp #log -bund -ccp -chat -iface -ipcp -lcp -link create link static wan_link0 pppoe set link action bundle wan set link disable multilink set link keep-alive 10 60 set link max-redial 0 set link disable chap pap set link accept chap pap eap set link disable incoming set link mtu 1492 set auth authname "username" set auth password passwod set pppoe iface vr1 open
