Small DHCP IP pool bug

[rdallen]

Thought I might report a small bug in Merlin, which has been around for a while.

I have two RT-AC68U routers. Every now and then I install the latest Merlin firmware on the unused RT-AC68U, and switch them.
Whenever I change the IP address of the router, it insists on changing the DHCP server pool of addresses back to the default, even though the IP address change is on the same subnet.
So, I change the IP address from 192.168.10.1 to 192.168.10.2. DHCP pool is set to 192.168.10.100-192.168.10.150
When I change the address, it insists on changing my DHCP pool to 192.168.10.2 - 192.168.10.254 (if I remember correctly, but whatever the default is). I then have to log back in, and change it back.

Why does it insist of changing my DHCP pool when the IP address is on the same subnet?

 

[retzer]

I've noticed the something similar. I've been playing around since 384.5 and after each session I'll reset the router to 192.168.1.1 and reset the DHCP pool to 192.168.1.100 - 192.168.1.254, leaving the lower addresses for static IPs. But soon after reconfiguration the pool always reverts to 192.168.1.2 - 192.168.1.254. Only after resetting a second time will it stick. Not a big deal but I was wondering if there's any good reason for that.

 

[RMerlin]

I've noticed the something similar. I've been playing around since 384.5 and after each session I'll reset the router to 192.168.1.1 and reset the DHCP pool to 192.168.1.100 - 192.168.1.254, leaving the lower addresses for static IPs. But soon after reconfiguration the pool always reverts to 192.168.1.2 - 192.168.1.254. Only after resetting a second time will it stick. Not a big deal but I was wondering if there's any good reason for that.

Because adjusting the pool while ensuring it's within the (possibly different) subnet would be quite tricky. That's why on an IP change, the pool will adjust to the new subnet, using the default range.