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

    Is there any way to have a built in alias (per interface) of all DHCP IPs?

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 3 Posters 985 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.
    • T
      Trel
      last edited by

      Is there any way to have an alias made per interface for every IP registered in the DHCP server?
      Including anything that was static or dynamically assigned that would update as leases are created or expire?

      I was thinking along the lines of something like DHCP_LAN being an autogenerated alias.

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

        Would an alias matching the DHCP scope be enough? Or is that too much or too little for what you are trying to achieve?

        pfSense AMD64 VGA - Assume latest version.
        Suricata, pfBlockerNG, SquidGuard, squid3.

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

          If you create your DHCP pools on subnet boundaries you can do the same thing with simple network aliases.

          No, there's nothing like this currently nor in any future versions, as far as I know.

          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
          • T
            Trel
            last edited by

            @jonesr:

            Would an alias matching the DHCP scope be enough? Or is that too much or too little for what you are trying to achieve?

            No, the idea I was thinking was to put a block rule against anything not that alias, such that machines that were connected with a static IP that wasn't registered to DHCP wouldn't be able to get out of the LAN.

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

              So put a block rule for anything not that alias.

              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
              • T
                Trel
                last edited by

                @Derelict:

                So put a block rule for anything not that alias.

                Yes.
                But I was asking if there was any way to automatically create and maintain that alias, not about the rule I intend to use it in.

                If it's not, then oh well.  Was just a thought.

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