From owner-freebsd-net Thu Nov 7 14:33:44 2002 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 EEB2337B401; Thu, 7 Nov 2002 14:33:42 -0800 (PST) Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7222143E42; Thu, 7 Nov 2002 14:33:42 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0030.cvx40-bradley.dialup.earthlink.net ([216.244.42.30] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 189vDO-0001dV-00; Thu, 07 Nov 2002 14:33:31 -0800 Message-ID: <3DCAE9E1.768685AF@mindspring.com> Date: Thu, 07 Nov 2002 14:32:01 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Steve Tremblett , freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: input source for network application References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Julian Elischer wrote: > Also look at ng_etf the ethertype filter.. > it is designed to connect to an ether node and filter out packets > with a particular ethertype. yuo could alter it to examine for a > particular tcp port number too. [ ... ] A more interesting problem is how to hook an address family to a netgraph node. > One possibility I am looking at is adding a netgraph hook onto ipfw > so one could grab a packet on ipfw and force it out to a netgraph hook. This would be moderately useful. Another alternative would be to provide a means of hooking all input from a particular ethernet card into the netgraph framework, and run the machine with multiple ethernet cards -- one for the normal stack, and one for the alternate stack. Another method is to use an alternate (fictitious) protocol family and therefore ethertype that's a duplicate of the TCP stack, and do the processing there, instead. This is also rather trivial. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message