🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dcom.lans.fddi
Article #8

Re: bridging source routed 802.5 across fddi/ethernet?

#8
From: Rich Seifert
Date: Sat, 31 Oct 1992 01:48
36 lines
2502 bytes
In article <1992Oct29.215308.15464@msuinfo.cl.msu.edu>, craven@egr.msu.edu (Dean Craven) writes:
> Is there any protocol specification or vendor specific implementation
> for tunneling source routed 802.5 frames through a FDDI or Ethernet
> LAN?  That is, can two bridges, each attached to a 802.5 LAN, bridge
> source routed frames across a FDDI/Ethernet LAN to/from 802.5 end
> stations which only know how to source route?
> 
> Or, is this problem only ever solved by network layer routing?
> 
There is no need to tunnel at all. A source routing bridge connected
between a Token Ring and an FDDI or Ethernet will talk correctly to
another source routing bridge connected to the same LAN. That is, no
special measures need to be taken to use an Ethernet or an FDDI as a
backbone for source routed token rings.

It is important that there be no transparent bridges in the path between
the source routing bridges. Transparent Bridges will not pass source
routed frames.

Of course, there will be no connectivity to devices connected to the backbone.
Neither Ethernet nor FDDI devices support source routing. Let's just
hope that it won't cause them to crash--The problem area is when
someone sends a frame to a multicast (or broadcast) with source routing
enabled. The receiving Ethernet or FDDI station will see a source 
address with the Routing Information Indicator set to one. This looks
like a multicast source address, which is outlawed in Ethernet.

I don't believe this is a problem in practice. It may cause a counter
to be bumped, but should not disrupt proper operation.


-- 
Rich Seifert                    Networks and Communications Consulting
seifert@netcom.com              (408) 996-0922
                                (408) 996-2860 FAX
"... specialists in Local Area Networks and Data Communications systems"
Technical Details
Message-ID: <1992Oct31.014819.16180@netcom.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!pipex!bnr.co.uk!bnrgate!nrcnet0!cunews!torn!cs.utexas.edu!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!apple!decwrl!netcomsv!netcom.com!seifert
References: <1992Oct29.215308.15464@msuinfo.cl.msu.edu>

Show Full Headers
Complete Article Headers
Newsgroups: comp.dcom.lans.fddi,comp.dcom.lans.ethernet
Path: arc1-ca.pugleaf.net!sparky!uunet!pipex!bnr.co.uk!bnrgate!nrcnet0!cunews!torn!cs.utexas.edu!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!apple!decwrl!netcomsv!netcom.com!seifert
From: seifert@netcom.com (Rich Seifert)
Subject: Re: bridging source routed 802.5 across fddi/ethernet?
Message-ID: <1992Oct31.014819.16180@netcom.com>
Followup-To: comp.dcom.lka  ans.ethernet
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
References: <1992Oct29.215308.15464@msuinfo.cl.msu.edu>
Date: Sat, 31 Oct 1992 01:48:19 GMT
Lines: 36