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

    Question about routing

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 914 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.
    • J
      jaapi
      last edited by

      Hi,

      Thx in advance for the help… I'm learning pfSense, so I'm new :-)

      Situation:

      ISP modem/router: LAN 192.168.0.0/24
      pfsense: WAN 192.168.0.2 ,  LAN 192.168.10.0/24 and 192.168.10.1 (NAT and Firewall are turned off)

      in the 192.168.0.0 subnet I have my desktop pc and the stuff from the family
      in the 192.168.10.0 subnet I have a winserver 2012 and some linux machines that i use for testing (school)

      With firewall turned off, I can ping from the wanside to the lanside witheout problems, I can start ssh sessions and use remote desktop to reach the 2012server

      But what doesn't seem to work is is accessing the machines from the lan to the wan side... ping does not work, tracert and traceroute hang on 192.168.10.1 (default gateway and ipaddress from pfsense)... so somehow pfsense routes traffic from wan to lan, but not from lan to wan, unless in a session (ssh, rds).

      I can also access shared folders on the server from my desktop... but not the other way around, unless there is an open remote desktop session. Then de server recognises \tsclient , but not the actual ipadress

      Anyone an idea whats the reason for this?

      1 Reply Last reply Reply Quote 0
      • J
        jaapi
        last edited by

        nobody?? really??  :o

        1 Reply Last reply Reply Quote 0
        • T
          timthetortoise
          last edited by

          On your WAN interface, make sure "block private networks" is not checked.
          Other than that, it sounds like it may be Windows firewall at fault. Disable the firewall on your desktop machine and test again.

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