Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Sep 1999 15:16:06 -0500 (CDT)
From:      Mark Tinguely <tinguely@plains.NoDak.edu>
To:        cendres@newbridge.com, freebsd-atm@FreeBSD.ORG
Subject:   Re: RFC1483 bridged 802.3 LLC encapsulation
Message-ID:  <199909102016.PAA15877@plains.NoDak.edu>

next in thread | raw e-mail | index | archive | help

>  Is anybody working on RFC1483 bridged 802.3 LLC encapsulation for
>  the NATM drivers? The capability I am after is support for a PVC to
>  an Ethernet-to-ATM bridge. Would anybody be willing to give me some
>  implementation hints?

the driver will need to define network interface. you can look at any
ethernet card driver to see how to do that (look for the if_attach and
ether_ifattach statements).

when you recieve a packet, pull off the LLC/SNAP run the packet
through ether_input() -- look at an ethernet card driver for examples.

on transmission, dequeue the packet from the interface send queue, slap
on the LLC/SNAP header, and send new packet to the ATM device's output
routine.

the problem is how do we tell that this packet coming in on a particular
virtual circuit is to go to the RFC1483 protocol stack, rather than
being sent to the socket protocol stack? ...I wish I could say there
is already a freely available, built-in way for FreeBSD to make this
decision and we could control it with a user command like atmconf, but
there isn't. I don't know the Washington University NATM stack, but I
would venture to say you need to make this packet processing decision
in the device driver right about the call to atm_input().

--mark.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-atm" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909102016.PAA15877>