Pool/Scope or subnet with PXE boot options?

Denis Laventure Denis_Laventure at uqac.ca
Fri Oct 9 15:18:19 UTC 2009

Hi Jason,

I did it with a global class but I can choose which VLAN get PXE using option-82.

class "PXE-GHOST" {
         match binary-to-ascii (10, 16, "", substring( option agent.circuit-id, 2, 2));
    next-server ghost.domain.com;
    filename "\\Tftpboot\\Menu.pxe";

subclass "PXE-GHOST" "298" {
    log (info, "Matched PXE-GHOST - VLAN 298");

subclass "PXE-GHOST" "428" {
    log (info, "Matched PXE-GHOST - VLAN 428");


-----Message d'origine-----
De : dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-bounces at lists.isc.org] De la part de Jason Gerfen
Envoyé : 8 octobre 2009 15:36
À : dhcp-users at lists.isc.org
Objet : Pool/Scope or subnet with PXE boot options?

I am not sure if this has been addressed before or not as I could not 
find anything in the archives or references (minus utilizing classes) to 
allow an entire pool/scope or subnet to a pxe group.

Would it be an options within the pool options? Something like:

pool {
    option domain-name-servers,;
    allow boot-clients;
    #bootp specs
     filename "/tftproot/pxelinux.0";
     next-server server.name;

or perhaps something like this within the subnet declaration?

subnet netmask {
    option domain-name-servers,;
    option routers;
    option ip-forwarding off;
    #bootp specs
     filename "/tftproot/pxelinux.0";
     next-server server.name;

I really want to avoid the use of classes here as I would simply like to 
allow our dynamic IP ranges the same group bootp access as our static IP 

Any help is appreciated.


dhcp-users mailing list
dhcp-users at lists.isc.org

More information about the dhcp-users mailing list