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

    Upgrade from 12/13 to 12/18 -> PPPoE dead…

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    193 Posts 20 Posters 91.5k 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.
    • J
      jlepthien
      last edited by

      Hm. No, that config wouldn't restore in a vm as well :(
      I also tested older configs from october. Same error, everytime…
      Tried with aliases and nat section. Does not work. Does this restore of some actually work for you in newer builds? Perhaps nobody tried to restore just a part of the config?

      | apple fanboy | music lover | network and security specialist | in love with cisco systems |

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

        The partial restore doesn't seek out portions of a whole config, you have to edit out the part you want. For example, to restore DHCP settings, you need to cut the <dhcpd>…</dhcpd> section out into a separate file, and then pick that file along with choosing the DHCP server settings from the drop-down.

        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
        • J
          jlepthien
          last edited by

          Aha. So THAT could be the problem….

          | apple fanboy | music lover | network and security specialist | in love with cisco systems |

          1 Reply Last reply Reply Quote 0
          • J
            jlepthien
            last edited by

            Thanks jimp! That works! Man I could have searched a long time. Perhaps you should add a comment on the restore page so that everyone knows about this…

            Or am I the only one who didn't know how it's suppose to work? ;)

            | apple fanboy | music lover | network and security specialist | in love with cisco systems |

            1 Reply Last reply Reply Quote 0
            • J
              jlepthien
              last edited by

              @ermal:

              Try this manually
              https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/92a1c8e6caca910ae1f8c54751bffebd45d87682

              or wait for a snapshot with the patch applied.

              I just had this error while updating my config. Applied this manually and it works. Will check if it reached the newest snap yet…

              | apple fanboy | music lover | network and security specialist | in love with cisco systems |

              1 Reply Last reply Reply Quote 0
              • J
                jlepthien
                last edited by

                Ok the fix is in the newest snap, but there seems to be a problem. Each time I reboot my Alix I get the same error as I posted in the beginning of this thread. I then need to ssh into my box do a killall mpd5. Then I have to go into the WebUI to my WAN interface, set a 0 into the idle timeout field and click save. Is this actually also a bug that I have to put in the zero everytime again? It does not get saved somehow…

                After these steps my connections stays online until the next reboot...

                | apple fanboy | music lover | network and security specialist | in love with cisco systems |

                1 Reply Last reply Reply Quote 0
                • G
                  gnhb
                  last edited by

                  So, are you saying that you have the "Dial on Demand" checkbox checked? Do you really need Dial on Demand?

                  Refs for devs:
                  http://redmine.pfsense.org/issues/757

                  http://redmine.pfsense.org/issues/927

                  1 Reply Last reply Reply Quote 0
                  • J
                    jlepthien
                    last edited by

                    Yes, that box is checked. I want my line to be up and running all the time…

                    | apple fanboy | music lover | network and security specialist | in love with cisco systems |

                    1 Reply Last reply Reply Quote 0
                    • G
                      gnhb
                      last edited by

                      Well, two points.

                      First if you you want your line up and running all the time, you need to uncheck that box. That box is supposed to bring the line down when no outgoing traffic is detected after "Idle timeout" time has elapsed.

                      Second, checking that box is likely what has caused all your problems. That options invokes some pretty complex code that apparently still isn't stable. (re: linked redmine issues)

                      1 Reply Last reply Reply Quote 0
                      • G
                        grandrivers
                        last edited by

                        If thats is the intended function of dial on demand the the wording of setting it to zero should be remove and replace with untick for always on connection would clear up some confusion

                        pfsense plus 25.03 super micro A1SRM-2558F
                        C2558 32gig ECC  60gig SSD

                        1 Reply Last reply Reply Quote 0
                        • E
                          eri--
                          last edited by

                          Can you please test with latest snapshots?

                          1 Reply Last reply Reply Quote 0
                          • J
                            jlepthien
                            last edited by

                            Ok. I'll wait for the next snapshot to appear and try it…

                            | apple fanboy | music lover | network and security specialist | in love with cisco systems |

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

                              2.0-BETA4 (amd64)
                              built on Tue Dec 21 15:13:51 EST 2010

                              This is a clean install using a config that was running on a nanobsd snapshot from about a week ago. I'm getting errors similar to the OP. I don't have, and never did have the dial on demand box checked. If I click the Connect button on Status: Interfaces, it connects within seconds, but never automatically after a reboot.

                              db

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

                                Try with the most current snapshot, the one just uploaded. IIRC some fixes happened after the snapshot you're on but a new snap hadn't been generated since last night/this morning.

                                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
                                • J
                                  jlepthien
                                  last edited by

                                  Still not working with latest snap…

                                  Still have to kill mpd5 and then click save on WAN interface again...

                                  | apple fanboy | music lover | network and security specialist | in love with cisco systems |

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    jlepthien
                                    last edited by

                                    Actually I tried again, because I needed to reboot. (Still the Internal Server Error after installing avahi package)
                                    I do not need to kill mpd5. I just need to click save on WAN…

                                    | apple fanboy | music lover | network and security specialist | in love with cisco systems |

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

                                      2.0-BETA4 (amd64)
                                      built on Thu Dec 23 12:13:59 EST 2010

                                      I updated 8 hours ago and still had to hit the Connect button to get a WAN.

                                      db

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        jlepthien
                                        last edited by

                                        Same problem here with newest snap of 12/26…
                                        But if I wait long enough pfSense connects by itself after 3-4 minutes...

                                        | apple fanboy | music lover | network and security specialist | in love with cisco systems |

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

                                          Post your mpd logs.

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            jlepthien
                                            last edited by

                                            Here is some output of my ppp.log:

                                            Dec 28 00:16:03	ppp: [wan_link0] Link: reconnection attempt 2
