From owner-freebsd-net@FreeBSD.ORG  Wed Feb 25 04:51:54 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 05EDA16A4CE
	for <freebsd-net@freebsd.org>; Wed, 25 Feb 2004 04:51:54 -0800 (PST)
Received: from smtp3.libero.it (smtp3.libero.it [193.70.192.127])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9050643D1F
	for <freebsd-net@freebsd.org>; Wed, 25 Feb 2004 04:51:53 -0800 (PST)
	(envelope-from ml.ventu@flashnet.it)
Received: from soth.ventu (151.37.23.42) by smtp3.libero.it (7.0.020-DD01)
	id 401D5C59009F27FA for freebsd-net@freebsd.org;
	Wed, 25 Feb 2004 13:51:52 +0100
Received: from mailer (xanatar.ventu [10.1.2.6])
	by soth.ventu (8.12.6p3/8.12.6) with SMTP id i1PCppmZ031547
	for <freebsd-net@freebsd.org>; Wed, 25 Feb 2004 13:51:52 +0100 (CET)
	(envelope-from ml.ventu@flashnet.it)
Message-Id: <200402251251.i1PCppmZ031547@soth.ventu>
To: freebsd-net@freebsd.org
Priority: Normal
X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0)
Date: Wed, 25 Feb 2004 13:51:52 EST
From: Andrea Venturoli <ml.ventu@flashnet.it>
Subject: Re: Bad loopback traffic not stopped by ipfw.
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Andrea Venturoli <ml@netfence.it>
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2004 12:51:54 -0000

** Reply to note from Iasen Kostov <tbyte@OTEL.net> Wed, 25 Feb 2004 14:37:25 +0200

>netstat -s -p ip
>..
>..
>..
>        3575124 datagrams with bad address in header
>  
>    Could it be this that drops "bad" packets before they enter the IPFW ?

Nice, it could be, but I'm not so expert as to tell for sure. Can someone with more insight confirm? And possibly
provide a pointer on why it is so, who blocks them, which are the criteria, ...?

In fact I think they ARE blocked, because otherwise I would see "Connection attempt ..." log entries.

Here it shows: 72641 datagrams with bad address in header


 bye & Thanks
        av.