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

    Migrating static dhcp mappings to new interface

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 1 Posters 1.3k 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.
    • rmaederR
      rmaeder
      last edited by

      I've changed the connection between the pfSense router and the internal switch to use VLANs, and so there is a new interface in pfSense that is now my lan connection. The dhcp server is a bit stubborn; I had to enable a new instance on the new interface, but all static mappings are somehow still attached to the old instance on the previous LAN. As a consequence the configured static addresses are not delivered to the clients asking for them on the new interface.
      I can still find them when I got to "related status" (https://router/status_dhcp_leases.php).
      I tried to edit one of them and save it, but there is an error:
      The IP address must lie in the LAN subnet.
      But the LAN interface no longer has a subnet; that is now with the new interface.

      Is there a way to move these over in bulk. I'd hate to type all of them in again.

      Roman

      rmaederR 1 Reply Last reply Reply Quote 0
      • rmaederR
        rmaeder @rmaeder
        last edited by

        I found a hack to move the static mappings over: I exported the dhcp settings, edited the xml file to change the interface name, then restored the dhcp settings from the uploaded file.
        There was one confusion that sometimes the dhcp settings page, which has only one tab for the one new lan interface, would not have that tab selected, so it looked like the settings were not present. Clicking on the tab showed them.
        In hindsight it would probably have been better to rename the interface and assign it the new port, rather than create a new one as I did.

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