On Sat, Aug 11, 2018 at 01:09:53AM +0000, Daniel Weller wrote:
> From: Geert Stappers Sent: Friday, August 10, 2018 7:20:50 AM
> > On Fri, Aug 10, 2018 at 09:11:48AM +0000, Daniel Weller wrote:
> > > I am trying to pass a DHCP header value that is read from the client
> > > DHCP request- to the file being called by dhcp-script=<file>. The
> > > easiest way to do that I think is to set an environment variable that
> > > the dhcp-script=<file> has access to while executing.
> > What is the original problem?
> > So let us know which DNSMASQ_... you miss.
> That is the original problem. Just trying to pass a custom DHCP
> header option to the dhcp-scrip=<file>. What do you mean by "So let
> us know which DNSMASQ_... you miss" ? I understand there is a lot of
> DNSMASQ_... options on the man page under dhcp-script. None let you
> grab all of the DHCP headers passed from the client to the server.
mmmm, I was hoping for an answer like
} I do mis DNSMASQ_FOO. FOO is a custom DHCP option, being option number ....
} Having DNSMASQ_FOO in dhcp-script would solve the problem of ...
Without knowing the original problem is not possible to provide
an alternative solution.
Without knowng the DHCP option number is not possible to advice
which existing DHCP option to use as starting point for the currently
missing source code for putting FOO into environment for dhcp-script.
Leven en laten leven
Dnsmasq-discuss mailing list