The current tree already has this functionality, though the code which
implements it is somewhat different. It certainly provides a
DNSMASQ_REQUESTED_OPTIONS variable containing a comma-separated list of
decimal numbers.

Best to look at the current code, and submit a patch if it doesn't
behave as you expect.



On 09/04/17 19:22, Denton Gentry wrote:
> is a database of OS signatures based
> on the DHCP options populated and the order in which they appear. So
> for example, an Android device will typically send
> '1,33,3,6,15,26,28,51,58,59' while iOS sends '1,3,6,15,119,252'.
> We modified dnsmasq to export DHCP OS signatures to a
> DNSMASQ_REQUESTED_OPTIONS environment variable when it forks the
> dhcp-script. The environment variable is formatted to match
> fingerbank. The dhcp-script we run writes the signature to a separate
> file, though of course this behavior is outside of dnsmasq itself.
> Is OS fingerprinting support something which could be more widely useful?
> Should I rebase the patch to the current tree and start discussion?
> _______________________________________________
> Dnsmasq-discuss mailing list

Attachment: signature.asc
Description: OpenPGP digital signature

Dnsmasq-discuss mailing list

Reply via email to