From owner-freebsd-net  Fri Feb 22  3:45:13 2002
Delivered-To: freebsd-net@freebsd.org
Received: from dreamflow.nl (dreamflow.nl [62.58.36.22])
	by hub.freebsd.org (Postfix) with SMTP id 1346037B404
	for <net@freebsd.org>; Fri, 22 Feb 2002 03:45:06 -0800 (PST)
Received: (qmail 21664 invoked by uid 1000); 22 Feb 2002 11:45:04 -0000
Date: Fri, 22 Feb 2002 12:45:04 +0100
From: Bart Matthaei <bart@dreamflow.nl>
To: "JINMEI Tatuya / ?$B?@L@C#:H?(B" <jinmei@isl.rdc.toshiba.co.jp>
Cc: net@freebsd.org
Subject: Re: mtu on gif devices
Message-ID: <20020222124504.A89164@heresy.dreamflow.nl>
References: <20020207220346.I68508@heresy.dreamflow.nl> <y7vd6yxlptv.wl@condor.jinmei.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <y7vd6yxlptv.wl@condor.jinmei.org>; from jinmei@isl.rdc.toshiba.co.jp on Fri, Feb 22, 2002 at 08:26:52PM +0900
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.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-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org


--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 22, 2002 at 08:26:52PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wr=
ote:
> Sorry for the delayed response,
>=20
> How did you configure (particularly the default) routes on the host
> "colo"?  I've seen several reports that the default route on a tunnel
> link has somehow become bogus.
>=20
> BTW: if the problem happens regardless of the MTU value, the MTU
> setting may not be the reason.

Jinmei,

The problem has already been fixxed. NAT + Gif tunnel is known to cause
mtu problems. I overlooked that. I didn't have this problem in 4.4, so
obviously something changed. (I also get a weird traceroute output
when i trace something in my homenet from the outside world since my
update to 4.5. If you want to hear this issue, let me know.)

Regards,

Bart

--=20
Bart Matthaei                 bart@dreamflow.nl=20

Support wildlife -- vote for an orgy.

--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE8di9Agcc6pR+tCegRAlnqAKCqLGSZiib9Pe91r8WZ7YV5UNfXFQCeJNv0
hooMi8uR+FUeO8UusGQ0FoU=
=0fFZ
-----END PGP SIGNATURE-----

--J2SCkAp4GZ/dPZZf--

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