Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 18 Mar 2002 13:44:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 18 Mar 2002 13:44:35 -0500 Received: from sbcs.sunysb.edu ([130.245.1.15]:60878 "EHLO sbcs.cs.sunysb.edu") by vger.kernel.org with ESMTP id ; Mon, 18 Mar 2002 13:44:15 -0500 Date: Mon, 18 Mar 2002 13:40:36 -0500 (EST) From: X-X-Sender: To: Robert Pfister cc: Subject: RE: Trapping all Incoming Network Packets In-Reply-To: <003501c1ceaa$91678f90$1e00a8c0@nomaam> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 18 Mar 2002, Robert Pfister wrote: > There are ways to accomplish similar things in user space. Is there some > reason that you need to do this in the kernel? What is your end-goal with > this? > > Robb > To do it in user space, you have to use the raw socket interface. This by-passes the entire TCP/IP stack. I want to sniff the packets, and make a decision based on certain characteristics of each packet. So I need to have a filter between the IP and link-layer. Also, I do not want the filter to slow down traffic. Hence I believe implementing inside kernel will be more efficient. -- pradipta - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/