From owner-freebsd-net Sat Feb 2 11:57:34 2002 Delivered-To: freebsd-net@freebsd.org Received: from artemis.drwilco.net (diana.drwilco.net [66.48.127.79]) by hub.freebsd.org (Postfix) with ESMTP id E7B9D37B416 for ; Sat, 2 Feb 2002 11:57:27 -0800 (PST) Received: from ceres.drwilco.net (docwilco.xs4all.nl [213.84.68.230]) by artemis.drwilco.net (8.11.6/8.11.6) with ESMTP id g12JvHi31150 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO); Sat, 2 Feb 2002 14:57:19 -0500 (EST) (envelope-from drwilco@drwilco.net) Message-Id: <5.1.0.14.0.20020202202155.01b9e390@mail.drwilco.net> X-Sender: lists@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 02 Feb 2002 20:32:49 +0100 To: Shaun Jurrens , freebsd-net@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: Weird path MTU autodiscovery problem in 4.5-RELEASE Cc: Alexey Luckyanchikov In-Reply-To: <20020202191943.B65253@atreides.freenix.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >#>Server have not any filters. ipfw support is compiled in, but first rule >#>is 'allow ip from any to any' and dump which you can see below was made >#>on server. > > yeah, but icmp is it's own protocol, so you're probably filtering it >and bpf will see it because it sees what comes in on the interface before >ipfw processes it. ICMP isn't allowed by default in ipfw. I'd suggest you >unload the module, if possible and see if it works correctly then. ICMP is an IP protocol, if the very first rule in IPFW is 'allow ip from any to any' then ICMP is allowed. Doc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message