From owner-freebsd-chat Wed Nov 22 14:47:19 2000 Delivered-To: freebsd-chat@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id DA31137B4CF for ; Wed, 22 Nov 2000 14:47:16 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id PAA19590; Wed, 22 Nov 2000 15:45:13 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpdAAAMWaOmM; Wed Nov 22 15:45:09 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA06411; Wed, 22 Nov 2000 15:47:10 -0700 (MST) From: Terry Lambert Message-Id: <200011222247.PAA06411@usr05.primenet.com> Subject: Re: DHCP To: dchulhan@uwi.tt (Dale Chulhan - Work) Date: Wed, 22 Nov 2000 22:47:10 +0000 (GMT) Cc: chat@FreeBSD.ORG In-Reply-To: <001601c0549f$0e6b9a40$280101c8@distance10> from "Dale Chulhan - Work" at Nov 22, 2000 12:12:46 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 > P: I recently discovered that I now have two dhcp servers in the same > broadcast domain and I was wondering how I could ensure ( short of splitting > the BD into two ) that the machines on Floor 1 & 2 get their addresses from > server1 and from 3 & 4 get theirs from server2 Put a router between them. You will still get the addresses assigned by the other, if you are running a DHCP forwarder, in the case that the first one goes down. If you don't want this feature, don't run the broadcast forwarder (which will only forward on second and subsequent requests, as long as your request packets aren't malformed). DHCP was never meant to be constrained by "workgroup" type semantics (e.g. where you have a fictional boundary instead of an actual network broadcast boundary, like a router). The problem is communicating the current lease-list between the failed machine and the machine doing the takeover. Doing simple broadcast snoops is not sufficient for this task. Ideally, you would install IPv6, and do IPv6 stateless autoconfiguration, and turn off your DHCP servers. If you are running a network behind a NAT, and can live with a clas C (in "link.local"), then you could use IPv4 stateless autoconfiguration (supported by Windows 98 and above) to just grab addresses for your workstations. Unfortunately, unlike all recent Macintosh machines, Windows does not ship with SLPv2 (Service Location Protocol) support, so locating your default DNS server and default route will be problematic, without DHCP, or static configuration of some of your workstation settings. If your workstations are FreeBSD boxes, turn on RIP (internally only), and you'll have no problem. 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