Features, bugs, etc for the OpenNetAdmin web interface
| Tasklist |

FS#68 - Not all DHCP settings can be set

Attached to Project: OpenNetAdmin Web Interface
Opened by Tim Bates (tin) - Monday, 30 November 2009, 16:19 GMT-6
Task Type Feature Request
Category Backend / Core
Status Assigned
Assigned To Matt Pascoe (matt)
Operating System All
Severity Low
Priority Normal
Reported Version 09.09.15
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

It would be quite handy to be able to set server settings for DHCP, particularly ISC DHCPD.

Settings such as "authoritative", "max-lease", etc would be nice to have accessible via the web front end, but currently don't appear to be configurable.

I am aware that the current build_dhcpd result can just be included in another DHCP config, but it would be nice to be able to set everything in one place to avoid some of the guesswork.
This task depends upon

Comment by Matt Pascoe (matt) - Monday, 30 November 2009, 21:39 GMT-6
I do think that having a GUI would be nice but it presents a lot of challenges due to the sheer amount of settings that could be managed.

This is the reason why I have chosen to just let the end user handle whatever they need by including a text file that they have edited with whatever settings appropriate.

With that said, I think a possible compromise would be to have the text file that includes all of this extra configuration be stored in the ONA database for the appropriate server. That way you would be able to view its contents in the web gui as well as edit it in the GUI. You would need to know ISC DHCPD configuration syntax but you would be able to do ANYTHING you wanted at that level. I've got some initial thoughts on how to do this in a way that would apply to DNS servers of various flavors as well as other services.

Thoughts?
Comment by Tim Bates (tin) - Tuesday, 01 December 2009, 02:39 GMT-6
Sounds like a fair enough start to just store a bunch of text and embed it in the output (towards the top?).

Would it be going too far to have each line as a record in the database with a field to enable and disable a given line?

Loading...