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.8k 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.
    • 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
            • X
              xbipin
              last edited by

              should it be considered that this cant be solved at all?

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

                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.

                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

                  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.

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

                    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>

                    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

                      @jimp:

                      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
                      1 Reply Last reply Reply Quote 0
                      • jimpJ
                        jimp Rebel Alliance Developer Netgate
                        last edited by

                        And there is no difference in that config at all when it works and when it doesn't?

                        The logs would probably be more helpful then.

                        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

                          config changes i tried almost all available combinations in the web interface. earlier there was an issue in being able to connect with vjcomp turned on which i had to disable but i reported that to the isp and they provided a global firmware upgrade to their devices and switching that to on or off doesn't cause any issues any more.

                          below is the log when i switch off my isp provided fiber optic device and switch it back on, some what similar to cable unplug

                          Jun  4 20:12:41 firewall ppp: [wan_link0] LCP: no reply to 1 echo request(s)
Jun  4 20:12:51 firewall ppp: [wan_link0] LCP: no reply to 2 echo request(s)
Jun  4 20:13:01 firewall ppp: [wan_link0] LCP: no reply to 3 echo request(s)
Jun  4 20:13:11 firewall ppp: [wan_link0] LCP: no reply to 4 echo request(s)
Jun  4 20:13:21 firewall ppp: [wan_link0] LCP: no reply to 5 echo request(s)
Jun  4 20:13:21 firewall ppp: [wan_link0] LCP: peer not responding to echo requests
Jun  4 20:13:21 firewall ppp: [wan_link0] LCP: state change Opened --> Stopping
Jun  4 20:13:21 firewall ppp: [wan_link0] Link: Leave bundle "wan"
Jun  4 20:13:21 firewall ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Jun  4 20:13:21 firewall ppp: [wan] IPCP: Close event
Jun  4 20:13:21 firewall ppp: [wan] IPCP: state change Opened --> Closing
Jun  4 20:13:21 firewall ppp: [wan] IPCP: SendTerminateReq #3
Jun  4 20:13:21 firewall ppp: [wan] IPCP: LayerDown
Jun  4 20:13:21 firewall ppp: [wan] IFACE: Down event
Jun  4 20:13:21 firewall ppp: [wan] IPCP: Down event
Jun  4 20:13:21 firewall ppp: [wan] IPCP: LayerFinish
Jun  4 20:13:21 firewall ppp: [wan] Bundle: No NCPs left. Closing links...
Jun  4 20:13:21 firewall ppp: [wan] IPCP: state change Closing --> Initial
Jun  4 20:13:21 firewall ppp: [wan_link0] LCP: SendTerminateReq #2
Jun  4 20:13:21 firewall ppp: [wan_link0] LCP: LayerDown
Jun  4 20:13:24 firewall ppp: [wan_link0] LCP: SendTerminateReq #3
Jun  4 20:13:26 firewall ppp: [wan_link0] LCP: state change Stopping --> Stopped
Jun  4 20:13:26 firewall ppp: [wan_link0] LCP: LayerFinish
Jun  4 20:13:26 firewall ppp: [wan_link0] PPPoE: connection closed
Jun  4 20:13:26 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:13:26 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:13:26 firewall ppp: [wan_link0] LCP: state change Stopped --> Starting
Jun  4 20:13:26 firewall ppp: [wan_link0] LCP: LayerStart
Jun  4 20:13:26 firewall ppp: [wan_link0] Link: reconnection attempt 1 in 3 seconds
Jun  4 20:13:29 firewall ppp: [wan_link0] Link: reconnection attempt 1
Jun  4 20:13:29 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:13:38 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:13:38 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:13:38 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:13:38 firewall ppp: [wan_link0] Link: reconnection attempt 2 in 2 seconds
Jun  4 20:13:40 firewall ppp: [wan_link0] Link: reconnection attempt 2
Jun  4 20:13:40 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:13:49 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:13:49 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:13:49 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:13:49 firewall ppp: [wan_link0] Link: reconnection attempt 3 in 4 seconds
Jun  4 20:13:53 firewall ppp: [wan_link0] Link: reconnection attempt 3
Jun  4 20:13:53 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:14:02 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:14:02 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:14:02 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:14:02 firewall ppp: [wan_link0] Link: reconnection attempt 4 in 1 seconds
Jun  4 20:14:03 firewall ppp: [wan_link0] Link: reconnection attempt 4
Jun  4 20:14:03 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:14:12 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:14:12 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:14:12 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:14:12 firewall ppp: [wan_link0] Link: reconnection attempt 5 in 3 seconds
Jun  4 20:14:15 firewall ppp: [wan_link0] Link: reconnection attempt 5
Jun  4 20:14:15 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:14:24 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:14:24 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:14:24 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:14:24 firewall ppp: [wan_link0] Link: reconnection attempt 6 in 1 seconds
Jun  4 20:14:25 firewall ppp: [wan_link0] Link: reconnection attempt 6
Jun  4 20:14:25 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:14:34 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:14:34 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:14:34 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:14:34 firewall ppp: [wan_link0] Link: reconnection attempt 7 in 2 seconds
Jun  4 20:14:36 firewall ppp: [wan_link0] Link: reconnection attempt 7
Jun  4 20:14:36 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:14:45 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:14:45 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:14:45 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:14:45 firewall ppp: [wan_link0] Link: reconnection attempt 8 in 1 seconds
Jun  4 20:14:46 firewall ppp: [wan_link0] Link: reconnection attempt 8
Jun  4 20:14:46 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:14:55 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:14:55 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:14:55 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:14:55 firewall ppp: [wan_link0] Link: reconnection attempt 9 in 2 seconds
Jun  4 20:14:57 firewall ppp: [wan_link0] Link: reconnection attempt 9
Jun  4 20:14:57 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:15:06 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:15:06 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:15:06 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:15:06 firewall ppp: [wan_link0] Link: reconnection attempt 10 in 4 seconds
Jun  4 20:15:10 firewall ppp: [wan_link0] Link: reconnection attempt 10
Jun  4 20:15:10 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:15:19 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:15:19 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:15:19 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:15:19 firewall ppp: [wan_link0] Link: reconnection attempt 11 in 4 seconds
Jun  4 20:15:23 firewall ppp: [wan_link0] Link: reconnection attempt 11
Jun  4 20:15:23 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:15:32 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:15:32 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:15:32 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:15:32 firewall ppp: [wan_link0] Link: reconnection attempt 12 in 1 seconds
Jun  4 20:15:33 firewall ppp: [wan_link0] Link: reconnection attempt 12
Jun  4 20:15:33 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:15:42 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:15:42 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:15:42 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:15:42 firewall ppp: [wan_link0] Link: reconnection attempt 13 in 3 seconds
Jun  4 20:15:45 firewall ppp: [wan_link0] Link: reconnection attempt 13
Jun  4 20:15:45 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:15:54 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:15:54 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:15:54 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:15:54 firewall ppp: [wan_link0] Link: reconnection attempt 14 in 1 seconds
Jun  4 20:15:55 firewall ppp: [wan_link0] Link: reconnection attempt 14
Jun  4 20:15:55 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:16:04 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:16:04 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:16:04 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:16:04 firewall ppp: [wan_link0] Link: reconnection attempt 15 in 3 seconds
Jun  4 20:16:07 firewall ppp: [wan_link0] Link: reconnection attempt 15
Jun  4 20:16:07 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:16:16 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:16:16 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:16:16 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:16:16 firewall ppp: [wan_link0] Link: reconnection attempt 16 in 2 seconds
Jun  4 20:16:18 firewall ppp: [wan_link0] Link: reconnection attempt 16
Jun  4 20:16:18 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:16:27 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:16:27 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:16:27 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:16:27 firewall ppp: [wan_link0] Link: reconnection attempt 17 in 2 seconds
Jun  4 20:16:29 firewall ppp: [wan_link0] Link: reconnection attempt 17
Jun  4 20:16:29 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:16:38 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:16:38 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:16:38 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:16:38 firewall ppp: [wan_link0] Link: reconnection attempt 18 in 4 seconds
Jun  4 20:16:42 firewall ppp: [wan_link0] Link: reconnection attempt 18
Jun  4 20:16:42 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:16:51 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:16:51 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:16:51 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:16:51 firewall ppp: [wan_link0] Link: reconnection attempt 19 in 4 seconds
Jun  4 20:16:55 firewall ppp: [wan_link0] Link: reconnection attempt 19
Jun  4 20:16:55 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
Jun  4 20:17:04 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Jun  4 20:17:04 firewall ppp: [wan_link0] Link: DOWN event
Jun  4 20:17:04 firewall ppp: [wan_link0] LCP: Down event
Jun  4 20:17:04 firewall ppp: [wan_link0] Link: reconnection attempt 20 in 4 seconds
Jun  4 20:17:08 firewall ppp: [wan_link0] Link: reconnection attempt 20
Jun  4 20:17:08 firewall ppp: [wan_link0] PPPoE: Connecting to '*'
                          1 Reply Last reply Reply Quote 0
                          • jimpJ
                            jimp Rebel Alliance Developer Netgate
                            last edited by

                            Sorry if I wasn't clear. I wasn't asking what config options you chose. I wanted you to look at that file when it worked, and then again when it doesn't work, to see if there is a change in the file from one time to the other. Compare the two files (working, not working) to see if any lines have changed, were added, or removed.

                            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

                              there r no changes in config since pf v1.2.3, the only difference since then is pfsense itself and the mpd in both of the versions as i believe earlier versions of pf v2.0 used older mpd and that time it used to work flawless also.

                              there is no config change which makes it work or makes it dead, on boot almost any config change i make works and the same falls dead when unplugged or isp device goes down or reboots.

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

                                Still not what I asked. Look a the file right when it boots up. Then look again when it's reconnecting and failing.

                                I'm not saying you changed anything - I want to know if the file is different in some way at boot time and when it fails. If something internal to the box rewrites the mpd_wan.conf file and changes something behind the scenes.

                                If the file is identical both times, then the problem would be somewhere different than if the file is the same at both of those times.

                                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

                                  sorry for the mis understanding, i guess i found out the issue.

                                  actually i checked the config right after start and then again after i unplugged the wire and replugged it back in, there wasnt any difference in the config file at all but then i compared it to the config file i had posted earlier and found one line had changed and the below line was added new

                                  set iface addrs 10.10.1.1 10.10.1.2

                                  so while pf was attempting to reconnect and failing, what i did is i opened the config file and removed that line and saved it and then it reconnected in the next attempt but then now the config again started showing this line, so is there any way to remove this line permanently and then perform more tests so as to verify if thats the cause or no.

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

                                    set iface addrs 10.10.1.1 10.10.1.2

                                    is this related to the situation when in some countries i have noticed that as soon as u plug the wire in the isp device, u get a temporary local i based on dhcp enabled on the isp device and then usually u dial the connection related to the pppoe but in my country, if i take that cable and plug into my windows pc or any computer at all, the isp device doesn't assign any temporary ip so after some time windows starts showing limited connectivity but if u use the dialup connection to connect the pppoe then it would dial and connect to the internet perfectly fine.

                                    so to make mpd work in dial on demand is it necessary for this temporary ip to be obtained before a pppoe connection can be established, if so then i would need a work around this problem

                                    Also this command may be used to force specified addresses usage instead of negotiated ones. It may be useful in some specific cases, for example, to avoid routing loop with misconfigured PPTP server. In such case '!' mark specifies IPs to be forced.

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

                                      It looks like that line should only be set of 'on demand' is checked, but judging by the other line in your config ("set iface disable on-demand") it would appear that you do not have that option set. Can you confirm whether or not you have "on demand" set?

                                      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

                                        it was disabled earlier coz it wouldnt anyways connect automatically but i have enabled it again and thats y that line appears.

                                        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 enable on-demand
	set iface idle 0
	set iface addrs 10.10.1.1 10.10.1.2
	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 password
	set pppoe iface vr1
	open
                                        1 Reply Last reply Reply Quote 0
                                        • jimpJ
                                          jimp Rebel Alliance Developer Netgate
                                          last edited by

                                          So if you leave "on demand" unchecked, does it reconnect like it should?

                                          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

                                            it doesnt and like i mentioned the issue is this i guess

                                            is this related to the situation when in some countries i have noticed that as soon as u plug the wire in the isp device, u get a temporary local ip based on dhcp enabled on the isp device and then usually u dial the connection related to the pppoe but in my country, if i take that cable and plug into my windows pc or any computer at all, the isp device doesn't assign any temporary ip so after some time windows starts showing limited connectivity but if u use the dialup connection to connect the pppoe then it would dial and connect to the internet perfectly fine.

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