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

    OpenVPN clients with shared key configuration adding gateway as 255.255.255.0

    OpenVPN
    2
    3
    458
    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
      Bohodir
      last edited by

      Hello Pfsense Community.

      I need your expertise, I have strange behavior lately on my Pfsense 2.7 OpenVPN nodes. Routing table shows 255.255.255.0 as gateway to my specific Pfsense OpenVPN server connections, those servers are configured with OpenVPN shared key option as you see below picture, other clients showing exactly OpenVPN servers ip address as it should.
      image_2023-07-23_103904517.png

      Here is my setup:

      Server: PfSense 2.7 (shared key)
      Client: Pfsense 2.7 (shared key)

      I had to use shared key now due to IDS on client side ISP, they somehow started blocking TLS streams, only way for workaround is to use shared key and it is working.

      My question here is why actual ip address is not assigned as gateway. Do I missing anything ? I have not changed any configs since upgrade, wondering new
      version on Pfsense 2.7 changed.

      H 1 Reply Last reply Reply Quote 0
      • H
        hr1sha @Bohodir
        last edited by

        @Bohodir small lyrical digression. But you can use openvpn inside SSL/TLS, but you will lose performance and be forced to use TCP.Then your ISP will not block the VPN. You can also check if your ISP will block an unobfuscated TCP connection with an SSL/TLS key configuration

        B 1 Reply Last reply Reply Quote 0
        • B
          Bohodir @hr1sha
          last edited by

          @hr1sha thank you for your responses, yea I have tried TCP and working just fine but performance worsens. ISP does not blocking un-obfuscated TCP connection with an SSL/TLS key configuration for some reason.

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