From owner-freebsd-net Wed Jun 27 17: 7:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 7BA5737B401 for ; Wed, 27 Jun 2001 17:07:20 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f5S06xI01154; Wed, 27 Jun 2001 17:06:59 -0700 Date: Wed, 27 Jun 2001 17:06:59 -0700 From: Brooks Davis To: Alfred Perlstein Cc: Stuart Eichert , net@FreeBSD.ORG Subject: Re: Am I missing something? Message-ID: <20010627170659.B30006@Odin.AC.HMC.Edu> References: <20010627111222.A9434@gourdy.coopcomp.com> <20010627143042.F74703@sneakerz.org> <20010627164107.A48973@gourdy.coopcomp.com> <20010627185545.J74703@sneakerz.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="bCsyhTFzCvuiizWE" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010627185545.J74703@sneakerz.org>; from bright@sneakerz.org on Wed, Jun 27, 2001 at 06:55:45PM -0500 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 --bCsyhTFzCvuiizWE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 27, 2001 at 06:55:45PM -0500, Alfred Perlstein wrote: > Actually if you use netgraph this is all already done. You can > see the netgraph callbacks in bother ether_input and ether_output, > just use those and you should be fine. I'm not terribly familiar > with netgraph, however i've heard it's trivial to use a subset of > the facilities, meaning using netgraph to provide your hooks should > be simple and not require you to learn an aweful lot about netgraph > versus just getting your stuff working. >=20 > All you need to do is add your handler to the ng_ether_input_p > and ng_ether_input_orphan_p callchains and you should be fine. For adding a new protocol, you can currently use the orphan's interface if you don't need any other protocols. Work needs to be done to allow tapping of specific protocols via the ng_ether_input interface. I was thing about doing it, but the project I was going to do it for took a different direction. If you want to support adding new ethernet protocols, this is definatly the way to go. This is also more or less necessicary to build a fully netgraph implementation of IP or similar protocols[0]. -- Brooks [0] Before someone flames me ;-), I only suggest that it would be very useful for working on research protocols if we had all the important building blocks (ip, icmp, tcp, udp, etc) available as netgraph nodes to allow easy testing of intresting new systems. --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --bCsyhTFzCvuiizWE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7OnUiXY6L6fI4GtQRApfUAJ0RNLspKLHAg6qI4fhK8cXavT374wCfawag XvKA2vXIr3HsE4Ln5a6tc70= =mZAq -----END PGP SIGNATURE----- --bCsyhTFzCvuiizWE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message