Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 May 2006 01:35:35 +0900
From:      JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To:        Ed Schouten <ed@fxq.nl>
Cc:        "Bruce A. Mah" <bmah@freebsd.org>, FreeBSD Net <freebsd-net@freebsd.org>
Subject:   Re: nd6_lookup prints bogus messages with point to point devices
Message-ID:  <y7v7j4k623s.wl%jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <20060508065841.GN15353@hoeg.nl>
References:  <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Mon, 8 May 2006 08:58:41 +0200, 
>>>>> Ed Schouten <ed@fxq.nl> said:

> I'm seeing the messages on the machine in Eindhoven (running RELENG_6
> from a few days/weeks ago), but they also show up on my HEAD machine at
> home. Below is the output of `ifconfig gif0` on my machine at home:

> | gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
> |         tunnel inet 83.181.147.170 --> 193.109.122.244
> |         inet6 fe80::202:a5ff:fe58:4927%gif0 prefixlen 64 scopeid 0x7 
> |         inet6 2001:7b8:310::1 --> 2001:7b8:2ff:a4::1 prefixlen 128 

> As far as I know, the latest FreeBSD releases show an error message when
> assigning an address with a non-128 prefixlen.

Sorry for not responding sooner, but I think I've figured out the
problem.  I'm now testing a local patch to this problem, and will
report the details once I confirm the behavior.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y7v7j4k623s.wl%jinmei>