From owner-freebsd-chat  Tue Feb  2 15:31:18 1999
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA26611
          for freebsd-chat-outgoing; Tue, 2 Feb 1999 15:31:18 -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 PAA26606
          for <freebsd-chat@FreeBSD.ORG>; Tue, 2 Feb 1999 15:31:17 -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 RAA31209;
	Tue, 2 Feb 1999 17:31:19 -0600 (CST)
Date: Tue, 2 Feb 1999 17:31:19 -0600 (CST)
From: "Jasper O'Malley" <jooji@webnology.com>
To: Terry Lambert <tlambert@primenet.com>
cc: wghicks@bellsouth.net, jcwells@u.washington.edu, freebsd-chat@FreeBSD.ORG
Subject: DHCP Autoconfig (Was: Lets Endorse KDE)
In-Reply-To: <199902022307.QAA06687@usr09.primenet.com>
Message-ID: <Pine.LNX.4.02.9902021724330.31014-100000@mercury.webnology.com>
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.

I've never seen that. There was a big discussion about it on the ISC DHCP
mailing list when Win98 retail was released.

> This would make sense, in that the statistical protection is 256
> times better than the 169.254.x.x net.

If I'm not mistaken, the autoconfiguration process checks the address it
picks before it sticks with it. From the IETF Internet Draft on the
subject:

    Once a DHCP Client has determined it must auto-configure an IP
    address, it chooses an address.  The algorithm for choosing an
    address is implementation dependant.  The address range to use MUST
    be "169.254/16", which is registered with the IANA as the LINKLOCAL
    net.

    If choosing an address in this range, the DHCP Client MUST not use
    the first 256 or the last 256, as these are reserved for future use.

    When an address is chosen, the DHCP Client MUST test to see if the
    address is already in use.  If the network address appears to be in
    use, the client MUST choose another address, and try again.  The
    client MUST keep choosing addresses until it either finds one, or it
    has tried more then the autoconfig-retry count.  The autoconfig-
    retry count is implementation specific, and should be based on the
    algorithm used for choosing an IP address.  This retry count is
    present to make sure that DHCP Clients auto-configuring on busy
    auto-configured network segments do not loop infinitely looking for
    an IP address.

> Are you perhaps running an early/MSDN release of Windows 98?

Nope. Standard OEM release.

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