From owner-freebsd-net@FreeBSD.ORG Mon Dec 14 09:11:50 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55B86106566C for ; Mon, 14 Dec 2009 09:11:50 +0000 (UTC) (envelope-from aman.jassal@esigetel.fr) Received: from mail.esigetel.fr (venus.esigetel.fr [192.134.106.8]) by mx1.freebsd.org (Postfix) with ESMTP id DB71B8FC20 for ; Mon, 14 Dec 2009 09:11:49 +0000 (UTC) Received: by mail.esigetel.fr (Postfix, from userid 65534) id 762A9102E6; Mon, 14 Dec 2009 10:11:48 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on venus.esigetel.avon X-Spam-Level: X-Spam-Status: No, score=-3.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=unavailable version=3.1.8 Received: from localhost (localhost [127.0.0.1]) by mail.esigetel.fr (Postfix) with ESMTP id D380D102E5; Mon, 14 Dec 2009 10:11:47 +0100 (CET) X-Virus-Scanned: amavisd-new at esigetel.fr Received: from mail.esigetel.fr ([127.0.0.1]) by localhost (venus.esigetel.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v3hVYrsTFbbv; Mon, 14 Dec 2009 10:11:42 +0100 (CET) Received: from webmail.esigetel.fr (neo.ecampus.avon [192.168.106.14]) by mail.esigetel.fr (Postfix) with ESMTP id 28169102DB; Mon, 14 Dec 2009 10:11:42 +0100 (CET) Received: from 83.206.131.26 (proxying for unknown) by webmail.esigetel.fr with HTTP; Mon, 14 Dec 2009 10:11:42 +0100 (CET) Message-ID: <9223.83.206.131.26.1260781902.squirrel@webmail.esigetel.fr> In-Reply-To: References: Date: Mon, 14 Dec 2009 10:11:42 +0100 (CET) From: "JASSAL Aman" To: "Dennis Glatting" User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org Subject: Re: Understanding multiple IPv6 interfaces under 8.0 (fwd) 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: Mon, 14 Dec 2009 09:11:50 -0000 Hello Mr.Glatting, Not that I'm an IPv6 genius, but at first sight your problem seems to be a route-related. I've put comments in-line. Le Dim 13 décembre 2009 22:58, Dennis Glatting a écrit : > > > Elmer# netstat -rn > Routing tables > > > Internet6: > Destination Gateway Flags > Netif Expire > ::/96 ::1 UGRS > lo0 => default fd7c:3f2b:e791:1::1 > UGS bce0 > ::1 ::1 UH > lo0 ::ffff:0.0.0.0/96 ::1 UGRS > lo0 fd7c:3f2b:e791:1::/64 link#1 U > bce0 fd7c:3f2b:e791:1::ac13:a0a link#1 UHS > lo0 fd7c:3f2b:e791:1:0:1:ac13:a0a link#2 UHS > lo0 fe80::/10 ::1 UGRS > lo0 fe80::%bce0/64 link#1 U > bce0 fe80::213:72ff:fe60:ac52%bce0 link#1 UHS > lo0 fe80::%bce1/64 link#2 U > bce1 fe80::213:72ff:fe60:ac50%bce1 link#2 UHS > lo0 fe80::%lo0/64 link#3 U > lo0 fe80::1%lo0 link#3 UHS > lo0 ff01:1::/32 fe80::213:72ff:fe60:ac52%bce0 U > bce0 ff01:2::/32 fd7c:3f2b:e791:1:0:1:ac13:a0a U > bce1 ff01:3::/32 ::1 U > lo0 ff02::/16 ::1 UGRS > lo0 ff02::%bce0/32 fe80::213:72ff:fe60:ac52%bce0 U > bce0 ff02::%bce1/32 fd7c:3f2b:e791:1:0:1:ac13:a0a U > bce1 ff02::%lo0/32 ::1 U > lo0 > Hmm, the entry for fd7c:3f2b:e791:1:0:1:ac13:a0a looks suspect. I was expecting bce1 rather than lo0, I suppose you were as well :) If I'm not mistaken, the packets emanating from bce1 go to the loopback interface, thus not really going out. You can try specifying the route manually with "route add *your parameters*" or even set it in /etc/rc.conf so that it's loaded at boot-time. There's no reason why among 2 physical interfaces sharing the same fabric, one can ship packets out and the other can't. > > Elmer's rc.config: > > > ipv6_enable="YES" ipv6_network_interfaces="bce0 bce1" > ipv6_ifconfig_bce0="FD7C:3F2B:E791:0001::0:172.19.10.10 prefixlen 64" > ipv6_ifconfig_bce1="FD7C:3F2B:E791:0001::1:172.19.10.10 prefixlen 64 mtu > 8192" > ipv6_defaultrouter="FD7C:3F2B:E791:0001::1" > Erm... You're using IPv4 addresses encapsulated in IPv6 ? I've never used this myself so I can't really comment, and I can't say if there aren't any sort of "interferences" with what you're trying to do. > > > The router (cisco): > > > interface GigabitEthernet0/0 ipv6 address FD7C:3F2B:E791:1::1/64 ipv6 > enable ipv6 nd prefix FD7C:3F2B:E791:1::/64 (etc) > Just a side-note, I'm not sure if it will be really useful to you, but you could give it a try if you want to. Have you tried using your Cisco router as a Router Advertisement Daemon ? That way, addresses would be built automatically and you could see how both interfaces react to such advertisements. I hope this helps. ------------ Aman Jassal Wisdom comes from experience. Experience comes from a lack of wisdom.