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

    Can't see hosts behind second gateway

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 1 Posters 1.7k 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.
    • M Offline
      mrsunfire
      last edited by

      Hi guys!

      I set up an OpenVPN Server on my pfSense 2.0.2. So far so good, I can connect and use the WAN. This is my setup:

      ISP modem –------ pfSense -------- DLink Router --------- PC's (192.168.0.x)
      external IP          192.168.1.1/24    192.168.1.199/24      - Server (192.168.0.197)

      OpenVPN is on 192.168.3.0/24. If I now connect with a device to the VPN, it gets for example the 192.168.3.6. Now I can ping the router (192.168.1.199), or show webpages from the server via 192.168.1.199. I also can ping FROM the Server (192.168.0.197) to the device (192.168.3.6) but I can't ping TO the server (192.168.0.197). Every IP from DLink routers LAN (192.168.0.x) I can't ping. pfSense also can't ping, or trace them.

      I think the problem is, that pfSense don't knows where the 192.168.0.x addresses are. But I'm on my end to try to learn them.

      How can I learn pfSense to route all the 192.168.0.x addresses over the DLink router (192.168.1.199), or where is my problem?

      Netgate 6100 MAX

      1 Reply Last reply Reply Quote 0
      • M Offline
        mrsunfire
        last edited by

        Well, as it seems he pfSense is working fine. I think the problem is, that the DLink router is a router with a NAT. So he can't route all from WAN to LAN. Accessing LAN via WAN seems impossible.

        If I setup a static route for 192.168.0.0/24 with gateway 192.168.1.199 in pfSense and try to ping 192.168.0.197, I can see on logs that there is an attemp to reach via the route, but nothing happens. So I think the DLink gets the order on his WAN to route the request to 192.168.0.197, but he says "no, I don't let you access the LAN subnet".

        Might this be the problem?

        Netgate 6100 MAX

        1 Reply Last reply Reply Quote 0
        • M Offline
          mrsunfire
          last edited by

          This was the problem! DLink Router can't route LAN IP's from the WAN side, to the LAN side!

          How to solve? -> connect the LAN from pfsense to a LAN of the router! Don't use WAN side anymore and DEACTIVATE (!!) DHCP and UPnP on router!

          Thats it!

          Netgate 6100 MAX

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