DHCP vs Static IP Addressing
Posted: Thu Jan 03, 2013 9:16 pm
I have a few questions about DHCP and Static IP Addressing.
(1) It seems to me that an IT savy user could set their own static IP address in order to get a new quota. Is that correct?
(2) Is static addressing purely just that, or does that option double as a reservation for IP addresses that are inside the scope, therefore stopping users from beating the quota?
(3) Is it possible to set a quota by mac address rather than IP, or should I include that as a feature request?
(4) Is it possible to set a TFTP server in the DHCP options? Scope options are not in the GUI, but presumably this could be done from ssh? I need this option in order to allow my Cisco phones to find their configuration files located in a tftp server in a FreePBX phone server. Are there any files in DHCP setup that are automatically overwritten, which would defeat my setting this option?
(1) It seems to me that an IT savy user could set their own static IP address in order to get a new quota. Is that correct?
(2) Is static addressing purely just that, or does that option double as a reservation for IP addresses that are inside the scope, therefore stopping users from beating the quota?
(3) Is it possible to set a quota by mac address rather than IP, or should I include that as a feature request?
(4) Is it possible to set a TFTP server in the DHCP options? Scope options are not in the GUI, but presumably this could be done from ssh? I need this option in order to allow my Cisco phones to find their configuration files located in a tftp server in a FreePBX phone server. Are there any files in DHCP setup that are automatically overwritten, which would defeat my setting this option?