[1558] in linux-net channel archive
Ethernet_SNAP
daemon@ATHENA.MIT.EDU (Superuser Account)
Sat Dec 30 20:26:04 1995
Date: Sat, 30 Dec 1995 18:14:09 +0000 (GMT)
From: Superuser Account <root@zaphod.wayne.esu1.k12.ne.us>
To: linux-net@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.91.951229090401.2455C-100000@pharcyde.sluh.edu>
Hello!
I recently moved our Linux 1.2.13 box from our Token Ring network to the
Ethernet segment, and have run into a little bit of a problem. The
problem is that we need to get Linux to speak to systems running
Ethernet_SNAP frame types. I have seen that SNAP code seems to exist in
the kernel, but it doesn't seem to be working or I don't have it setup
right.
Let me give some background on the problem incase someone else has a
better solution:
Our backbone is token ring running Token_Ring and Token_Ring_SNAP
frames. Our Netware server, BOOTP server (Using Novell Lan Workgroup)
and our router (Cisco 2511) are all on the backbone. IP on the token
side is using Token_Ring_SNAP frames.
Our Ethernet is standard 10Mbit Ethernet bridged by an IBM 8229 bridge.
The bridge can bridge all 4 ethernet frame types, but it does it like this:
802.2 -> Token_Ring
802.3 -> Token_Ring
Ethernet_II -> Token_Ring
Ethrenet_SNAP -> Token_Ring_SNAP
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??
-me
