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

    LAN user Can't ping to Remote VPN Road Warrior

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 1.9k 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
      farrukhndm
      last edited by

      My scenario is
      LAN NEtwork =192.168.1.0/24
      LAN Gateway for All machines =192.168.1.3
      WAN            =16.22.16.1
      pfsense        =192.168.1.3
      OpenVPN Client Subnet=192.168.2.0/24

      i have configured openvpn for my laptop user and it connects and get ip address 192.168.2.6
      when i ping to my LAN IP address behind OPENVPN <pfsenese>it can ping to 192.168.1.47
      and tracert

      C:\Documents and Settings\Administrator>tracert 192.168.1.47

      Tracing route to 192.168.1.47 over a maximum of 30 hops

      1  200 ms  200 ms    301 ms  192.168.2.1

      1  250 ms  224 ms    30 ms  192.168.1.47

      I can easy reach from Remote computer to MY LAN without problem
      –----------------
      Problem is below

      i can't access Remote VPN  connected machine from MY LAN IPS ???

      When from LAN machine 192.168.1.47 i tracert
      C:\Documents and Settings\Administrator>tracert 192.168.2.6

      Tracing route to 192.168.2.6 over a maximum of 30 hops

      1    38 ms    1 ms    1 ms  16.22.16.1
        2    55 ms    57 ms    62 ms  2xx.2.180.252
        3    51 ms    59 ms    57 ms  2xx.2.180.69
        4    89 ms    84 ms    76 ms  1xx.xx.129.145
        5    73 ms    73 ms    74 ms  xx7.xx.31.13
        6    *        *        *    Request timed out.

      It means no routes for 192.168.2.0 are available in pfsense and it send all traffic to WAN interface 16.22.16.1 .
      how to resolve this situations.thanks.</pfsenese>

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

        Still waiting for reply ???? Any one plz… :( :( :( :( :( :( :( :( :(

        1 Reply Last reply Reply Quote 0
        • N
          Nikolow-Niki
          last edited by

          I had the same problem and added advansed options in the following command:
          push "route 192.168.2.0 255.255.255.0";

          Look at this guide or introduction to the whole blog http://blog.stefcho.eu/?p=492

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