From owner-freebsd-net@FreeBSD.ORG Mon Dec 13 17:38:01 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 9B29616A4CE for ; Mon, 13 Dec 2004 17:38:01 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81BB543D45 for ; Mon, 13 Dec 2004 17:38:01 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id iBDHc01O000889; Mon, 13 Dec 2004 09:38:01 -0800 (PST) Received: from [10.1.1.245] (nfw1.codefab.com [199.103.21.225]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id iBDHbxQS023290; Mon, 13 Dec 2004 09:38:00 -0800 (PST) In-Reply-To: <20041213090609.GA30379@webcom.it> References: <20041211090235.GD11190@webcom.it> <41BAC0BD.7000706@mac.com> <20041211102825.GB12803@webcom.it> <41BB40B7.5000907@mac.com> <1B251E0B-4C95-11D9-A057-000393CFACB0@apple.com> <20041213090609.GA30379@webcom.it> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 13 Dec 2004 12:37:58 -0500 To: Andrea Campi X-Mailer: Apple Mail (2.619) cc: net@freebsd.org cc: Peter Heerboth 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: Mon, 13 Dec 2004 17:38:01 -0000 On Dec 13, 2004, at 4:06 AM, Andrea Campi wrote: > I'd like to live complications such as this for a later stage. I'd say > if you have a multihomed machine you better know how to configure it; > the primary target for my work are laptops and other clients. That is > not to say I don't care; rather, I need to limit how much I chew at a > time. For now I only work on one interface. Indeed, handling link-local addressing by only looking at one interface at a time is something the zeroconf spec seems to encourage if the implementation does not yet handle IP collision avoidance across multiple interfaces. -- -Chuck