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

    PfSense 2.0.1 on Soekris Net5501: poor performances

    Scheduled Pinned Locked Moved Development
    3 Posts 2 Posters 3.7k 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.
    • A
      akelge
      last edited by

      Hi to all!
      I'm have been using pfSense on Soekris hardware for almost 5 years.
      I've used it on a Net4801 and now on a Net5501-70.
      The schema is:

      vlan0 on vr1 -> LAN
      vlan1 on vr1 -> OOB (internal management network)
      vr0 -> WAN
      vr2 -> OLAN (another LAN)

      Everything was working fine and bandwidth was fully usable (10Mbps fiber)

      Yesterday we upgraded our Internet connection from 10Mbps to 100Mbps and I decided to upgrade pfSense from 1.2.2 to 2.0.1.

      After upgrading and reconfiguring performances were really poor:
      on LAN (vlan interface) I could reach 3/4 Mbps at most;
      on OLAN (physical interface) I could reach at most 20Mbps.
      CPU was low (10% load) and mem was almost free (as it should be), no hardware problems, no interface errors.

      I suspected something involving VLANs and the Switch, made all my checks, then put up and old PC with pfSense 2.0.1, same configuration and everything went good (80/85 Mbps).

      Then I downgraded the Net5001 to 1.2.2 and performances went really UP (80/85Mbps) either with polling enabled or not.
      So, I tried with 1.2.3 and performances where the same of 1.2.2.

      What is wrong with 2.0.1 (I've no time to test 2.0.0, unluckily) and Soekris Net5501? Is there some tuning I can try?

      I would really like to use 2.0.1, but, right now, it is not possible.+
      TIA
      A.

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

        check interface link negotiation or force it to the configured speed!

        1 Reply Last reply Reply Quote 0
        • A
          akelge
          last edited by

          @ermal:

          check interface link negotiation or force it to the configured speed!

          You're right! I've found it by myself, autonegotiation wins in this case, forcing speed and duplex can cause troubles.

          Now I'm on 2.0.1, at last!

          Thanks
          A.

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