[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(usagi-users 00704) Re: IPv6 multi-netted source address problem

To: Spencer Brooks <sbrooks@xxxxxxxxxxxxxxxx>
Subject: (usagi-users 00704) Re: IPv6 multi-netted source address problem
From: Yuji Sekiya <sekiya@xxxxxxxxxxxxxx>
Date: Thu, 23 Aug 2001 03:30:28 +0900
Cc: usagi-users@xxxxxxxxxxxxxx
In-reply-to: <B79D71D3.2B9D%sbrooks@sonypictures.com>
List-subscribe: <mailto:usagi-users-ctl@linux-ipv6.org?body=subscribe>
Organization: Keio University
References: <B79D71D3.2B9D%sbrooks@sonypictures.com>
Reply-to: usagi-users@xxxxxxxxxxxxxx
User-agent: Wanderlust/2.4.0 (Rio) REMI/1.14.2 (Hokuhoku-ﾒshima) Chao/1.14.1 (Rokujizò) APEL/10.2 MULE XEmacs/21.1 (patch 9) (Canyonlands) (i686-pc-linux)

At Mon, 13 Aug 2001 12:00:20 -0700,
Spencer Brooks <sbrooks@xxxxxxxxxxxxxxxx> wrote:

Hello Spencer,

> If an interface is multi-netted (has 2 or more IPv6 addresses) the kernel
> will lock the source address for all out bound packets to the most recently
> added IPv6 address.  This can lead to routing problems.  See below for the
> example.

Have you tried USAGI kernel ?
If you not, please try.

-- Yuji Sekiya

References:
- (usagi-users 00672) IPv6 multi-netted source address problem
  - From: Spencer Brooks

Prev by Date: (usagi-users 00703) [BUG] FATAL BUG in kernel/linux2{2,4}/net/ipv6/route.c (was Re: System crash)
Next by Date: (usagi-users 00705) Re: [BUG] FATAL BUG in kernel/linux2{2,4}/net/ipv6/route.c (was Re: System crash)
Previous by thread: (usagi-users 00672) IPv6 multi-netted source address problem
Next by thread: (usagi-users 00674) Re: Looking for an implementation of DHCPv6
Index(es):
- Date
- Thread