classless routes

[Enrique de Guindos Carretero]

May be you're right, Glenn. On the documentation I read it understands rfc
2131 but  nothing about rfc 3442, the one defining code 121...
Thx,

Enrique



2007/2/21, Glenn Satchell <Glenn.Satchell at uniq.com.au>:
>
> >Date: Wed, 21 Feb 2007 10:25:54 +0100
> >From: "Enrique de Guindos Carretero" <eguindos at gmail.com>
> >To: dhcp-users at isc.org
>
> Does the dhcp-client configuration script know how to interpret option
> 121 and do the right thing? It may be that the client does not understand
> what it has to do.
>
> regards,
> -glenn
>
> >Hello Eric.
> >Thanks for your quick answer.
> >
> >Unfortunately, my dhcp still does not work as I want with Linux clients.
> >Now, my config file is the next:
> >
>
> >-------------------------------------------------------------------------------
> ----------------
> >
> >ddns-update-style none;
> >authoritative;
> >
> >default-lease-time              3600;           # 1 hora
> >max-lease-time                  14400;
> >
> >option ca-static-routes code 121  = array of unsigned integer 8;
> >
> ><several options for domain, dns server, etc...>
> >
> >option  broadcast-address       192.168.0.255;
> >option  routers                        192.168.0.1;
> >option  subnet-mask               255.255.255.0;
> >
> >subnet  192.168.0.0  netmask 255.255.255.0
> >{
> >        pool
> >        {
> >                range   192.168.0.15    192.168.0.50;
> >                option ca-static-routes 24, 192,168,0,0, 192,168,0,1;
> >        }
> >}
> >...
>
> >-------------------------------------------------------------------------------
> --------------------
> >
> >But as soon as a Linux dhcp client boots, it has the normal route table,
> >same as if I do not put the code 121 option:
> >
> >linux_client#> route
> >
> >Destination   Gateway      Genmask        Flags   Metric   Ref   Use
> Iface
> >192.168.0.0   *                 255.255.255.0 U         0          0
> >0       eth0
> >default          192.168.0.1  0.0.0.0           UG       0          0
> >0       eth0
> >
> >And I think I should expect something like
> >
> >Destination   Gateway   ...
> >192.168.0.0  192.168.0.1
> >
> >The above is what I observe on Windows Clients if I add an option for
> code
> >249 instead (or together with) of code 121.
> >
> >Do you see anything wrong on my configuration?
> >
> >Just to let you know, I'm using OpenSuSE 10.2
> >
> >Thanks a lot in advance,
> >
> >Enrique
> >
> >2007/2/20, Eric Helm <helmwork at ruraltel.net>:
> >>
> >>
> >> Enrique de Guindos Carretero wrote:
> >> > Hello.
> >> > I'm new to dhcp and I'm having a problem.
> >> >
> >> > I have read RFC 3442 concerning classless routes sent to the dhcp
> >> clients.
> >> >
> >> > As I saw, Windows clients are using code 249 while the standard one
> is
> >> 121.
> >> > On Windows clients I have no problems. But I have troubles on Linux
> >> ones.
> >> >
> >> > On my dhcpd.conf I have:
> >> >
> >> > option  ca-static-routes code 121 = string;
> >> > option  ca-static-routes 18:C0:A8:00:C0:A8:00:01;
> >> >
> >> > In order of having  192.168.0.0/24 routed through 192.168.0.1 router.
> >> > Changing the code with 249 works for windows clients. But with code
> 121,
> >> my
> >> > Linux clients are receiving nothing and they have not the static
> route
> >> > configured.
> >> >
> >> > Is it there any solution?
> >> >
> >>
> >> For my linux hosts, this config works to supply option 121:
> >> option classless-routes code 121 = array of unsigned integer 8;
> >>
> >> subnet 192.168.0.0 netmask 255.255.255.0
> >> {
> >>        pool
> >>        {
> >>                range 192.168.0.2 192.168.0.254
> >>                option classless-routes 24, 192,168,0,0,  192,168,0,1;
> >>        }
> >> }
> >>
> >> /Eric
> >>
> >>
> >
> >
> >
>
>