Dec 28 00:16:03	ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd8264-0" and "[f]:"->"left": No such file or directory
Dec 28 00:16:03	ppp: [wan_link0] can't remove hook mpd8264-0 from node "[12]:": No such file or directory
Dec 28 00:16:03	ppp: [wan_link0] Link: DOWN event
Dec 28 00:16:03	ppp: [wan_link0] LCP: Down event
Dec 28 00:16:03	ppp: [wan_link0] Link: reconnection attempt 3 in 4 seconds
Dec 28 00:16:07	ppp: [wan_link0] Link: reconnection attempt 3
Dec 28 00:16:07	ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd8264-0" and "[f]:"->"left": No such file or directory
Dec 28 00:16:07	ppp: [wan_link0] can't remove hook mpd8264-0 from node "[12]:": No such file or directory
Dec 28 00:16:07	ppp: [wan_link0] Link: DOWN event
Dec 28 00:16:07	ppp: [wan_link0] LCP: Down event
Dec 28 00:16:07	ppp: [wan_link0] Link: reconnection attempt 4 in 2 seconds
Dec 28 00:16:09	ppp: [wan_link0] Link: reconnection attempt 4
Dec 28 00:16:09	ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd8264-0" and "[f]:"->"left": No such file or directory
Dec 28 00:16:09	ppp: [wan_link0] can't remove hook mpd8264-0 from node "[12]:": No such file or directory
Dec 28 00:16:09	ppp: [wan_link0] Link: DOWN event
Dec 28 00:16:09	ppp: [wan_link0] LCP: Down event
Dec 28 00:16:09	ppp: [wan_link0] Link: reconnection attempt 5 in 2 seconds
Dec 28 00:16:11	ppp: [wan_link0] Link: reconnection attempt 5
Dec 28 00:16:11	ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd8264-0" and "[f]:"->"left": No such file or directory
Dec 28 00:16:11	ppp: [wan_link0] can't remove hook mpd8264-0 from node "[12]:": No such file or directory
Dec 28 00:16:11	ppp: [wan_link0] Link: DOWN event
Dec 28 00:16:11	ppp: [wan_link0] LCP: Down event
Dec 28 00:16:11	ppp: [wan_link0] Link: reconnection attempt 6 in 2 seconds
Dec 28 00:16:13	ppp: [wan_link0] Link: reconnection attempt 6
Dec 28 00:16:13	ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd8264-0" and "[f]:"->"left": No such file or directory
Dec 28 00:16:13	ppp: [wan_link0] can't remove hook mpd8264-0 from node "[12]:": No such file or directory
Dec 28 00:16:13	ppp: [wan_link0] Link: DOWN event
Dec 28 00:16:13	ppp: [wan_link0] LCP: Down event
Dec 28 00:16:13	ppp: [wan_link0] Link: reconnection attempt 7 in 4 seconds
Dec 28 00:16:17	ppp: caught fatal signal term
Dec 28 00:16:17	ppp: [wan] IFACE: Close event
Dec 28 00:16:17	ppp: [wan] IPCP: Close event
Dec 28 00:16:17	ppp: [wan_link0] LCP: Close event
Dec 28 00:16:17	ppp: [wan_link0] LCP: state change Starting --> Initial
Dec 28 00:16:17	ppp: [wan_link0] LCP: LayerFinish
Dec 28 00:16:19	ppp: [wan] Bundle: Shutdown
Dec 28 00:16:19	ppp: [wan_link0] Link: Shutdown
Dec 28 00:16:19	ppp: process 8264 terminated
Dec 28 00:16:25	ppp: Multi-link PPP daemon for FreeBSD
Dec 28 00:16:25	ppp:
Dec 28 00:16:25	ppp: process 38608 started, version 5.5 (root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org 21:35 22-Dec-2010)
Dec 28 00:16:25	ppp: web: web is not running
Dec 28 00:16:25	ppp: [wan] Bundle: Interface ng0 created
Dec 28 00:16:25	ppp: [wan_link0] Link: OPEN event
Dec 28 00:16:25	ppp: [wan_link0] LCP: Open event
Dec 28 00:16:25	ppp: [wan_link0] LCP: state change Initial --> Starting
Dec 28 00:16:25	ppp: [wan_link0] LCP: LayerStart
Dec 28 00:16:25	ppp: [wan_link0] PPPoE: Connecting to '*'
Dec 28 00:16:25	ppp: PPPoE: rec'd ACNAME "KIER71-se800-B2234310702478"

                                            That goes on for like 2-3 minutes and then suddenly it works…

                                            Dec 28 00:17:44	ppp: [wan_link0] Link: reconnection attempt 7 in 2 seconds
