Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Is PPPOE working for you guys?

    Scheduled Pinned Locked Moved General pfSense Questions
    75 Posts 21 Posters 41.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      wallabybob
      last edited by

      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.

      1 Reply Last reply Reply Quote 0
      • I
        infinityloop
        last edited by

        @Derek:

        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?

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          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).

          1 Reply Last reply Reply Quote 0
          • I
            infinityloop
            last edited by

            @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. :)

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              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.

              1 Reply Last reply Reply Quote 0
              • I
                infinityloop
                last edited by

                @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! :)

                1 Reply Last reply Reply Quote 0
                • I
                  infinityloop
                  last edited by

                  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.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cmb
                    last edited by

                    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.

                    1 Reply Last reply Reply Quote 0
                    • I
                      infinityloop
                      last edited by

                      @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!

                      1 Reply Last reply Reply Quote 0
                      • C
                        cmb
                        last edited by

                        the config upgrade code has no ability to change the password, you had to have changed it at some point.

                        1 Reply Last reply Reply Quote 0
                        • I
                          infinityloop
                          last edited by

                          @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 final

                          At 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?

                          1 Reply Last reply Reply Quote 0
                          • I
                            infinityloop
                            last edited by

                            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 down

                            as i said, I did not touch any config at all.
                            what now?

                            1 Reply Last reply Reply Quote 0
                            • jimpJ
                              jimp Rebel Alliance Developer Netgate
                              last edited by

                              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>

                              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                              Need help fast? Netgate Global Support!

                              Do not Chat/PM for help!

                              1 Reply Last reply Reply Quote 0
                              • A
                                azzido
                                last edited by

                                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.

                                1 Reply Last reply Reply Quote 0
                                • I
                                  infinityloop
                                  last edited by

                                  @azzido:

                                  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!

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    Mitar
                                    last edited by

                                    @jigglywiggly:

                                    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 seconds

                                    Tried 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  >:(

                                    1 Reply Last reply Reply Quote 0
                                    • I
                                      infinityloop
                                      last edited by

                                      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” before

                                      I 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

                                      1 Reply Last reply Reply Quote 0
                                      • jimpJ
                                        jimp Rebel Alliance Developer Netgate
                                        last edited by

                                        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>

                                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                        Need help fast? Netgate Global Support!

                                        Do not Chat/PM for help!

                                        1 Reply Last reply Reply Quote 0
                                        • X
                                          xbipin
                                          last edited by

                                          @Mitar:

                                          @jigglywiggly:

                                          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 seconds

                                          Tried 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.

                                          1 Reply Last reply Reply Quote 0
                                          • X
                                            xbipin
                                            last edited by

                                            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.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.