From owner-freebsd-hackers  Mon Feb 25  2:31:26 2002
Delivered-To: freebsd-hackers@freebsd.org
Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124])
	by hub.freebsd.org (Postfix) with ESMTP
	id BF3CE37B417; Mon, 25 Feb 2002 02:31:10 -0800 (PST)
Received: from localhost ([3ffe:501:4819:2000:e028:ba95:b8bc:b5a5])
	by shuttle.wide.toshiba.co.jp (8.11.6/8.9.1) with ESMTP id g1PAV0o03956;
	Mon, 25 Feb 2002 19:31:00 +0900 (JST)
Date: Mon, 25 Feb 2002 19:30:59 +0900
Message-ID: <y7vwux1q2e4.wl@condor.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: Edwin Groothuis <edwin@mavetju.org>
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Subject: Re: IPv6-over-IPv4 problems since the upgrade to 4.5
In-Reply-To: <20020223084616.G492@k7.mavetju.org>
References: <0D9185CE635BD511ACA50090277A6FCF1359DB@axcs18.cos.agilent.com>
	 <20020216130842.A19081@energyhq.homeip.net>
	 <20020217122510.D491@k7.mavetju.org>
	 <y7v4rk9lobt.wl@condor.jinmei.org>
	 <20020222234829.F492@k7.mavetju.org>
	 <y7vit8pbmg8.wl@condor.jinmei.org>
	 <20020223084616.G492@k7.mavetju.org>
User-Agent: Wanderlust/2.7.5 (Too Funky) Emacs/21.1 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
X-Dispatcher: imput version 980905(IM100)
Lines: 44
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

>>>>> On Sat, 23 Feb 2002 08:46:16 +1100, 
>>>>> Edwin Groothuis <edwin@mavetju.org> said:

>> > And the interface configuration:
>> > gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
>> > 	tunnel inet 203.173.130.126 --> 206.123.31.114
>> > 	inet6 fe80::250:8bff:feb9:2d24%gif0 prefixlen 64 scopeid 0x9 
>> > 	inet6 3ffe:b80:2:460::2 --> 3ffe:b80:2:460::1 prefixlen 128 
>> 
>> Hmm, and what command did you type to cause this problem? If possible,
>> please give me the network topology as well.

> The problem was when "route add -inet6 default -interface gif0" was
> used instead of the "route ... <ipaddress>". For the rest the
> configuration and the commands were the same.

> This is a layout of the 'network':

(snip)

> The symptons were that if I setup a TCP-session, the original message
> is at:
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=279914+284924+/usr/local/www/db/text/2002/freebsd-hackers/20020217.freebsd-hackers

Okay, I understand the configuration.  I did a similar test on a
4.5-RELEASE box, but could not reproduce the problem.  The main
difference in my test case is I did not use ppp, so I guess ppp is
somehow related to this problem...

Now I'd like to know:

- did you see the same problem in an environment without ppp?
- what is the result of netstat -rnal when the kernel is sending
  neighbor solicitations?
- I guess some process (or kernel) modifies the route to the
  destination.  Could you run 'route -n monitor' while the session to
  see the modification?

Thanks,

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message