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

    DHCP on WAN interface will not release the public IP

    Scheduled Pinned Locked Moved DHCP and DNS
    5 Posts 2 Posters 2.7k 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.
    • M
      mcm311
      last edited by

      I use pFsense to connect to 4 different company offices I use for work. Because of issues I have not been able to resolve I cannot leave the router online 24/7 because it interferes with video on demand services from Verizon. I am looking for a solution to that but in the mean time I have this other issue.

      So the problem I have is when I want to remove the pFsense box from the network and move over the ActionTec router, I have to release the public IP or the AT router will not be able to pick up the IP.

      In pFsense I tell it to release the IP, which according to the GUI it appears to do just that. But if you look at Wireshark captures I can see that it never sends DHCPRELEASE to the network. Because of this the AT router never picks up an IP and I need to call FiOS tech suport and tell them to break my lease. Sometimes that takes forever depending on how busy they are and how long I am on hold.

      I tried releasing it from a command line as well but that did not seem to work. I can get it to renew the IP using cli but not release. Maybe the command I am using is not correct. I can renew it by running:

      dhclient il0

      Pretty sure the correct syntax to release should be dhclient -r il0 but that does not work. Neither does dhclient il0 -r

      Anyone have any ideas to get around this? I was running 1.2.3  but I have since upgraded to the latest 2x version and still have the same issue

      1 Reply Last reply Reply Quote 0
      • N
        NOYB
        last edited by

        This patch for dhclient additional options and override dhclient config file may be useful:

        http://forum.pfsense.org/index.php/topic,40194.0.html

        There are ways for the determined.

        I've gone so far as to do this before.  A bit tricky and delicate, but it works.

        http://www.dslreports.com/forum/r27210694-FiOS-Dual-Router-Separated-Computer-TV-Service-Networks

        1 Reply Last reply Reply Quote 0
        • M
          mcm311
          last edited by

          Does not look like the additional options will help at here.

          As far as the dual router, not sure if that will do what I need either. In that setup it looks like the feed from the ONT is coax but mine is CAT5.

          1 Reply Last reply Reply Quote 0
          • N
            NOYB
            last edited by

            @mcm311:

            Does not look like the additional options will help at here.

            As far as the dual router, not sure if that will do what I need either. In that setup it looks like the feed from the ONT is coax but mine is CAT5.

            Use the additional options to create a pfSense WAN DHCP client config that imitates the Actiontec.  Then you can switch between the two without even having to release the IP address.

            The dual router setup is CAT5 feed from ONT.  CoAX from ONT only carries TV signal.

            1 Reply Last reply Reply Quote 0
            • M
              mcm311
              last edited by

              I'll give that a try, thanks

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