From owner-freebsd-chat Thu Nov 23 16:17:23 2000 Delivered-To: freebsd-chat@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 7BBFB37B4C5 for ; Thu, 23 Nov 2000 16:17:20 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id RAA29741; Thu, 23 Nov 2000 17:13:36 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpdAAAwAaO.5; Thu Nov 23 17:13:29 2000 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id RAA02448; Thu, 23 Nov 2000 17:17:09 -0700 (MST) From: Terry Lambert Message-Id: <200011240017.RAA02448@usr06.primenet.com> Subject: Re: DHCP To: res03db2@gte.net (Robert Clark) Date: Fri, 24 Nov 2000 00:17:09 +0000 (GMT) Cc: dchulhan@uwi.tt, tlambert@primenet.com, chat@FreeBSD.ORG In-Reply-To: <200011230235.SAA04238@gte.net> from "Robert Clark" at Nov 22, 2000 06:35:02 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Yeah Terry, > But doesn't all that do exactly what Dale asked not to > do? ie: Split the broadcast domain. No. He's asking to split the broadcast domain. He just wants it split based on what floor the machine is on, without really having to split it. With respect, a DHCP server can't know which floor a client is on, so that it can decide whether or not to respond to a packet based on where it came from. It's like buying 4 walkie-talkies from Radio Shack, all of which have crystals for CB channel 11, and then asking that two people using two of them on the second floor not interfere with the conversation between another two people using two of them on the first floor. Or it's like buying a 900MHz cordless phone, and expecting it to not work when you are upstairs and the base is downstairs. DHCP was never built to work this way. Technically, he could set up an explicit list of MAC addresses for each server, by going around to every machine and writing down its MAC address, and then explicitly configuring the DHCP via bootp options to only ever answer for a certain list of MAC addresses. If you are doing that, you might as well open the "network properties" instead of the "winipcfg" dialog, and explicitly configure them; you won't ever be able to move machines from one floor to the other, or buy new hardware and add it, without maintaining the MAC list on one or both DHCP servers. In other words, you statically configure the clients with the server information, or you statically configure the server with the client information -- or you split the broadcast domain. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message