From owner-freebsd-atm Wed Jun 14 7:48:48 2000 Delivered-To: freebsd-atm@freebsd.org Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (Postfix) with ESMTP id C71E737C1F4 for ; Wed, 14 Jun 2000 07:48:45 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.9.3/8.9.3) id JAA27074; Wed, 14 Jun 2000 09:48:44 -0500 (CDT) Date: Wed, 14 Jun 2000 09:48:44 -0500 (CDT) From: Mark Tinguely Message-Id: <200006141448.JAA27074@plains.NoDak.edu> To: jgreco@ns.sol.net, jpt@networkcs.com Subject: Re: HARP and BPF Cc: freebsd-atm@FreeBSD.ORG Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > That being said, adding BPF at the IP level can be considered > a trivial task... I think literally less than one dozen lines of code. > What's harder, and I admit that I haven't been following the tcpdump > et. al. discussions, is adding ATM support. That is, passing info > such as VPI/VCI so that one could say, decode UNI messages as well > as IP traffic. > > You could take a look at most any if_* driver with BPF and then > look at /usr/src/sys/netatm/ipatm/{ipatm_input.c,ipatm_output.c}. he could also look at the BPF additions to the IDT NICStAR ATM driver and the associated atmdump program from: ftp://ftp.cs.ndsu.nodak.edu/pub/freebsd/atm/nicstar.tgz ftp://ftp.cs.ndsu.nodak.edu/pub/freebsd/atm/atm-bpf.tgz the BPF adddition could go into any other ATM driver. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message