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

    Problem with NAT

    Scheduled Pinned Locked Moved NAT
    4 Posts 2 Posters 653 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.
    • A Offline
      avarela
      last edited by

      Hi,

      I Have this scenario:

      My Pfsense has two network

      Lan -192.168.0.19
      Wan - 192.168.1.67 (DHCP) - i get this ip from my router

      My router
      router is use protocol ipoe, is the default gateway

      So i have a service that i want to acess outside from my networks. so i make my nat rules

      NAT

      Interface:wan
      protocol:tcp
      source address: any
      source ports:any
      dest. address:wan address
      dest. ports:491
      NAT IP:192.168.1.223
      NAT ports:491
      Nat reflection:use systems default
      filter rule association:create new associated filter rule

      On my system->advanced->firewall & NAT

      Nat reflection mode :disabled
      Enable nat reflection:no check
      enable automatic outbound no check

      when i try to access my network from outside, my nat rule is not working, i use portchecktool.com i got this message could not see service on port 491. can you help me please.

      1 Reply Last reply Reply Quote 0
      • johnpozJ Online
        johnpoz LAYER 8 Global Moderator
        last edited by

        "NAT IP:192.168.1.223"

        How would that work?  If your lan is 192.168.0

        Your wan is also rfc1918, so whatever is doing nat in front of pfsense would have to allow the traffic into pfsense WAN IP before pfsense could forward it on to something on its lan.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 25.07 | Lab VMs 2.8, 25.07

        1 Reply Last reply Reply Quote 0
        • A Offline
          avarela
          last edited by

          sorry i make mistake, i mean NAT IP:192.168.0.223, and i don´t have checked in wan interface on my block private networks and loopback addresses. i don´t understand what do you mean i have rfc1918. My nat rule still don´t work it

          1 Reply Last reply Reply Quote 0
          • johnpozJ Online
            johnpoz LAYER 8 Global Moderator
            last edited by

            your pfsense wan is private IP, ie its not public. So there is something in front of it doing nat..

            Your other router or isp device is changing your public IP to the is private (rfc1918 address)

            "Wan - 192.168.1.67 (DHCP) - i get this ip from my router "

            So you need to make sure you forward whatever it is you want to forward on that device to pfsense wan IP.

            Since you will be sending traffic to rfc1918 (your pfsense wan) you will need to make sure you uncheck the block rfc1918 on wan.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 25.07 | Lab VMs 2.8, 25.07

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