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

    Build for 1Gbps on PPPoE

    Scheduled Pinned Locked Moved Hardware
    32 Posts 9 Posters 11.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.
    • ?
      Guest
      last edited by

      It must be that damn single-core pppoe bug,

      If they get solved this I would imagine 70 % of all users will be happy.

      and 3 site-to-site OpenVPNs, +some road warriors.

      As I am informed each OpenVPN tunnel is using one CPU core. So this could also
      narrow down the entire throughput a bit more as we could imagine. Or am I wrong with this.

      btw: do we know for sure that 2.3 will solve the PPPoE issue?

      Yep if so it many customers would be sorted right at one touch. I was also lurking on
      the new Xeon D-15x8 network accelerated platforms, but they are not fully launched till
      today so I have to wait longer. But it is likes it is, their is the NVMe M.2 SSD the problem
      to get this SSD type working flawless as reported here in the forum.

      1 Reply Last reply Reply Quote 0
      • R
        robi
        last edited by

        @BlueKobold:

        It must be that damn single-core pppoe bug,

        If they get solved this I would imagine 70 % of all users will be happy.

        Agree…

        @BlueKobold:

        and 3 site-to-site OpenVPNs, +some road warriors.

        As I am informed each OpenVPN tunnel is using one CPU core. So this could also
        narrow down the entire throughput a bit more as we could imagine. Or am I wrong with this.

        Well I don't really see which process goes to which core, but I really hope OpenVPN procresses don't stick all to the same single core as pppoe… The operating system should take care to distribute different processes to different available cores of the CPU.
        So far I didn't have problems with this, as traffic inside these tunnels is only limited to inter-site intranet traffic, which is minimal.

        @BlueKobold:

        btw: do we know for sure that 2.3 will solve the PPPoE issue?

        Yep if so it many customers would be sorted right at one touch.

        As far as I read the bug reports, they are not so optimistic. Where did you see a clear statement that this is going to be fixed in pfSense v2.3???

        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by

          As far as I read the bug reports, they are not so optimistic. Where did you see a clear statement that this is going to be fixed in pfSense v2.3???

          There is not clear statement out! @nikkon was asking for what we can be sure on this that it will be
          solved out in the version 2.3 and I was answering if they get it to work, many users will be sorted with
          one touch.

          1 Reply Last reply Reply Quote 0
          • L
            louf
            last edited by

            @nikkon @robi I have RDS as well. Too bad PPPoE is an issue since one of the reasons for moving to it was to get away from the proprietary wifi routers and their 'magic'/'hardware' NAT without sacrificing speed. I wonder if there are any PPPoE bridges out there - use the ISP box to handle PPPoE and pfsense for routing (maybe through some virtual lan or such)?

            @nikkon where in RO did you get supermicro? I don't see a lot of options.

            @sudonim interesting comment about em vs igb driver. Initially I went with em but after reading the comments about it being old and igb being newly written and supported, I decided to go for the respective Intel NICs, basically 82575 and 82576 - on paper they look a lot beefier than 82571. Can you expand on why em is better than igb? Thanks!

            1 Reply Last reply Reply Quote 0
            • N
              nikkon
              last edited by

              I got my both supermicro mobo's from Elko
              First one was an J1900. Both ware planned for pfsense :)

              pfsense 2.3.4 on Supermicro A1SRi-2758F + 8GB ECC + SSD

              Happy PfSense user :)

              1 Reply Last reply Reply Quote 0
              • L
                louf
                last edited by

                How big was the CPU difference after the upgrade?

                1 Reply Last reply Reply Quote 0
                • H
                  hardsense
                  last edited by

                  Same goes to this thread here..
                  Would you run iperf test first ?
                  So that at least you roughly know what your hardware is capable of.

                  Some good ref on how user test his hardware so that he understand what exactly his hardware is capable of:
                  https://forums.openvpn.net/topic15861.html

                  1 Reply Last reply Reply Quote 0
                  • N
                    nikkon
                    last edited by

                    sory for my late asnwer :(
                    C2758 is much faster than J1900, firs of all is octo-core vs quad, still if you don't use openvpn/ipsec only the difference in pfsense is not much…notable but not so big.In my case, with pppoe cpu matters when i use the full bandwith downloading stuff.

                    pfsense 2.3.4 on Supermicro A1SRi-2758F + 8GB ECC + SSD

                    Happy PfSense user :)

                    1 Reply Last reply Reply Quote 0
                    • PerforadoP
                      Perforado Rebel Alliance
                      last edited by

                      You could go completely overboard with a Supermicro X10SRM-F and a Xeon E5-1620 v3 ;)

                      I think this setup could even handle surricata-inline on 2.3 at 1GBe. Will try as soon as the X10SRM with 10GBe is available.

                      1 Reply Last reply Reply Quote 0
                      • N
                        nikkon
                        last edited by

                        @Perforado:

                        You could go completely overboard with a Supermicro X10SRM-F and a Xeon E5-1620 v3 ;)

                        I think this setup could even handle surricata-inline on 2.3 at 1GBe. Will try as soon as the X10SRM with 10GBe is available.

                        Suricata will be much more easy to handle!!! it's multithreading application.On the other side Snort is single and doesn't use the advantage of multi core CPU's
                        no clue if suricata will support PPPoE ?

                        pfsense 2.3.4 on Supermicro A1SRi-2758F + 8GB ECC + SSD

                        Happy PfSense user :)

                        1 Reply Last reply Reply Quote 0
                        • T
                          trumee
                          last edited by

                          Is using em driver better than igb for pppoe connections?

                          1 Reply Last reply Reply Quote 0
                          • N
                            nikkon
                            last edited by

                            have no clue…does the driver matters?

                            pfsense 2.3.4 on Supermicro A1SRi-2758F + 8GB ECC + SSD

                            Happy PfSense user :)

                            1 Reply Last reply Reply Quote 0
                            • L
                              louf
                              last edited by

                              See this previous post (has some nice links):
                              @sudonim:

                              From my research and experiments, you need an older system that uses an "em" driver card not an "igb" card. https://kdemaria.wordpress.com/2015/04/22/how-to-configure-pfsense-2-2-2-for-centurylink-gigabit-seattle-edition/#comment-300

                              You might have bad luck with PPPoE and gigabit with an igb card because of this issue: https://redmine.pfsense.org/issues/4821

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