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

    [SOLVED]PPPoE unstable in 2.0-RC2

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    23 Posts 11 Posters 8.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.
    • T
      thomas777
      last edited by

      I also have been dealing with this problem for months of PPPoE being unstable. This is why in a previous post I mention that I am switching to static DSLs so I can be done with PPPoE connections.

      I would like to note however that the October 18th snapshot worked with my PPPoE connections perfectly. The problem came back for me when I upgraded to the latest snapshot in early June and the old problem of PPPoE from earlier than October 18th came back again. I would have switched back to the older snapshot but could not find it. So for weeks I updated to the latest snapshot last month trying to fix the problem, with no luck, hence deciding to change my DSL connections with the ISP.

      My posts often are about load balancing but the essential problem is that PPPoE has been unstable making the loadbalancing to not function.

      1 problem is they appear to go down and another is they are constantly gathering data on the dashboard.

      I am adding this so people know others are having issues with PPPoE as well, but as I said I am switching my connections so I don't use PPPoE anymore.

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

        @thomas777:

        I would like to note however that the October 18th snapshot worked with my PPPoE connections perfectly. The problem came back for me when I upgraded to the latest snapshot in early June and the old problem of PPPoE from earlier than October 18th came back again.

        And that is why it pays to keep up to date with snapshots. If you could point at one specific snapshot that supposedly broke something, it's much easier to find a problem than somewhere in the vast difference between October and June. Thousands of commits and changes between there, and no easy way for anyone to reproduce it makes it that much harder.

        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
        • T
          thomas777
          last edited by

          I understand and I apologize, I got everything working and left it alone for 6 months. Did not know until a few weeks ago.

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