From owner-freebsd-chat Tue Feb 2 15:34:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27017 for freebsd-chat-outgoing; Tue, 2 Feb 1999 15:34:53 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27012 for ; Tue, 2 Feb 1999 15:34:51 -0800 (PST) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.2/8.9.2) with SMTP id RAA31284; Tue, 2 Feb 1999 17:34:36 -0600 (CST) Date: Tue, 2 Feb 1999 17:34:36 -0600 (CST) From: "Jasper O'Malley" To: Terry Lambert cc: wghicks@bellsouth.net, jcwells@u.washington.edu, freebsd-chat@FreeBSD.ORG Subject: Re: DHCP Autoconfig (Was: Lets Endorse KDE) In-Reply-To: <199902022307.QAA06687@usr09.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 2 Feb 1999, Terry Lambert wrote: > Hm. My experience is that it comes up on the 10.x.x.x net. > > This would make sense, in that the statistical protection is 256 > times better than the 169.254.x.x net. Yes, but a lot of people are actually using the 10.X.X.X net for real networks, and most of them have them subnetted. IMHO, it's best to use LINKLOCAL (169.254/16) addresses, so as not to conflict with existing network topologies, and to quickly identify which machines can't (or aren't authorized to) talk to the DHCP server. Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message