From owner-freebsd-net@FreeBSD.ORG Sat Dec 11 09:41:37 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9175716A4CE for ; Sat, 11 Dec 2004 09:41:37 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C4DA43D46 for ; Sat, 11 Dec 2004 09:41:37 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-160-207-47.ny325.east.verizon.net [68.160.207.47]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iBB9fYfw001163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Dec 2004 04:41:36 -0500 (EST) Message-ID: <41BAC0BD.7000706@mac.com> Date: Sat, 11 Dec 2004 04:41:17 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrea Campi References: <20041211090235.GD11190@webcom.it> In-Reply-To: <20041211090235.GD11190@webcom.it> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: net@freebsd.org Subject: Re: Working on howl port X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 09:41:37 -0000 Andrea Campi wrote: [ ... ] > The way I'm addressing this is to have autoipd use SIOCAIFADDR > and manage exactly one address in the 169.254/16 block. This > means you will ALWAYS have an IP address in that range; if you > also run dhclient, you might have an additional IP and a default > route. > > Thoughts? See http://files.zeroconf.org/draft-ietf-zeroconf-ipv4-linklocal.txt: 1.9. When to configure an IPv4 Link-Local address Having addresses of multiple different scopes assigned to an interface, with no adequate way to determine in what circumstances each address should be used, leads to complexity for applications and confusion for users. A host with an address on a link can communicate with all other devices on that link, whether those devices use Link- Local addresses, or routable addresses. For these reasons, a host SHOULD NOT have both an operable routable address and an IPv4 Link-Local address configured on the same interface. ...but there is more there to read. It's fine to let an interface have a 169.254/16 IP and a "real" IP (assigned by DHCP, the user, etc) for a little while during transitions, but not forever. -- -Chuck