From owner-freebsd-atm Mon Sep 22 14:46:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23410 for atm-outgoing; Mon, 22 Sep 1997 14:46:53 -0700 (PDT) Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA23401 for ; Mon, 22 Sep 1997 14:46:49 -0700 (PDT) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.5/8.8.5) id QAA24799; Mon, 22 Sep 1997 16:46:43 -0500 (CDT) Date: Mon, 22 Sep 1997 16:46:43 -0500 (CDT) From: Mark Tinguely Message-Id: <199709222146.QAA24799@plains.NoDak.edu> To: freebsd-atm@freebsd.org Subject: atmdump correction Cc: ylim@netstar.com Sender: owner-freebsd-atm@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sep 10, 1997, I said: > As a NDSU Graduate Student, Yen Yen Lim (http://www.cs.ndsu.NoDak.edu/~lim/ > and mailto:ylim@netstar.com), made some changes to BPF/TCPDUMP to trace > incoming/outgoing ATM packets. > > Since I had not chosen a ATM stack for my FreeBSD driver until she was nearly > defending her thesis, the code that parses and prints ATM PDUs is based > on LANE (which she tested on a Solaris machine using the Sun ATM cards). > Hopefully, I can add the IETF's IP over ATM information into the atmdump > in the near future. I was wrong, Yen Yen did implement parsing/printing for IETF's Classical IP over ATM, and not LANE parsing/printing as I stated earlier. I changed her printing routines to use the standard tcpdump IP (TCP, UDP, ICMP) printing routine because it give much more details on the packet. I also change to code to support point to point IETF's Classical IP over ATM (basically ignoring the missing LLC header). I fixed the raw cell BPF tracing in the nicstar driver (I had the old cell header order in the passing of BPF header). There is another error in the NICStAR card that causes the reception of Payload types to be wrong in certain cases: Send a payload type of 1, 4 or 6 and the last cell of the transmission will be sent/received as type 2, 5, or 7 respectively. I am stilling thinking of changing the BPF pseudo-header on the driver/atmdump to include: 1) AAL (BPF can filter on this field) 2) Encoding type (LANE, IETF IP over ATM, NATIVE ATM, etc) future atmdump support for: 1) the atmdump now needs LANE parsing/printing support. 2) better native ATM the nicstar code ftp://ftp.cs.ndsu.NoDak.edu/pub/freebsd/atm/nicstar.tgz the atmdump ftp://ftp.cs.ndsu.NoDak.edu/pub/freebsd/atm/atm-bpf.tgz From owner-freebsd-atm Thu Sep 25 06:44:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA16862 for atm-outgoing; Thu, 25 Sep 1997 06:44:04 -0700 (PDT) Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA16837 for ; Thu, 25 Sep 1997 06:43:41 -0700 (PDT) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.5/8.8.5) id IAA32415; Thu, 25 Sep 1997 08:43:30 -0500 (CDT) Date: Thu, 25 Sep 1997 08:43:30 -0500 (CDT) From: Mark Tinguely Message-Id: <199709251343.IAA32415@plains.NoDak.edu> To: rlyon@ozemail.com.au Subject: FWD: NIST ATM Network Simulator. Cc: freebsd-atm@freebsd.org Sender: owner-freebsd-atm@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a forwarded question (from freebsd-questions) in case someone here can answer his question. --mark. --------------- on Wed Sep 24 21:49:12 1997, Richard Lyon asks: > I am currently attempting to port the NIST ATM > simulator to FBSD. It compiles correctly but > does suffer from the dreaded floating point exceptions > during simulations. > > Has anyone run this application on FBSD successfully? > > Looking at the source, I can see most of the problems > relate to the differences between the original development > environment and FBSD. Not a big deal, but it will take a > few weeks work, which I would rather avoid if possible. > > Regards ...