From owner-freebsd-net@FreeBSD.ORG Thu Oct 2 08:52:32 2003 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 9E84016A4BF for ; Thu, 2 Oct 2003 08:52:32 -0700 (PDT) Received: from smtp.uc3m.es (smtp01.uc3m.es [163.117.136.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id D531A43FF3 for ; Thu, 2 Oct 2003 08:52:29 -0700 (PDT) (envelope-from jrh@it.uc3m.es) Received: from smtp01.uc3m.es (localhost [127.0.0.1]) by smtp.uc3m.es (Postfix) with ESMTP id AC7E643295; Thu, 2 Oct 2003 17:52:28 +0200 (CEST) Received: from cimborrio (cimborrio.it.uc3m.es [163.117.139.95]) by smtp01.uc3m.es (Postfix) with ESMTP id 6DA8599EB7; Thu, 2 Oct 2003 17:52:28 +0200 (CEST) From: Juan Rodriguez Hervella Organization: UC3M To: SUZUKI Shinsuke Date: Thu, 2 Oct 2003 17:52:28 +0200 User-Agent: KMail/1.5 References: <200309291859.09355.jrh@it.uc3m.es> <200309300942.40834.jrh@it.uc3m.es> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310021752.30192.jrh@it.uc3m.es> cc: freebsd-net@freebsd.org Subject: Re: IPv6 autoconfiguration on a multihomed site 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: Thu, 02 Oct 2003 15:52:32 -0000 On Thursday 02 October 2003 17:04, SUZUKI Shinsuke wrote: > Hello Juan, > > >>>>> On Tue, 30 Sep 2003 09:42:39 +0200 > > > > Address of Router1: 2001:720:410:100b::3 > > Address of Router2: 2001:800:40:2471::4 > > Please confirm connectivity from Router2 to Router1 by the following > command. > Router2% ping6 -S 2001:720:410:100b::3 2001:800:40:2471::4 Though I don't know how to select the source address on the ping command on the CISCO, I tell you that *doesn't* work (without -S). I've got a default route towards the upstream provider that this router is connected to, so if I sends packets to 2001:800:40:2471::4 those will be routed outside my site because this router doesn't belong to the 2001:800:40:2471::/64 network (it is the router that announces 2001:720:410:100b::/64). > > If it does not work, it's no wonder that you cannot ping from PC to > Router1 when the PC's default router is router2. The simplest fix for > this problem is to assign 2001:720:410:40::/64 and > 2001:800:40:2471::4/64 to both routers: > Address of Router1: 2001:720:410:100b::3, 2001:800:40:2471::3 > Address of Router2: 2001:720:410:100b::4, 2001:800:40:2471::4 > If I do that, then everything is fixed. (I suppose that the first time I send sth. to router1 from the host, it will be route, for example, to router2, which will realize that the packet belongs to the other router, making something like a triangular routing, at least the first time, because afterwards a redirect message should be sent, right ?) But I think this isn't the way the problem should be fixed, I mean, why a router which only announces one prefix has to be configured with the prefix of another router ? In this scenario, the hosts should behave in the same way as with only one prefix. For example, if there's only one prefix, the host doesn't send packets to the default router, it sends them directly on the link...I don't understand why the same thing can not be applied when there are *two or more* links... where's the limitation ? or do you think that this is the way things should be running ? (Windows XP SP1 behave alike, though this isn't a relief :) > If you cannot still ping from PC to Router1 although it works, please > show me the routing tables of both routers. > > Thanks, My *thanks* for you all, you're doing a great job! (I'm applying to visit Japan some day *lol*, just kidding... I've seen on the telly that there are earthquakes !!) > ---- > SUZUKI, Shinsuke @ Hitachi / KAME Project -- JFRH