Hi,

We're running the very latest snapshot of 2.1beta0 on two boxes with
failover : it's GREAT !!!

However, we like to report some limits of the DHCP server's
configuration capabilities, in case these enhancements could be
implemented in a future release.

 * First problem is with the "range" settings : if we want to create a
   set of static mappings, and check the "Deny unknown clients"
   checkbox, then the WebUI doesn't accept that we don't fill the start
   and end range boxes. So we have to fill them in and we use the same
   IP address for start and end, but this is not very clean. Are we
   doing something wrong, or as we think, should the WebUI accept such
   settings ?

 * Second problem is about network booting : it's not possible to
   specify a different boot server or none at all for a set of machines
   behind the same interface. What would be great would be a way to
   override the "next-server" setting on a host-by-host basis, just like
   it's possible to do so when modifying ISC's dhcpd.conf manually.  So
   a "next-server" input box should be added in the "edit static
   mapping" box when network booting is enabled on a particular
   interface : this page already allows one to specify a different root
   path and filename than the ones defined at the interface level, so
   why not add a different next server override option as well ?

Would other people like such enhancements ?

Thanks in advance.

--
Jérôme Alet - <[email protected]> - Direction du Système d'Information
      Université de la Nouvelle-Calédonie - BPR4 - 98851 NOUMEA CEDEX
   Tél : +687 290081                                  Fax : +687 254829
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to