From owner-freebsd-questions@FreeBSD.ORG Sat Jul 26 09:19:01 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A931106564A for ; Sat, 26 Jul 2008 09:19:01 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id ABBD78FC1A for ; Sat, 26 Jul 2008 09:19:00 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 4294 invoked by uid 89); 26 Jul 2008 09:23:30 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 26 Jul 2008 09:23:30 -0000 Message-ID: <488AEC1A.1020909@ibctech.ca> Date: Sat, 26 Jul 2008 05:19:22 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: David Allen References: <9339104B-252B-49DC-9648-B59343E17E16@hughes.net> <488A0997.3090300@infracaninophile.co.uk> <2daa8b4e0807251605j525d7480n5a5531188f718660@mail.gmail.com> In-Reply-To: <2daa8b4e0807251605j525d7480n5a5531188f718660@mail.gmail.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris Pratt , FreeBSD Questions Subject: Re: IP alias/routing question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2008 09:19:01 -0000 David Allen wrote: > On Fri, Jul 25, 2008 at 10:12 AM, Matthew Seaman > wrote: >> Chris Pratt wrote: >> Carefully not answering the 'why do these packets come from the >> wrong address' question, > Deliberately addressing the question of 'why do these packets come > from the wrong address' question which Mr. Seaman avoided ...heh, heh heh. Good job with the wording guys. I smiled brightly when I went through this ;) Since I've replied but clipped out any further context, I'll add a bit... I agree with David in that this is purely a routing issue. What (IMHO) it comes down to is 'source address selection'. I've been more focused in this scope within IPv6, but it is apparently a problem as well with IPv4, in a different manner. Perhaps this will become more of an issue as more people get used to the understanding that having multiple addresses per interface is the design goal, not an alias workaround. At one point I was advised that there is the ability to use multiple route tables within -current. If the box is being designed for only one application, could you try the new implementation of routing as opposed to making the application fit? Steve