You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, is there a way to prevent the dhcp server from issuing ip's referenced in the list of reservations? it seems that if the reservations are within the pool, there can still be a conflict as the server will issue an ip that can also be taken by a reservation.
The text was updated successfully, but these errors were encountered:
In the config file the normal pool start-end range should not overlap the reservation ranges, but it's true there's no validation or warning when they do. To fix this I could choose one of these:
validate and warn if there's an overlap
allow overlap but automatically exclude reservation ranges from the normal pool
I should have a look and see what's a common way of handling this in other dhcp servers.
It seems that we should allow overlap of reservations and the pool. But we need to make sure that the dhcp server will NOT assign ip's that are reserved. This would allow both scenarios to be covered. Users that are keeping it outside the range could validate the reservations and not allow overlap. But to keep users from having to power cycle their devices, the server should never assign an IP that has a reservation. Can we do it that way?
Hi, is there a way to prevent the dhcp server from issuing ip's referenced in the list of reservations? it seems that if the reservations are within the pool, there can still be a conflict as the server will issue an ip that can also be taken by a reservation.
The text was updated successfully, but these errors were encountered: