My old setup was:

VSDL modem -> pfsense on mini J1900 Celeron (2 GHz) -> CISCO SG300 10MPP switch -> Rukus R310 wifi -> Laptop

Currnet setup

Fiber model -> pfsense on mini J1900 Celeron (2 GHz) -> CISCO SG300 10MPP switch -> Rukus R310 wifi -> Laptop

Today i got my 1GBit fiber installed (big deal for those like me living in rural areas) only to discover that my current network setup is not allowing me to benefit from it.

I was on VSDL copper wire before and was probably in the region of 50-60 MBit/s with my above current setup. Even when removing the wifi bottle and linking with Cat5 UTP wire directly to switch, I’m not getting major improvements.

When I got the fiber installed this morning I was disappointed when I saw only marginal gain running at 80 MBit/s (c. +30 MBit). So I decided to connect the laptop via LAN cable directly to modem. I got a starkling 900MBit/s. So, along my network I have bottlenecks.

THe first one I tested was my little pfsense machine. I installed the speedtext-cli command and was surprised to find that it was giving my around 300 MBit/s. So a lot better than my laptop on its usual wifi connection but still only 33% of what I get directly off the modem.

So my first question is how can it be that my little mini J1900 Celeron (2 GHz) with 4 GB RAM cannot handle this bandwith? Do I need an upgrade for my pfsense machine? I noticed that the peak CPU demand as speedtest-cli was running was in the 60% region, far from a saturated CPU and RAM only occupied for about 30%. If it is my little pfsense machine, how far do I have to go with finding the right little machine that can handle 1 GBit/s.

