On Mon, Jul 12, 2010 at 9:33 AM, Jonathan Dieter <jdie...@lesbg.com> wrote:
> In current 2.0BETA3, it seems that there's no way to write one's own
> configuration settings into dhcpd.conf.  For example, if I want to
> chain-load gPXE, there's nowhere to put the following:
>
> if exists user-class and option user-class = "gPXE" {
>        filename "http://www.lesaz.loc/netboot/pxelinux.0";;
> } else {
>        filename "gpxe.pxe";
> }
>
> I've added a "Custom DHCP configuration" that will be inserted at the
> end of the subnet declaration.  To be honest, this feels a bit hackish
> (why at that location), but I'm not sure of any better place to put it.
>
> I did modify xmlparse.inc to make any name that ends as "_cdata" a CDATA
> type, as that was the most logical way that I could think of to maintain
> newlines.  If there's a better way, please correct it (or let me know
> and I'll correct it).
>

This one should use base64 rather than cdata, to be consistent with
all other similar fields.

---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org

Reply via email to