From owner-freebsd-bugs  Mon Sep  2  1:30: 8 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1343937B400
	for <freebsd-bugs@hub.freebsd.org>; Mon,  2 Sep 2002 01:30:05 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8972E43E4A
	for <freebsd-bugs@hub.freebsd.org>; Mon,  2 Sep 2002 01:30:04 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g828U4JU081884
	for <freebsd-bugs@freefall.freebsd.org>; Mon, 2 Sep 2002 01:30:04 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g828U4x8081883;
	Mon, 2 Sep 2002 01:30:04 -0700 (PDT)
Date: Mon, 2 Sep 2002 01:30:04 -0700 (PDT)
Message-Id: <200209020830.g828U4x8081883@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Harold Gutch <logix@foobar.franken.de>
Subject: Re: kern/42137: Path MTU broken - initial too-large packet continuously resent
Reply-To: Harold Gutch <logix@foobar.franken.de>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.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-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR kern/42137; it has been noted by GNATS.

From: Harold Gutch <logix@foobar.franken.de>
To: freebsd-gnats-submit@FreeBSD.org, jeff@expertcity.com
Cc: martin.kaeske@stud.tu-ilmenau.de
Subject: Re: kern/42137: Path MTU broken - initial too-large packet continuously resent
Date: Mon, 2 Sep 2002 10:27:56 +0200

 Hi,
 
 I doubt that the problem is ipfilter-related for two reasons:
 
 1) as the original poster stated, FreeBSD actually is aware that
    it got a ICMP NEEDFRAG message, as it does lower the MTU for
    that route - it just does not use the new, lowered, MTU.
 
 2) I'm seeing the same without ipfilter, even with both, the
    router and the client-machine being FreeBSD 4-STABLE.  Neither
    of the two have IPFILTER in the kernel, both have IPFIREWALL
    (ipfw) in it.
 
 
 bye,
   Harold

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