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

    VPN throughput dips

    Scheduled Pinned Locked Moved OpenVPN
    13 Posts 6 Posters 1.2k 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.
    • B
      blwag
      last edited by blwag

      I'm seeing an interesting behavior when connected to an OpenVPN. The hardware is a Supermicro SYS-5019A-FTN4 with a Comcast Gigabit (1024M/40M) service.

      When the firewall is receiving traffic, there are occasions where throughput drops to zero. It will eventually rebound, but I'm curious what's causing the drops.

      Here's an example:
      0_1544635119670_Screen Shot 2018-12-12 at 10.00.45 AM.png

      I do not see the same behavior on traffic in the reverse direction. I've tried both iperf as well as file copies with the same result.

      I'm wondering if there's a configuration item that's limiting the throughput or something else I should be looking at.

      Here's my client VPN config:
      dev tun
      persist-tun
      persist-key
      cipher AES-128-CBC
      auth SHA256
      tls-client
      client
      resolv-retry infinite
      remote <host> 443 tcp-client
      verify-x509-name "pfsense" name
      auth-user-pass
      remote-cert-tls server
      route 192.168.10.0 255.255.255.0
      route 192.168.100.1 255.255.255.255

      Thoughts? Thanks in advance!

      JKnottJ 1 Reply Last reply Reply Quote 0
      • RicoR
        Rico LAYER 8 Rebel Alliance
        last edited by

        TCP is always a really bad choice for OpenVPN.

        -Rico

        1 Reply Last reply Reply Quote 0
        • chpalmerC
          chpalmer
          last edited by

          What modem are you using?

          Triggering snowflakes one by one..
          Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

          B 1 Reply Last reply Reply Quote 0
          • B
            blwag @chpalmer
            last edited by

            @chpalmer Netgear CM1000. To be clear, I don't see that pattern on LAN traffic. It's only via VPN.

            1 Reply Last reply Reply Quote 0
            • chpalmerC
              chpalmer
              last edited by chpalmer

              How about the other side? How is it built?

              Triggering snowflakes one by one..
              Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

              B 1 Reply Last reply Reply Quote 0
              • B
                blwag @chpalmer
                last edited by

                @chpalmer The source is my office, which is a Cisco/Juniper enterprise environment.

                1 Reply Last reply Reply Quote 0
                • chpalmerC
                  chpalmer
                  last edited by

                  @blwag said in VPN throughput dips:

                  192.168.100.1 255.255.255.255

                  The above address seems odd.. Can you reach your modem while the VPN is up?

                  Triggering snowflakes one by one..
                  Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    blwag @chpalmer
                    last edited by

                    @chpalmer Yes, the modem management is accessible via VPN.

                    1 Reply Last reply Reply Quote 0
                    • D
                      doylet8456
                      last edited by

                      Hey, I’m seeing exactly the same thing with my OpenVPN server. Were you able to determine the issue ?

                      My video streaming suffers due to the dip. Thanks for showing me the traffic graph package, now I can visually see what I’m seeing onscreen (OLED).

                      B 1 Reply Last reply Reply Quote 0
                      • JKnottJ
                        JKnott @blwag
                        last edited by

                        @blwag said in VPN throughput dips:

                        remote <host> 443 tcp-client

                        why are you using TCP for a VPN? That can cause flow control issues, as both the computer and firewall are trying to do flow control. You should use UDP for VPNs, unless you have no other option.

                        PfSense running on Qotom mini PC
                        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                        UniFi AC-Lite access point

                        I haven't lost my mind. It's around here...somewhere...

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          blwag @JKnott
                          last edited by

                          @jknott I travel quite a bit for work and outbound network policies seem to differ from office to office. The common denominator is tcp/443. It's the easiest way to know that my VPN will always work.

                          1 Reply Last reply Reply Quote 0
                          • B
                            blwag @doylet8456
                            last edited by

                            @doylet8456 I'm currently on Holiday break from work, so I haven't been at the office to do any additional testing. I will after the new year. I haven't found a smoking gun, so my guess is the throughput is the same.

                            1 Reply Last reply Reply Quote 0
                            • DerelictD
                              Derelict LAYER 8 Netgate
                              last edited by

                              TCP in TCP is far from ideal, as you are finding out. I would at least test using UDP for the tunnel and see if your issues go away there.

                              Chattanooga, Tennessee, USA
                              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                              Do Not Chat For Help! NO_WAN_EGRESS(TM)

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