The next question is if I’m getting 300 MBit/s on the WAN connection of the pfSense machine, how is it that I only see a small percentage of this on my laptop? i.e. a drop from 300 MBit/s to 80 MBit/s? I guess I would have to test the switch to start and then move to the wifi access points …

  • Corngood@lemmy.ml
    link
    fedilink
    English
    arrow-up
    61
    ·
    4 months ago

    Have you checked all the ethernet links are actually connected at 1G and not 100M?

  • SaltySalamander@fedia.io
    link
    fedilink
    arrow-up
    29
    ·
    4 months ago

    how can it be that my little mini J1900 Celeron (2 GHz) with 4 GB RAM cannot handle this bandwith?

    Because it’s ancient, and when it was new it was bottom-of-the-barrel.

    • trilobite@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      4 months ago

      I probably didn’t realise how CPU intensive the work of 1Gbit connection must be …

  • earmuff@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    24
    ·
    4 months ago

    The question is what you do with your pfsense. IDS/IPS are quite CPU hungry and Celerons are not really fast CPU’s.

    • catloaf@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      4 months ago

      peak CPU demand as speedtest-cli was running was in the 60% region, far from a saturated CPU and RAM only occupied for about 30%

      It doesn’t look like he’s bound by CPU.

      • earmuff@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        5
        ·
        4 months ago

        And he is currently at 1/3 of the potential speed and 3*60% = 180% CPU load for 1Gbits. So I wouldn’t even bother troubleshooting further when you already know the hardware will be an issue sooner or later.

        • catloaf@lemm.ee
          link
          fedilink
          English
          arrow-up
          5
          ·
          4 months ago

          That assumes that all of the 60% is for pushing packets, which is almost certainly not the case.

          • earmuff@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            4 months ago

            True. But since OP is using a benchmark anyways, I don‘t know how close to real world that is. If they are doing lots of filesharing, let‘s say with P2P networks, it could be way worse because of the number of connections. So I agree with you - I was just working with the info I had :)

  • teawrecks@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    12
    ·
    4 months ago

    Something to look for besides bandwidth is actual packet routing throughput. It’s possible you enabled a feature (ex. Deep packet inspection) that is limiting how many packets can be routed per second given the speed of your hardware.

  • i_am_not_a_robot@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    9
    ·
    4 months ago

    That Pentum is a budget CPU from just over 10 years ago. It has PCIe 2.0. Maybe the “gigabit” ethernet is connected to the CPU by a single 500Mbit PCIe lane.

    • cmnybo@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 months ago

      PCIe 2.0 is 500 MB/s per lane, it’s not going to limit the speed. That CPU certainly doesn’t have enough power to run something heavy like IDS at 1gbps though.

  • filister@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    4 months ago

    Another piece of the puzzle is probably your WiFi router, as you normally won’t get speeds near 1Gbps over WiFi. In order to benefit maximally from it, you need to connect your devices (laptops, stationary PC, TV, etc.) with a cable to get the most of it.

    You should also try to disable some pfSense plugins, like OpenVPN, zenArmor, etc. as they will severely limit your bandwidth throughput. But as others said, most likely you will also need to upgrade your hardware box, and you can migrate to OPNsense while at it.

  • sebas@lemm.ee
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    I have been using similar hardware setups in A LOT of installations. This is mostly an issue with the pfSense hardware. There’s a lot of decent options around $200, mostly focus on getting a modern CPU (if it supports AES-NI there’s a good chance it will be fine). A lot of them have 2.5g nics these days too.

    Sadly, sg300 line is also getting pretty old. In recent years I’m seeing more and more issues with them, especially in the models with poe. Sg350 is even eos now, with cbs350 being the current.

    I’m also now using r610 as the absolute minimum ruckus ap. I was using r510 for a long time, but the r610 has noticable improvements.

    • trilobite@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      Any thoughts on a good little fanless device that I can use as a pfSense machine that has a resonable CPU. I would just swap the SSD from my curent device to the new one and it should all work nicely.

  • azl@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    For what it’s worth, since it sounds like you will be hardware shopping soon: I am using a 2.4GHz Intel Atom C2758 running pfSense and get 2Gb/s down and around 1.5Gb/s up through it. I am using an add-on Intel-based PCIe network adapter, so I’m not sure if that is helping with the CPU load. But it works well.

  • IsoKiero@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    4 months ago

    The process is to go step-by-step. First direct connect to modem you have, bridged connection if possible, and test with multiple bandwidth measurements (speedtest, fast.com, downloading a big file from some university ftp…) and work your way downstream of the network. And on every step test multiple scenarios where it’s possible, preferably with multiple devices.

    When I got a 1Gbit fiber connection few years back I got an Ubiquiti Edgerouter-X with PoE-options. On paper that should’ve been plenty for my network, but in theory with NAT, DNAT, firewall rules and things like that it capped on 6-700Mbps depending on what I used it for. With small packets and VPN it dropped even more. So now that thing acts as an glorified PoE switch and the main routing is handled with Mikrotik device, which on manufacturers tests should be able to push 7Gbps on optimal conditions. I only have 1/1Gbps, so there’s plenty of room, but with very specific loads that thing still is still pushed to the limit (mostly small packet size with other stuff on top of it) but it can manage the full duplex 1000Base-T. And on normal everyday use it’s running at 20% (or so) load, but I like the fact that it can manage even the more challenging scenarios.

    • trilobite@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      Ok, starting to think I need a new little device for my pfSense. I was thinking of going OpenSense and buying one of their devices to support the project.

      Regarding my switch, the ports where my Rukus APs are connected are showing 1000M on the interface. But I think a step by step testing is what is needed as suggested above.

      • Oisteink@feddit.nl
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 months ago

        Run iperf internally to see if your bottleneck is switch/ap or fw. I set up a j1900 pfsense for my sisters family a while back to do qos (gamer bois in the house) amd it had no problem staying at 500mbps. No ids or other stuff.

        Not built any opn/pf-sense in a while, but i always use intel server-nic’s. Used to have way better support than other stuff on bsd

  • waggz@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    I had to upgrade my pfsense hardware when I got fiber several years ago, which was in a similar situation as yours. The CPU just couldn’t handle the connection table.

    • RustyHeater@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      J1900 has no hardware switch. Every packet goes through CPU, so even LAN to LAN uses processing power. Add pfsense to the mix and it’s probably choking.

  • eramseth@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

    CPU and RAM are not the only limiting factors. Not only that but not everything runs multithreaded. Maybe some piece of the puzzle is not multithreaded and is using all it can from a single core (assuming that cpu is multi- core)

    Depending on how much you value your time, you’re almost certainly better off getting a new machine to run pfsense.