DHCP Reservations Very Broken

Comments

10 comments

  • Avatar
    Michael Bierman

    “ Device B comes online and before Device A gets its reservation Device B takes a.a.b.b”.

    I’ve never seen this. Are you saying Firewalla gave put that iP on its own?

    1
    Comment actions Permalink
  • Avatar
    Joshua Manton

    I’m using a 255.255.255.248 subnet so I’d imagine that would increase the likelihood. Also perhaps it is relevant to reproducing, I’m using a 2 port LAG with 2 VLANs each doing DHCP.

    0
    Comment actions Permalink
  • Avatar
    Joshua Manton

    I just had it happen again but on a larger network. It's really a problem.

    0
    Comment actions Permalink
  • Avatar
    Yoav freiberger

    it gets even worse than that:

    1. Device A can ignore DNS reservation, even when it doesn't have a static IP assigned to it,and continue to connect is it wishes,for example AdGuard Home on raspberry pi

    2. Device a can connect to subnetwork X through appropriate AP, then when I make it forget the password for the access point and force it to connect to submet Y (HomePod trying to tag onto mine iOS network), it is able to connect through access point for subnetwork Y to IP range in subnetwork X completely to segregate it

     

    but not much more basically that: no UI feature as an every simple router to renew DHCP lease.This means:

    3. Setting static IP only after device connects to specific subnetwork requires rebooting the device and sometimes even leaving it powered off for a few minutes, when rearranging the network this means multiple devices

    4. Worse yet, not being able to renew lease from Firewalla you UI, means that changes are made to two instances of AdGuard Home this week' IP addresses, not only require rebooting,it's impossible to know that some of the 50 devices I need to reboot are still on the old settings,since IP appears correct,only in network flows I can see blocked traffic too old DNS server location,which requires a lot of digging and endlessly reboots

     

     

     

     

     

    0
    Comment actions Permalink
  • Avatar
    Joshua Manton

    My guess, and I don't have time at the moment to investigation, is that the Firewalla is not playing nicely with my Netgear MS510TXM switches. But it also may have something to do with the LAG. Like the DHCP reservation is still tied to an interface. 

    I should have taken a screen shot, but earlier today I had I multi-honed system with the same IP on each interface from Firewalla DHCP.

    If they give only limited functionality to control DHCP settings, that feature better work well.

    0
    Comment actions Permalink
  • Avatar
    Support Team

    Did you delete any IP reservations on these devices before? There is a bug in 1.977 that ip reservation deletion may not take effect.

    You may send email to help@firewalla.com that we can help check what's wrong.

    0
    Comment actions Permalink
  • Avatar
    Joshua Manton

    I had a reservation request for 3 days, I rebooted the server multiple times and it never took the reservation. I shut off DHCP on the firewalla for that network. I started using another system for DHCP and it works perfectly. For my main home LAN where I don’t need reservations, Firewalla woks fine. On the network where I actually want to control DHCP reservations the Firewalla did not perform its job.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    @joshua, I just created a ticket for you.  dhcp reservations is one of the basic features, likely there is just something simple to fix. 

    0
    Comment actions Permalink
  • Avatar
    John Barbieri

    I just wanted to write in this thread to say, that if you delete a reservation, it does not seem to actually delete it from the server. I changed my network around and I deleted a previous device that had a reservation, but now I am trying to get my new device to use the new reservation. Even though the app allows me to reserve that IP, it is still handing out from the dynamic DHCP pool. I actually have experienced this multiple times as I have deleted multiple devices that had reservations.

    Is there a way to force the deletions? Or just need to wait for the bug to be fixed (running 1.977).

     

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Corey Kronengold

    Any update here? I'm also running 1.977 and experiencing the same issue. 

    I have 3 Raspberry Pis that I was trying to sort out with DHCP reservations. I tried to switch an IP address from a laptop to one of the Pis, but it never takes. So I can't seem to assign x.x.x.28 to anything except the old laptop that I stole it from. 

    Basically hoping to force or speed up the deletions or freeing up an IP address from the table. 

    Thanks!

    0
    Comment actions Permalink

Please sign in to leave a comment.