Ticket #842 (closed defect: fixed)
Ebox DHCP Server doesn't have custom options - useless in network boot environment
|Reported by:||danson.joseph@…||Owned by:||ejhernandez@…|
|Severity:||normal||Keywords:||DNS DHCP network boot|
I am really enjoying ebox as a platform, and use it in a school environment as the firewall/dhcp/dns server. One big problem for thin-client operation is that the dhcp portion does not have the option for "filename" or "next-server" or possibly custom options. This means as soon as I modify the dhcp server via ebox, I have to go in and modify the dhcpd.conf file manually again and again.
Additionally, dhcp and dns do not work together as a ddns system which is silly given that they are on one unified system.
I can provide testing facilities at the school.
Regards, Danson Joseph
- Owner changed from juruen@… to ejhernandez@…
- Status changed from new to assigned
- Milestone set to 0.12
- hours changed from 0 to 8
- Status changed from assigned to closed
- Resolution set to fixed
- totalhours changed from 0.0 to 8.0