PXE Client configuration

Jason Frisvold frisvolj at lafayette.edu
Fri Feb 19 21:29:06 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/16/2010 09:18 AM, Denis Laventure wrote:
> That's not too complicated...
> I did it with a global class and subclasses so I can choose which VLAN get PXE using option-82. You can also add match condition like if substring(option vendor-class-identifier, 0, 9) = "PXEClient"; to the class if you like. 

Can you provide an example subnet declaration for this?  I'm not sure I
follow how this works..

I'm running into a few problems right now.  If I merely add the
PXEClients class and have no allow/deny statements in the pool
declaration, it appears to work fine.  If I put a "deny members of"
message, then it denies anything declaring itself as a PXEClient from
getting an address.  This appears to be ok as well, though it would be
nice if they could still get a DHCP address, just not the PXE server
information.

The big problem is that if I put an "allow members of" in the pool
declaration, it then denies everything except PXEClients.  I can remove
the "allow" and leave it open, which would work, but we're looking to
possibly have multiple PXE servers, so I need to be able to define the
pxe server information for each matched class.

I *think* the subclass declaration would help here, but I'm not 100%
sure how to make it work.

> Denis

Thanks,

- -- 
- ---------------------------
Jason Frisvold
Network Engineer
frisvolj at lafayette.edu
- ---------------------------
"What I cannot create, I do not understand"
   - Richard Feynman
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkt/AqIACgkQO80o6DJ8UvnogwCeMfjC1Lw4Sh9N5HiZcRWft1vm
PzYAn1AnAWtD6ikEFN32BBEbJyBCTJwV
=Jo5u
-----END PGP SIGNATURE-----



More information about the dhcp-users mailing list