[Dnsmasq-discuss] how to configure lot of static routes

Albert ARIBAUD albert.aribaud at free.fr
Tue Jun 30 19:02:32 BST 2015


Le Tue, 30 Jun 2015 19:52:26 +0200, Albert ARIBAUD
<albert.aribaud at free.fr> a écrit :

> Le Tue, 30 Jun 2015 19:48:01 +0200, Albert ARIBAUD
> <albert.aribaud at free.fr> a écrit :
> 
> > > yes but RFC 3396 is about "Encoding Long Options in the Dynamic Host
> > > Configuration Protocol (DHCPv4)"
> > 
> > Yes, it is. The routes are among these long options.
> 
> Forget that, sorry, heat wave here is making me slip things.
> 
> What I meant to say is, DHCP routes are transmitted as variable-length
> options according to RFC 2132 section 2, not RFC 3396 -- do a Wireshark
> on some DHCP traffic and you'll see the option with the 8-byte-per-route
> entries in the DHCP offer.

More to the point, routes in dnsmasq are transmitted as classless
static routes (option 121) which are described in RFC 3442 in the
binary form that I mentioned.

(cc:ing Simon for the following altough it is purely for info; I don't
think dnsmasq needs fixing for this)

Note BTW that RFC 3442 says DHCP clients should ignore router option if
classless route option is present, and that servers should add the
default route to the classless static routes options even though the
default route is already given in the router option (which they should
also send regardless); however, dmsnasq does not add the default route
to the classless static routes, but that's fine because obviously Linux
and Windows clients do not ignore the router option when a classless
static routes option is present. :)

Amicalement,
-- 
Albert.



More information about the Dnsmasq-discuss mailing list