<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Feb 14, 2014, at 7:16 AM, José Queiroz <<a href="mailto:zekkerj@gmail.com">zekkerj@gmail.com</a>> wrote:<br><div><blockquote type="cite">2014-01-31 11:09 GMT-02:00 Ole Holm Nielsen <span dir="ltr"><<a href="mailto:Ole.H.Nielsen@fysik.dtu.dk" target="_blank">Ole.H.Nielsen@fysik.dtu.dk</a>></span>:<br></blockquote><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We run the ISC DCHP version 4.1.1 server that comes with Red Hat RHEL 6.5 Linux. We grant DHCP leases only to known hosts, and we have files with declarations of host names and their MAC addresses to achieve this.<br>
<br>
We have a new challenge because we want to restrict all Windows XP PCs (and we know who they are :-) to a specific VLAN subnet, where we want to impose strict firewall rules. If a user connects his XP PC to any other VLAN subnet, the DHCP server must ignore this client.<br>
</blockquote><div> <br></div><div>Just in a rhetoric question... if one of these machines get booted in a different OS, like Linux or even Windows 7, should DHCPD treat it differently?<br></div></div></div></div></blockquote><br></div><div>Possibly. If the first OS uses a CID, and then the different OS provides a different CID or no CID at all, then yes, the client will be treated as a different client than before.</div><div><br></div><div>Chris Buxton</div><br></body></html>