[Dnsmasq-discuss] dhcp-option=121 doesn't seem to work
g.liakhovetski at gmx.de
Thu Dec 20 10:47:04 GMT 2007
On Wed, 19 Dec 2007, Simon Kelley wrote:
> Guennadi Liakhovetski wrote:
> > I also
> > added it to dnsmasq.conf like
> > dhcp-option=<client-ip>,33,<target-network>,<gateway-ip>
> Wrong syntax: you can't put the client-ip there. If you want to send
> options to certain hosts only, you need to use tags. Sorry, should have
> spotted that in your first message.
Yep, thanks. But, as I said, it wasn't the problem with the option 121 - I
also tried without the restriction, just starting with 121.
Now, I did know 33 was deprecated, but as 121 doesn't seem to be supported
by the dhclient, and I didn't want to use extra scripts, I gave 33 a go.
Fixed the syntax, specifying like
and I do see this time in wireshark, that the option is sent from the
dnsmasq, but the route is not configured. Ok, this is now not dnsmasq's
problem any more, but maybe you would know, have they disabled "33" in
dhclient or why it doesn't work?
> > Do you know which dhcp client should support 121? I'm using dhclient ATM,
> > maybe it was dhcpcd that you meant? Or is it only supported in testing /
> > experimental Debian branches?
> dhcpcd doesn't support it, I think. dhclient can be made to, with
> sufficiently clever scripting. See:
> for the last time this came up.
Wait, but you first have to request this option? I haven't managed even
that - haven't found its name.
More information about the Dnsmasq-discuss