From owner-freebsd-hackers Tue Jun 25 07:55:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA04405 for hackers-outgoing; Tue, 25 Jun 1996 07:55:51 -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 HAA04394 for ; Tue, 25 Jun 1996 07:55:47 -0700 (PDT) Received: (from tinguely@localhost) by plains.nodak.edu (8.7.1/8.7.1) id JAA24735 for hackers@freebsd.org; Tue, 25 Jun 1996 09:55:37 -0500 (CDT) Date: Tue, 25 Jun 1996 09:55:37 -0500 (CDT) From: Mark Tinguely Message-Id: <199606251455.JAA24735@plains.nodak.edu> To: hackers@freebsd.org Subject: Re: Frame relay and ATM support Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer says: > I'm looking into the support needed in FreeBNSD to support > ATM and Frame relay services in a generic manner. > fr0: flags=c010 mtu 552 > inet 3.3.3.3 --> 4.4.4.4 netmask 0xff000000 > inet 3.3.3.3 --> 140.5.5.5 netmask 0xffffff00 > note: that this doesn't work at the moment because > the addition of the alias wipes out the original if the local address > is the same.. > > (BTW NBMA == non broadcast multiple access) I am interested in the ATM side. I assumed a single adapter name would list all IP connections rather than listing on a virtual circuit basis. I also assumed eventually a person could use Berkeley Packet Filters to display packets on an adapter card simular to an ethernet card. of course this level of ATM support is mega-vaporware.