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

    How to allow only one source IP in NAT configuration

    Scheduled Pinned Locked Moved NAT
    5 Posts 3 Posters 887 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.
    • D
      deepakaagrwal
      last edited by

      Hello All,

      I have a computer with static IP which I want to access from outside network remotely, in order to test it I have configured NAT and allowed only one  IP (Static Ip) and it is working fine, same I want to do this  for dynamic IP as I have modem which don't have static Ip address then how to overcome from this issue.

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        Add an IP alias in Firewall > Aliases (here you may also use FQDNs) and use this alias in the (NAT) rule.

        1 Reply Last reply Reply Quote 0
        • D
          deepakaagrwal
          last edited by

          Dear viragomann , thanks for your reply, as you know that My ISP provide me dynamic IP and it's ip changing frequently then how can I create a alias with IP please guide

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

            You want to allow a port forward from a single source IP address but that source IP address is always changing?

            You might be able to get there with a dynamic DNS entry and an alias populated by that FQDN.  I don't know how often pfSense updates its FQDN aliases but having it do it often enough to make that work seems pretty ham-fisted.

            Use an OpenVPN remote access server instead.

            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
            • D
              deepakaagrwal
              last edited by

              Dear Derelict,

              Thanks for your advice, I will try it.

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