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

    Openvpn site-to-site, ping only from client

    OpenVPN
    2
    4
    1.0k
    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.
    • S
      spillek
      last edited by

      Hi..
      I have two pfsense with openvpn site-to-site and shared key, but seem work only for the client;
      if I ping from the GUI of client-pfsense I see everything, the server tunnel and the lan behind the server-pfsense.
      if I ping from the GUI of client-pfsense  I see nothing, even the client tunnel, much less the behind lan
      I tried to "open" all in the rules and put the "route" in openvpn advanced option, but nothing …
      any idea ?

      thanks in advance, best regards.

      1 Reply Last reply Reply Quote 0
      • M
        marvosa
        last edited by

        Post the server1.conf from the server and client1.conf from the client.

        Also, please rephrase this… it is unclear what you mean:

        if I ping from the GUI of client-pfsense I see everything, the server tunnel and the lan behind the server-pfsense.
        if I ping from the GUI of client-pfsense  I see nothing, even the client tunnel, much less the behind lan

        add an any/any rule on both sides (firewall -> rules -> openvpn tab) until we get it communicating properly.

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

          any/any rule on both sides (firewall -> rules -> openvpn tab) already exist
          rephrase this:
          if I make a ping from the GUI of client-pfsense, I get response from server tunnel IP,  and from the lan behind the server-pfsense.
          if I make a ping from the GUI of server-pfsense I get response only from server tunnel IP, but I do not get any response from client tunnel IP, much less the behind lan

          :(

          1 Reply Last reply Reply Quote 0
          • M
            marvosa
            last edited by

            If you have any/any on both sides, it's probably a routing issue, but we need the .conf files from both sides to troubleshoot effectively.

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