Two subnets, one with PXE clients

[osmany at oc.quimefa.cu]

On Wed, 3 Mar 2010 16:59:25 +0000, Simon Hobson <dhcp1 at thehobsons.co.uk>
wrote:
> Osmany wrote:
> 
>>Now the PXE Client boots perfectly with the IP it's meant
>>to have, but now I have another problem. Once the PXE client loads, it
>>begins configuring itself to load the OS and obviously does a
>>DHCPDISCOVER once again because it is no longer a PXE Client but I find
>>that the dhcp server assigns an IP from the subnet 10.25.4.0/24 which I
>>don't want it to have those IPs because the LTSP server does not have
>>any of those IP's.
> 
> Well of course, that's exactly how you've configured it !
> 
> Once the client boots it's OS, it's not a PXE client, doesn't match 
> the PXE class, and so is only allowed an IP from the 10.25.4.0/24 
> subnet. If you want certain clients to continue getting a 
> 192.168.0.0/24 address after boot, then you'll need to add a class 
> that matches them, and add the appropriate allow/deny statements.
> 
> Eg :
> 
> class "LTSPClients" {
>    match if ...
> }
> 
> shared-network ... {
>    subnet 10.25.4.0 netmask 255.255.255.0 {
>      ...
>      pool{
>        ...
>        allow unknown-clients;
>        deny members of "PXEClients";
>        deny members of "LTSPClients";
>      }
>    }
> 
>    subnet 192.168.0.0 netmask 255.255.255.0 {
>      pool{
>        ...
>        allow members of "PXEClients";
>        allow members of "LTSPClients";
>      }
>    }
> }
> 
Yes I actually thought this is what is happening and I'm going to try and
create a second class to include the
dhcp-clients that make the DHCPDISCOVER. Thanks for the help. I will post
my results later.