Version 13 (modified by ejhernandez@…, 3 years ago) (diff)

Some things are now done but some of them partially

DHCP

Make PXE-Features Useful

Today I tried to get eBox to act as a PXE Boot Server. During my trials I found some problems:

  1. You cannot upload files into the directory served by the tftpd via the web interface.
  2. After uploading a file (pxelinux.0) via the upload form, the entry written into dhcpd.conf is wrong, as it does not point to the file and should not be prefixed by the filepath (/var/lib/pxeboot), as it should be stored into the root directory of the tftp server.
  3. Documentation on this topic is in a very bad condition.

Support for Other Parameters

  1. WINS
  2. NTP This needs to be able to advertise to the internal NETWORK that eBox is the NTP Server for this NETWORK.
  3. Others as requested

Add A Comment Field for Static DHCP Mappings

When adding static DHCP mappings for MAC addresses it would be nice to have a comment field as well, as the hostname of a computer might not be enough information to easily determine the user or type of that system.

Dynamic DNS Update

Every time a new DHCP client with its hostname asks for an IP and it is leased. Add a DNS entry dynamically with its hostname and the leased IP address. This post is very useful about this topic:  http://forum.ebox-platform.com/index.php?topic=1970.msg8857#msg8857

Add Option to Allow for Groups in DHCP

Just like in normal dhcpd.conf syntax it would be nice to have the option to apply settings to groups of computers as well. Something like one group would be for all my AP MAC addresses so that they get the parameters that they need at bootup, typically their IP, and NTP Server, other settings, another group for my non-AP Routers, another for the DMZ servers I may run and another couple for groups of PC's

DHCP Relay

Add an option for eBox to function as a DHCP Agent Relay.

Show static leases

Static addresses fixed to a MAC addreess doesn't appear on dhcpd.leases and then doesn't apper on the widget neither, try to fix that. The reason here:  https://lists.isc.org/pipermail/dhcp-users/2009-July/009504.html

Implement reverse dynamic DNS update

The direct mapping is now done but we need to allow reverse dynamic DNS update. To apply so, we need to be able to edit a dynamic zone without modifying the current journal file.