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

    Port forwarding from Local network connected to WAN of PFsense

    Scheduled Pinned Locked Moved NAT
    2 Posts 1 Posters 306 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
      craig121
      last edited by

      Good morning,

      I hope someone can give me some advice around setting up Pfsense to allow me to port forward from my local network to the Pfsense router on the WAN directly. Even to ping the Pfsense router would be a step closer from the main local subnet.

      I have tested and confirmed that if I port forward from my main router to the Pfsense router WAN, I can then for example SSH from my public address it works fine.

      I also have the issue of not being about to ping my Pfsense router from my local subnet e.g from a iMac on 192.168.1.10 and my Pfsense WAN setup on 192.168.1.100 ( I get timeout for all requests). I dont think its firewall for the ping as I setup in the firewall rules to pass ICMP on WAN.

      For info - I can ping all main local subnet IP from Pfsense without any issues.

      Please see attached for my drawing of my network, apologies I am not a network engineer if i am asking any dumb questions.

      All of my main LAN clients are mainly on DHCP with the exception of a couple of static IP.

      All of the Pfsense LAN clients are on DHCP and all fine without any issues.

      7e486d86-0300-42c6-b967-f546abdafb24-image.png

      As a work around i could port forward from my main router to Pfsense but i would rather minimise external access into my network.

      Thanks

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

        The issue was due to blocking private networks on the WAN interface.

        I disabled the Block private network under Reserved networks and everything is working as expected now.

        a65ef545-6a79-43ba-89c9-88644af1e737-image.png 

        Hope this helps anyone else that experiences a similar problem.

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