home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.isdn
- Path: sparky!uunet!europa.eng.gtefsd.com!emory!swrinde!zaphod.mps.ohio-state.edu!howland.reston.ans.net!usc!elroy.jpl.nasa.gov!ames!sgi!rigden.wpd.sgi.com!rpw3
- From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
- Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
- Message-ID: <ve5te50@sgi.sgi.com>
- Sender: rpw3@rigden.wpd.sgi.com
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Date: Thu, 28 Jan 1993 05:02:19 GMT
- Lines: 35
-
- dcarr@gandalf.ca (Dave Carr) writes:
- +---------------
- | Bridging can be done transparently to the protocol, and thus one chunk
- | of code works on all protocols. Routing requires separate code for
- | each protocol.
- +---------------
-
- Actually, while this is mostly true, even bridging requires requires
- separate code for some protocols depending on the media being bridged.
-
- Example #1, FDDI to Ethernet: All protocols encapsulated with the
- 802.2/LLC/SNAP/OUI=0/ethertype method are converted to D/I/X Ethernet
- encapsulation with the same "ethertype" *EXCEPT* Appletalk Phase 2,
- which insists on using the 802.3/LLC/SNAP/OUI=0/ethertype encapsulation.
-
- Example #2, 802.5 Token Ring to FDDI: The ARP protocol must have the 48-bit
- hardware MAC addresses *inside* the ARP packet in the ar_sha and ar_tha fields
- (that is, *above* the MAC layer) bit-flipped, since on FDDI (as on every MAC
- layer except 802.5) those fields are carried in "canonical" order, but on
- 802.5 Token Ring they are carried in 802.5 bit-order. [Note: On FDDI, the
- addresses in the FDDI *MAC* layer are carried in 802.5 order, but not the
- ARP ar_{s,t}ha fields.]
-
- I'm sure someone can provide some examples of protocol-sensitive XXX-to-ISDN
- bridging (if not today, then "soon")...
-
-
- -Rob
-
- -----
- Rob Warnock, MS-9U/510 rpw3@sgi.com
- Silicon Graphics, Inc. (415)390-1673
- 2011 N. Shoreline Blvd.
- Mountain View, CA 94043
-
-