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

    Very poor NAT performance

    Scheduled Pinned Locked Moved Virtualization
    13 Posts 6 Posters 4.1k 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.
    • E
      EMWEE
      last edited by

      Do you have 5.5 U2? FreeBSD10 is only supported on 5.5U2 and 6.

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

        @EMWEE:

        Do you have 5.5 U2? FreeBSD10 is only supported on 5.5U2 and 6.

        i've got a 2.2.X running on esxi4.1 running the legacy e1000 nics, just fine … hitting 1gbit/s wire speed without too much trouble.

        there is something else going on here.
        did you accidently install the official vmware-tools ? if yes --> reinstall and don't do it again  ;)

        1 Reply Last reply Reply Quote 0
        • S
          szabolcs
          last edited by

          I've got the latest ESXi as the update manager keeps all the hosts updated.
          As for the vmware-tools, I had it installed way back when my pfsense was 2.1 or 2.0 not sure. Back then the FreeBSD kernel did not support the vmxnet3 out of the box. Before I have upgraded the pfsense (using the autoupdated) I have uninstalled properly the vmware-tools.

          However that could be a candidate. One thing which leaves some doubt, if I change the adapters to e1000, the performance still the same. But only for the forwarded ports. When I connect to any VPN provided on the WAN interface and reach the LAN like that, all's good. Only the port forwards are extremely bad. I think I going to have to reinstall maybe, but if I do I'd like to understand why? It just doesn't make much sense to me at the moment.

          1 Reply Last reply Reply Quote 0
          • S
            szabolcs
            last edited by

            Well, the bad news is that I have reinstalled and the issue remains. I used the latest stable 2.2.2 amd64 release.

            1 Reply Last reply Reply Quote 0
            • S
              Supermule Banned
              last edited by

              I can easily get wirespeed on the 2.2.2 release using NAT.

              I use the E1000 NIC's. FreeBSD support VMXnet3 out of the box and it could easily be shitty drivers.

              1 Reply Last reply Reply Quote 0
              • S
                szabolcs
                last edited by

                I mentioned in one of the posts that I tried to change the NIC to e1000 and did not help. But let me try that again.

                1 Reply Last reply Reply Quote 0
                • S
                  Supermule Banned
                  last edited by

                  It could be the fact you NAT a very large subnet to a smaller one, but still belonging to the same overall subnet.

                  Pretty weird rules tbh.

                  1 Reply Last reply Reply Quote 0
                  • S
                    szabolcs
                    last edited by

                    What do you mean? It's a simple port forward. Are you looking at the rdr rules (which is the problem) or the nat (which is outgoing NAT). The outgoing NAT couldn't be more standard….

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

                      what does the cpu graph show on the vsphere client? (while pushing traffic)

                      how fast can you fetch a file from the pfSense console ? (to find out if its only while forwarding, or a general connection issue)

                      1 Reply Last reply Reply Quote 0
                      • S
                        szabolcs
                        last edited by

                        CPU is around 0-1 percent both on pfSense and ESXi side. Virtually not utilised at all.

                        The fetch is near 100MB/sec with once again near zero CPU utilisation. When I connect to OpenVPN or IPSec on WAN I can reach the LAN with full speed. The network drivers are absolutely fine in my view.

                        1 Reply Last reply Reply Quote 0
                        • P
                          planetinse
                          last edited by

                          Confirming the very same issue

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

                            I'm seeing the same type of behaviour. When the gateway is the CARP Vip my throughput out of WAN is ~3mbps max as soon as I switch to the real router LAN interface I have connection speeds of 50mbps (which is normal). No raise in CPU or memory usage either.

                            ESXi 6.0
                            4gb Ram
                            5 CPUs

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