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

    Network behind openvpn client can not ping openvpn server

    Scheduled Pinned Locked Moved OpenVPN
    7 Posts 2 Posters 784 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.
    • V
      vjfromgt
      last edited by

      pc (a) ----pfsense openvpn CLIENT (b)------- openvpn server (c) -----server (d)

      b can reach c
      b can reach d

      a can reach b
      a can not reach c or d

      Routing table shows that the routes exist.

      If I replace the pf router with lets say a ddwrt, all work fine.

      What am I doing wrong?

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @vjfromgt
        last edited by

        @vjfromgt said in Network behind openvpn client can not ping openvpn server:

        If I replace the pf router with lets say a ddwrt, all work fine.

        Doing so, do you see the clients source IP at c and d? Or is it replaced by b?

        1 Reply Last reply Reply Quote 0
        • V
          vjfromgt
          last edited by

          c and d do not see any attempt from a
          nothing in tcpdump when I ping from a to C

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @vjfromgt
            last edited by

            @vjfromgt
            With the ddwrt, what so you see as source IP, when accessing from a?

            1 Reply Last reply Reply Quote 0
            • V
              vjfromgt
              last edited by

              replaced by b

              V 1 Reply Last reply Reply Quote 0
              • V
                viragomann @vjfromgt
                last edited by

                @vjfromgt
                pfSense doesn't do this by default.
                But you can manually add an outbound NAT rule.

                So either there might be the routes missing to a at c and d or it is blocked by the firewall.

                V 1 Reply Last reply Reply Quote 0
                • V
                  vjfromgt @viragomann
                  last edited by

                  @viragomann

                  Thanks
                  this did the trick

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