From owner-freebsd-net@FreeBSD.ORG Mon Sep 29 09:59:11 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 133B616A4B3 for ; Mon, 29 Sep 2003 09:59:11 -0700 (PDT) Received: from smtp.uc3m.es (smtp01.uc3m.es [163.117.136.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2203143FB1 for ; Mon, 29 Sep 2003 09:59:09 -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 DF4F943131; Mon, 29 Sep 2003 18:59:07 +0200 (CEST) Received: from cimborrio.it.uc3m.es (cimborrio.it.uc3m.es [163.117.139.95]) by smtp01.uc3m.es (Postfix) with ESMTP id 7F6DF99E66; Mon, 29 Sep 2003 18:59:07 +0200 (CEST) From: Juan Rodriguez Hervella Organization: UC3M To: freebsd-net@freebsd.org Date: Mon, 29 Sep 2003 18:59:08 +0200 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309291859.09355.jrh@it.uc3m.es> cc: snap-users@kame.net Subject: 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: Mon, 29 Sep 2003 16:59:11 -0000 Hello all: I'm using FreeBSD-4.8-RELEASE. (I've tested the same thing using a KAME snap, so I CCs to them :) I've got two routers sending RAs on the same link, so the host is configured with two IPv6 prefix on the same NIC. Watching the routing table I only see one default IPv6 route. When I try to ping the global IPv6 address of one router, if I'm lucky and the router is the same router which I've got installed on the default route, it will answer. The problem is that the host doesn't seem to realize that it is on two links at the same time, so it always sends packets to the default router.... For example, if there's only one RA, the autoconfiguration process ends up with a link-route like this: 2001:720:410:1001::/64 link#2 UC fxp0 On the other hand, when there are 2 RAs on the same link, this route doesn't exist ! Is this behaviour right ? I've observed the same thing on Linux... -- JFRH