From owner-freebsd-net@FreeBSD.ORG Thu Aug 24 05:40:45 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 1941E16A524; Thu, 24 Aug 2006 05:40:45 +0000 (UTC) (envelope-from fli+freebsd-net@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C0C343D46; Thu, 24 Aug 2006 05:40:43 +0000 (GMT) (envelope-from fli+freebsd-net@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id 899061A78D; Thu, 24 Aug 2006 07:40:41 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23772-04; Thu, 24 Aug 2006 07:40:39 +0200 (CEST) Received: from [192.168.1.100] (217-208-33-252-o926.tbon.telia.com [217.208.33.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id B41121A751; Thu, 24 Aug 2006 07:40:38 +0200 (CEST) Message-ID: <44ED3BD1.3030206@shapeshifter.se> Date: Thu, 24 Aug 2006 07:40:33 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 1.5.0.4 (X11/20060727) MIME-Version: 1.0 To: Pat Lashley References: <44EA1926.2000501@shapeshifter.se> <9C04919EE684029A410DE208@garrett.local> <44EAC40E.9000904@shapeshifter.se> <3E654CC0217F90E20FCD806E@garrett.local> <44EC90B7.6090908@shapeshifter.se> <44ECB0F2.9040300@FreeBSD.org> <20060823212110.GD27961@lor.one-eyed-alien.net> <20060823221835.GA28978@lor.one-eyed-alien.net> <23D2619F6BACE4E728178EE5@garrett.local> In-Reply-To: <23D2619F6BACE4E728178EE5@garrett.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: freebsd-net@freebsd.org, Doug Barton Subject: Re: Zeroconfig and Multicast DNS X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Aug 2006 05:40:45 -0000 Pat Lashley wrote: > >> The one thing >> I'd be worried about is how the socket code handles connect() requests. >> My hope would be that it would pick the address that goes with the >> router to be used and thus the LLA would never be the source of a packet >> going to a non-LLA address in normal circumstances. > > The RFC is pretty explicit about the need to prefer non-LLA addresses. > We may need to put some explicit checks in the connect() code to enforce > that preference in the aliased case. The trick, of course, is to > recognize those cases where the LLA address must be used anyway. > > Hmmm. Interesting routing problem. Basically, we need to prefer a route > that doesn't use the LLA (unless the destination is in an LLA); but > still handle the edge cases like having the default route be through an > LLA-only-connected router. (Which MUST do NAT...) > > Um..wouldn't the routing code handle this? If you set a lla address and some other address on a interface like 192.168.0.2 or something and then a default route of 192.168.0.1, I would assume that an application without specific knowledge that tries to contact an external address would get 192.168.0.2 as the source address and that the packet is sent to 192.168.0.1. If you're in the situation that you need lla (no dhcp server available), you wouldn't know the default route right? And if you need to configure the default route manually it isn't really zeroconfig any longer. Fredrik Lindberg