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> In-Reply-To: <y7vd6yxlptv.wl@condor.jinmei.org>; from jinmei@isl.rdc.toshiba.co.jp on Fri, Feb 22, 2002 at 08:26:52PM %2B0900 References: <20020207220346.I68508@heresy.dreamflow.nl> <y7vd6yxlptv.wl@condor.jinmei.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Fri, Feb 22, 2002 at 08:26:52PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wrote: > Sorry for the delayed response, > > 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. > > 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 -- Bart Matthaei bart@dreamflow.nl Support wildlife -- vote for an orgy. [-- Attachment #2 --] -----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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020222124504.A89164>