From owner-freebsd-net Mon May 10 2:58:59 1999 Delivered-To: freebsd-net@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 88CDB14DEA for ; Mon, 10 May 1999 02:58:49 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10gmpE-000GRD-00; Mon, 10 May 1999 16:58:16 +0700 Date: Mon, 10 May 1999 16:58:16 +0700 (ALMST) From: Boris Popov To: Luigi Rizzo Cc: net@FreeBSD.ORG Subject: Re: ipfw misc... In-Reply-To: <199905100619.IAA12419@labinfo.iet.unipi.it> 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 Mon, 10 May 1999, Luigi Rizzo wrote: > > Very nice. Also syntax 'ether type xxx' are very useful. The only > > sorry, yes, this was what i meant with > > ipfw add ether from type xxx ... > > since clearly there is only one ether type in the header... > > > question - how 802.3 frame can be filtered (it doesn't have 'type' field)? > > it must be somewhere.. i wonder actually if FreeBSD does handle IP > packets in 802.3! Definetly, not IP but IPX or XNS :). Look at the code in ether_input() that process XNS family (same things used for IPX). As I understand by specifying 'ether' keyword we should get rid of higher level protocols and use only ethernet header for filtering. -- Boris Popov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message