Anyone else noticed this? Reservations seem to work fine for majority of devices after a reboot or wifi toggle but windows 10 doesn't seem to be working.
I did a packet capture and can see my device sending a DHCP option 50 with its previous used IP address in the request. Not sure if its aligning to an RFC but assume its always done this? So I'm thinking firewalla is just accepting this instead of offering the new reserved IP?
I had ddwrt on my router and reservations worked fine for all so wondering if there is something up with firewalla implementation?
Had to move r7000 back to stock, DDWRT caused speed slowdowns and was unstable. It was previously in simple mode however decided to switch to DHCP so I could use the reservation feature as it comes in handy.
I have a Firewalla blue with a netgear r7000. I switched my netgear to 192.168.0.0/24 and set the overlay to 192.168.1.0/24 (Firewalla is 192.168.1.1 in the overlay).
Please sign in to leave a comment.