From owner-freebsd-net Sun Jun 11 11:29:33 2000 Delivered-To: freebsd-net@freebsd.org Received: from alive.znep.com (alive.znep.com [207.167.15.58]) by hub.freebsd.org (Postfix) with ESMTP id 5362137B8FD for ; Sun, 11 Jun 2000 11:29:31 -0700 (PDT) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.3/8.9.1) with ESMTP id MAA65935; Sun, 11 Jun 2000 12:29:21 -0600 (MDT) (envelope-from marcs@znep.com) Date: Sun, 11 Jun 2000 12:29:21 -0600 (MDT) From: Marc Slemko To: Dann Lunsford Cc: net@FreeBSD.ORG Subject: Re: Strange MTU related (?) problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 11 Jun 2000, Marc Slemko wrote: > In any case, the proper fix is probably to complain to slashdot and tell > them to fix their probably broken systems. Unfortunately, without access > to both ends, determining if that is the case for sure isn't easy. Well, I just reproduced the same thing on my test setup here by lowering the MTU on the router in the middle, so it looks like it is almost certainly near slashdot's end, probably with their load balancers. So I'm going to drop a note to them asking them to smarten up... As for the general case, education is the only answer. People need to understand that ICMP matters, and that TCP is complex and you need chimps to work on it, not mere monkeys. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message