[1563] in linux-net channel archive

home help back first fref pref prev next nref lref last post

Re: Ethernet_SNAP

daemon@ATHENA.MIT.EDU (John Paul Morrison)
Sun Dec 31 02:23:20 1995

From: jmorriso@bogomips.com (John Paul Morrison)
To: root@zaphod.wayne.esu1.k12.ne.us (Superuser Account)
Date: 	Sat, 30 Dec 1995 19:04:32 -0800 (PST)
Cc: linux-net@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.91.951230180802.7069A-100000@zaphod.wayne.esu1.k12.ne.us> from "Superuser Account" at Dec 30, 95 06:14:09 pm

> 
> So as you can see, the only way that we can get the workstations on the 
> Ethernet side to use bootp properly is to use Ethernet_SNAP framing.  
> When we use Ethernet_SNAP, we can now BOOTP, connect to anyplace on the 
> other side of the bridge (since it bridged it to Token_Ring_SNAP so the 
> cisco and bootp can read it), however, we cannot talk to our Linux box on 
> the same segment as the sending machine.  If we change our frame type to 
> Ethernet_II, the linux box can now talk to us, but we cannot bootp or hit 
> the router since it gets bridged to Token_Ring frames rather then 
> Token_Ring_SNAP frames.
> 
> Any ideas??


Can you setup a proper IP router between the ethernet and token-ring segments instead?
That wouldn't be as awful as using a bridge. A router can do bootp forwarding too.

> 
> -me
> 
> 
> 

---------------------------------------------------------------------------
BogoMIPS Research Labs  --  bogosity research & simulation  --  VE7JPM  -- 
  jmorriso@bogomips.com  ve7jpm@ve7jpm.ampr.org  jmorriso@ve7ubc.ampr.org
---------------------------------------------------------------------------




home help back first fref pref prev next nref lref last post