> I couldn't easily in this situation, however, rely on a DHCP server not > on my VSWITCH, no. I'm perfectly aware of that. My DHCP server is a tiny > SLES9 user under VM, on the same layer 3 VSWITCH as all my clients, so > it's not an issue.
Yeah, understood. I need to deal with protocols that care about the MAC address a lot more commonly (like SNA), so the requirement remains. It also forestalls some of the "ip helper" offload capability in the outboard routers for controlling which server responds, which is sometimes very useful. > Sending a DHCPDISCOVER with a Client ID for > the server to key on is not a function of layer 2 or layer 3; think > about PPPoA and how all those cablemodem or DSL DHCP clients out there > work. Yeah. In most cases those cable boxes do have unique MACs, though, or are in special situations where there are tools that understand their quirks. Your average enterprise network doesn't have the tooling to track down something like that, and it makes it harder to engineer and harder for the networking guys to understand, which is worth avoiding. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
