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

    Routing between VPN client and LAN client

    Scheduled Pinned Locked Moved OpenVPN
    6 Posts 2 Posters 1.5k 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.
    • C
      cesjr
      last edited by

      Hi guys
      I have set up a openVPN Server and it is working fine.
      But how should I let them can communicate with each other

      LAN : 192.168.1.1
      WAN : WAN IP
      Tunnel network : 172.16.0.0 /26

      After the connection have been established ,  I can ping from 172.16.0.2 to 192.168.1.1 , but can't ping 192.168.1.x /24 behind the 192.168.1.1
      I also try to add a virtual interface 172.16.0.62 , I using ping tools on pfsense to ping from LAN to 172.16.0.1 and 172.16.0.62 , it is success
      How should I let 172.16.0.1 can ping 192.168.1.20 , thanks

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Check the local firewall on host 192.168.1.20. Make sure it allows connections from outside its local subnet.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • C
          cesjr
          last edited by

          the 192.168.1.20 is a freebsd server , I add route  " route add -net 172.16.0.0/26 192.168.1.1" , but it is still failed  :-X

          1 Reply Last reply Reply Quote 0
          • C
            cesjr
            last edited by

            well , I add push "route 192.168.1.0 255.255.255.0" on Advanced Configuration
            but it still not working ….

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              If that is already in Local Networks on the server that is redundant.

              Really. If the OpenVPN clients can ping 192.168.1.1 but not 192.168.1.20, check the firewall on 192.168.1.20.

              FreeBSD has them too. pfSense is one.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 0
              • C
                cesjr
                last edited by

                Thanks , I found the problem
                I change the GW of 192.168.1.20 from 192.168.1.23 to 192.168.1.1 and permit firewall rules allow on WAN from any to 192.168.1.20 (specfic port).
                And now I can ping 192.168.1.20 from vpn client.
                But , I have another question , why I can not add static route , like "add net 172.16.0.0/26 192.168.1.1" to  achive my gole .
                It seems like it is the only way to change the default GW , if the clint build the connection with me , it should be "in firewall subnet" , am I right ? some client's GW with 192.168.1.247 have same situation.

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