From owner-freebsd-hackers  Fri Jun 28 06:39:14 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA02959
          for hackers-outgoing; Fri, 28 Jun 1996 06:39:14 -0700 (PDT)
Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA02954
          for <hackers@FreeBSD.ORG>; Fri, 28 Jun 1996 06:39:12 -0700 (PDT)
Received: (from tinguely@localhost) by plains.nodak.edu (8.7.1/8.7.1) id IAA29637; Fri, 28 Jun 1996 08:38:51 -0500 (CDT)
Date: Fri, 28 Jun 1996 08:38:51 -0500 (CDT)
From: Mark Tinguely <tinguely@plains.nodak.edu>
Message-Id: <199606281338.IAA29637@plains.nodak.edu>
To: hackers@FreeBSD.ORG, joe@ns.via.net
Subject: Re: Frame relay and ATM support: virtual interface per vpi?
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I was proposing a "atmdump" to a student interested in doing something
in the network tool area. Since ATM adapters' SAR reconstitutes AAL
packets (and a person couldn't keep up with the construction of
AAL packets from cell in software) that they leave and report the
PDUs with the recieved summary  header (and trailer if appropriate).

In this way, a person can save raw packets, display header, or control
information just like "tcpdump". I would prefer to treat all the virtual
circuits as one interface to have the ability to display everything
and use command line filters to restrict the view just like "tcpdump".

--mark.