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

P_CONTROL_HARD_RESET_CLIENT_V2 error

Scheduled Pinned Locked Moved OpenVPN
4 Posts 3 Posters 2.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.
  • J
    JKnott
    last edited by Apr 19, 2022, 8:43 PM

    I'm setting up OpenVPN between my notebook computer, running OpenSUSE Leap 15.3, with OpenVPN 2.5.3 client, and pfsense. The VPN works when the notebook is connected to my LAN, but not when coming in from an external address. When it fails I see P_CONTROL_HARD_RESET_CLIENT_V2 in Wireshark and Packet Capture. This indicates the packets are getting to my firewall, but the VPN is not connecting. Given that it connects while on the same LAN indicates the VPN settings are correct. My notebook is tethered to my cell phone, which is the same company as my ISP, but completely different IP address. However, NAT is used for IPv4 on my cell phone.

    Any idea what might be causing this?

    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...

    1 Reply Last reply Reply Quote 0
    • R
      Rico LAYER 8 Rebel Alliance
      last edited by Apr 20, 2022, 1:56 PM

      Did you pick the correct Interface in OpenVPN > Server Configuration?
      For Interface "Localhost" you manually need to NAT > Port Forward
      OC you need to have the correct Firewall Rules in place.

      -Rico

      J 1 Reply Last reply Apr 20, 2022, 7:18 PM Reply Quote 0
      • J
        JKnott @Rico
        last edited by Apr 20, 2022, 7:18 PM

        @rico

        The NAT is at the other end. My pfsense has a public address, so no NAT needed at this end.

        Here's the rule:

        121df6a2-46c0-429d-83b1-be3e7903212f-image.png

        As for interfaces, I currently have UDP IPv4 and IPv6 on all interfaces, though I have tried just UDP IPv4 on WAN interface. Either way, it does the same thing.

        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...

        R 1 Reply Last reply May 23, 2023, 10:54 PM Reply Quote 0
        • R
          riahc8 @JKnott
          last edited by May 23, 2023, 10:54 PM

          @jknott said in P_CONTROL_HARD_RESET_CLIENT_V2 error:

          @rico

          The NAT is at the other end. My pfsense has a public address, so no NAT needed at this end.

          Here's the rule:

          121df6a2-46c0-429d-83b1-be3e7903212f-image.png

          As for interfaces, I currently have UDP IPv4 and IPv6 on all interfaces, though I have tried just UDP IPv4 on WAN interface. Either way, it does the same thing.

          For some reason, in the OpenVPN Server you have to set the interface as any, not WAN

          1 Reply Last reply Reply Quote 1
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            [[user:consent.lead]]
            [[user:consent.not_received]]