Dec 28 00:17:46	ppp: [wan_link0] Link: reconnection attempt 7
Dec 28 00:17:46	ppp: [wan_link0] PPPoE: Connecting to '*'
Dec 28 00:17:46	ppp: PPPoE: rec'd ACNAME "KIER71-se800-B2234310702478"
Dec 28 00:17:55	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Dec 28 00:17:55	ppp: [wan_link0] Link: DOWN event
Dec 28 00:17:55	ppp: [wan_link0] LCP: Down event
Dec 28 00:17:55	ppp: [wan_link0] Link: reconnection attempt 8 in 3 seconds
Dec 28 00:17:58	ppp: [wan_link0] Link: reconnection attempt 8
Dec 28 00:17:58	ppp: [wan_link0] PPPoE: Connecting to '*'
Dec 28 00:17:58	ppp: PPPoE: rec'd ACNAME "KIER71-se800-B2234310702478"
Dec 28 00:18:04	ppp: [wan_link0] PPPoE: connection successful
Dec 28 00:18:04	ppp: [wan_link0] Link: UP event
Dec 28 00:18:04	ppp: [wan_link0] LCP: Up event
Dec 28 00:18:04	ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Dec 28 00:18:04	ppp: [wan_link0] LCP: SendConfigReq #1
Dec 28 00:18:04	ppp: [wan_link0] PROTOCOMP
Dec 28 00:18:04	ppp: [wan_link0] MRU 1492
Dec 28 00:18:04	ppp: [wan_link0] MAGICNUM a8eef870
Dec 28 00:18:04	ppp: [wan_link0] LCP: rec'd Configure Request #52 (Req-Sent)
Dec 28 00:18:04	ppp: [wan_link0] MRU 1492
Dec 28 00:18:04	ppp: [wan_link0] AUTHPROTO PAP
Dec 28 00:18:04	ppp: [wan_link0] MAGICNUM 49a2d6c8
Dec 28 00:18:04	ppp: [wan_link0] LCP: SendConfigAck #52
Dec 28 00:18:04	ppp: [wan_link0] MRU 1492
Dec 28 00:18:04	ppp: [wan_link0] AUTHPROTO PAP
Dec 28 00:18:04	ppp: [wan_link0] MAGICNUM 49a2d6c8
Dec 28 00:18:04	ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Dec 28 00:18:04	ppp: [wan_link0] LCP: rec'd Configure Reject #1 (Ack-Sent)
Dec 28 00:18:04	ppp: [wan_link0] PROTOCOMP
Dec 28 00:18:04	ppp: [wan_link0] LCP: SendConfigReq #2
Dec 28 00:18:04	ppp: [wan_link0] MRU 1492
Dec 28 00:18:04	ppp: [wan_link0] MAGICNUM a8eef870
Dec 28 00:18:04	ppp: [wan_link0] LCP: rec'd Configure Ack #2 (Ack-Sent)
Dec 28 00:18:04	ppp: [wan_link0] MRU 1492
Dec 28 00:18:04	ppp: [wan_link0] MAGICNUM a8eef870
Dec 28 00:18:04	ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
Dec 28 00:18:04	ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
Dec 28 00:18:04	ppp: [wan_link0] PAP: using authname "xxxx@t-online.de"
Dec 28 00:18:04	ppp: [wan_link0] PAP: sending REQUEST #1 len: 54
Dec 28 00:18:04	ppp: [wan_link0] LCP: LayerUp
Dec 28 00:18:05	ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
Dec 28 00:18:05	ppp: [wan_link0] LCP: authorization successful
Dec 28 00:18:05	ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Dec 28 00:18:05	ppp: [wan_link0] Link: Join bundle "wan"
Dec 28 00:18:05	ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Dec 28 00:18:05	ppp: [wan] IPCP: Open event
Dec 28 00:18:05	ppp: [wan] IPCP: state change Initial --> Starting
Dec 28 00:18:05	ppp: [wan] IPCP: LayerStart
Dec 28 00:18:05	ppp: [wan] IPCP: Up event
Dec 28 00:18:05	ppp: [wan] IPCP: state change Starting --> Req-Sent
Dec 28 00:18:05	ppp: [wan] IPCP: SendConfigReq #1
Dec 28 00:18:05	ppp: [wan] IPADDR 0.0.0.0
Dec 28 00:18:05	ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 28 00:18:05	ppp: [wan] IPCP: rec'd Configure Request #229 (Req-Sent)
Dec 28 00:18:05	ppp: [wan] IPADDR 87.186.224.38
Dec 28 00:18:05	ppp: [wan] 87.186.224.38 is OK
Dec 28 00:18:05	ppp: [wan] IPCP: SendConfigAck #229
Dec 28 00:18:05	ppp: [wan] IPADDR 87.186.224.38
Dec 28 00:18:05	ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
Dec 28 00:18:05	ppp: [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)
Dec 28 00:18:05	ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 28 00:18:05	ppp: [wan] IPCP: SendConfigReq #2
Dec 28 00:18:05	ppp: [wan] IPADDR 0.0.0.0
Dec 28 00:18:05	ppp: [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
Dec 28 00:18:05	ppp: [wan] IPADDR xxxx
Dec 28 00:18:05	ppp: [wan] xxxx is OK
Dec 28 00:18:05	ppp: [wan] IPCP: SendConfigReq #3
Dec 28 00:18:05	ppp: [wan] IPADDR xxxx
Dec 28 00:18:05	ppp: [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
Dec 28 00:18:05	ppp: [wan] IPADDR xxxx
Dec 28 00:18:05	ppp: [wan] IPCP: state change Ack-Sent --> Opened
Dec 28 00:18:05	ppp: [wan] IPCP: LayerUp
Dec 28 00:18:05	ppp: [wan] xxxx -> 87.186.224.38
Dec 28 00:18:05	ppp: [wan] IFACE: Up event

                                            This whole thing was working fine for me before…

                                            | apple fanboy | music lover | network and security specialist | in love with cisco systems |

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