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

    OpenVPN CPU Usage after WAN outage

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    3 Posts 2 Posters 824 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.
    • F
      FisherKing
      last edited by

      Running 2.2-BETA (i386)
      built on Fri Oct 17 11:29:18 CDT 2014

      Had an outage on my WAN connection this evening for a few minutes. When the connection came back up again, my OpenVPN client connection spiked the CPU and stayed there. A connection to YouTube (not routed over VPN) was disrupted until I restarted the client.  An RDP connection, also not routed over the VPN, recovered before the client was restarted.  IMAP and SMTP traffic was disrupted until the restart.

      I'm sorry I don't have much in the way of detail. I understand this is a work in progress. Just reporting what happened. I can provide logs if needed - let me know which ones.

      1 Reply Last reply Reply Quote 0
      • F
        firewalluser
        last edited by

        As and when this happens again, do the unresponsive connections come back when you kill the states to these services?
        Diagnostic, States, select the ip address that links to one of your unresponsive connections and delete it.

        Does the connection come back and behave like normal after a period of time?

        This sounds a bit like what happens to asterisk users when the wan ip changes, hence the above.

        Capitalism, currently The World's best Entertainment Control System and YOU cant buy it! But you can buy this, or some of this or some of these

        Asch Conformity, mainly the blind leading the blind.

        1 Reply Last reply Reply Quote 0
        • F
          FisherKing
          last edited by

          Interesting observation.  I do have multiple wan connections, but there is at least one issue with routing traffic out the correct interface / gateway, so I'm not currently configured to failover / switch between WAN links.  The observed behavior all happened utilizing a single WAN link.

          I will test killing the the states for the frozen connections next time I see this.  Thanks for the suggestion.

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