DHCP: Allow static lease of addresses within the dynamic pool
Currently it is not possible in the Sophos XG to store static DHCP leases in the internal DHCP server where the IP addresses are located within the configured DHCP pool. This is with other manufacturers such. B. AVM (Fritz! Box) without problems possible. Thus here is the DHCP for large customers currently partly to use. When will this be a solution.
Aktuell ist es in der Sophos XG nicht möglich Statische DHCP Leases im internen DHCP Server zu hinterlegen, bei denen die IP Adressen sich innerhalb des konfigurierten DHCP Pool befinden. Dies ist bei anderen Herstellern wie z. B. AVM (Fritz!Box) ohne Probleme möglich. Somit ist hier der DHCP für Großkunden aktuell nun teilweise zu gebrauchen. Wann wird es hierzu eine Lösung geben.
Michael Kaiser
shared this idea
10 comments
-
Andre
commented
This really needs to be added. I don't know of any other product that has a DHCP server which this cannot be done.. We came from Sophos UTM (where this was possible) over to XG and it's quite disappointing that features like this and many others are missing.... Sophos please add this!
-
Michael
commented
Hello all,
it is already possible to assign a fixed mac - IP binding in the DHCP server.
From my point of view the static and dynamic range schould stay separated.
Why?
If one will use the dynamic range with fixed mappings, the number of clients to connect dynamically will decrease - suddenly to 0!It is up to every admin to very well plan the usage of IP address ranges within the complete network range to avoid IP address conflicts.
1. Network devices like routers, switches, access points and so on
2. Servers
3. Printers, Scanner devices and Clients / Workstations that are always present
4. Portable devices like Laptops, card phones and so on, that will not be always connected1 to 2 is always static with a fixed IP configured
3 is static or may be assigned to a fixed mapping via DHCP outside of the dynamic range
4 is normally dynamic and the IP comes out of the dynamic range. In some cases one can behave like 3 with some devices here.
So one has to devide the static from the dynamic range(s) to prevent running out of free IPs of the dynamic part and / or to prevent IP address conflicts.
In Short:There is no need for this request / function and I dissagree to this request.
Sorry -
Simon
commented
Being able to set a dynamic IP to static is basic key functionality of just about every enterprise DHCP server. It's often essentially to lock in a current IP of a host. The inability to set a current IP to static is painful. The need for that IP to be outside the dynamic IP scope is just a ridiculous limitation especially if deploying into an existing network. This is the second deployment where I've had to deploy a 3rd party DHCP server to accomodate the requirements of an existing IP subnet. Fix this short sighted insanity please.
-
Alexandre
commented
I abound on this subject. No way from Sophos, must be implemented. Actually, I must use Microsoft DHCP to resolve this gap...
-
Anonymous
commented
Sophos, please, thank you
-
Nicholas
commented
Static IP reservation is important. As many customers have this requirements for a DHCP server.
-
Sean
commented
In some cases it is preferable to set a static DHCP reservation inside the range allocated to dynamic clients.
Adding this ability would also allow fulfillment of this other feature request: https://ideas.sophos.com/forums/330219-xg-firewall/suggestions/11707182-dhcp-static-assignment-from-list-of-leases -
Chris
commented
See also: Cant reserve IP Address in the DHCP Pool
-
Rob Grafton
commented
It was pretty bad to manage DHCP on the preceeding Cyberoam devices. Having to make a new dhcp range and not include anything you want to reserve is a pain, especially if you have devices in the middle of your DHCP scope you want to statically assign. The windows DHCP management is not perfect but its simple enough to use and understand, something similar in function would be great.
-
Grant
commented
It would be great if the DHCP configuration could be simplified.
1/ Make static IP from an assigned IP would be great.
2/ It would be nice to have a single DHCP pool with exceptions/exclusions/static assignments within that pool or outside that pool.References:
https://serverfault.com/questions/768655/how-dhcpd-handles-static-ips-vs-dhcp-reservations
https://linux.die.net/man/5/dhcpd.conf
