Which clients?
In general, PacketFence only runs DHCP for registration and isolation VLANs.
Registered clients on production VLANs may use any DHCP server, configured
however you like.
If you really need to pass special options to clients in
registration/isolation, I believe it can be done, as long as you can
distinguish them by something in the client request, such as vendor-class, a
substring of host-name, circuit-id. Unlike some other systems, PacketFence does
not regularly update the DHCP configuration, so you cannot easily make
decisions based on the client MAC address.
Here's how I currently give tftpboot options to certain clients on our network.
In theory, you could put something similar before %%networks%% line in
~pf/conf/dhcpd.conf.
class "boot-pxe-class" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
next-server bootserver;
filename "boot.0";
}
class "boot-usb-class" {
match if substring (option host-name, 0, 7) = "minint-";
next-server bootserver;
filename "boot.0";
}
--
Rich Graves http://claimid.com/rcgraves
Carleton.edu Sr UNIX and Security Admin
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
