From owner-freebsd-hackers Sun Jan 25 21:50:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08126 for hackers-outgoing; Sun, 25 Jan 1998 21:50:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from plugcom.ru (uucp@radiance.plugcom.ru [195.2.73.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08118 for ; Sun, 25 Jan 1998 21:50:04 -0800 (PST) (envelope-from usr02.primenet.com!tlambert@minas-tirith.pol.ru) Received: from minas-tirith.pol.ru (uucp@localhost) by plugcom.ru (8.8.7/8.8.6) with UUCP id IAA16147 for freebsd.org!freebsd-hackers; Mon, 26 Jan 1998 08:50:01 +0300 (MSK) Received: (from uucp@localhost) by minas-tirith.pol.ru (8.8.7/8.8.7) with UUCP id IAA10570; Mon, 26 Jan 1998 08:29:35 +0300 (MSK) (envelope-from tlambert@usr02.primenet.com) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by plugcom.ru (8.8.7/8.8.6) with ESMTP id BAA06510; Mon, 26 Jan 1998 01:35:29 +0300 (MSK) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA25337; Sun, 25 Jan 1998 15:35:23 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd025329; Sun Jan 25 15:35:19 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA14069; Sun, 25 Jan 1998 15:35:19 -0700 (MST) From: Terry Lambert Message-Id: <199801252235.PAA14069@usr02.primenet.com> Subject: Re: Ethernet_802.2 and IPX To: tarkhil@minas-tirith.pol.ru (Alex Povolotsky) Date: Sun, 25 Jan 1998 22:35:18 +0000 (GMT) Cc: freebsd.org!freebsd-hackers@minas-tirith.pol.ru In-Reply-To: <199801251206.PAA08837@minas-tirith.pol.ru> from "Alex Povolotsky" at Jan 25, 98 03:06:44 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > Why doesn't IPX support frame types other than Ethernet_II? Is there any > black magic involved? Are there any description on making IPX router > (IPXrouted says nothing on how-to)? Nobody has written 802.3 LLC code (well, someone did, and implemented NetBEUI using it, over at Mitre, but the code isn't released yet). It is mostly there in the FDDI code... this is the same thing preventing use of token ring drivers. You can build a driver, but you can't make it talk to other machines without the right LLC. People have reported working on 802.3 IPX; check the list archives. I'm certainly not authoritative about whether one of these people has completed the code. 8-). Even so, Novell screwed up the 802.3 frame type usage by IPX. Instead of putting the right value in the length field and putting an encapsulated header containing the protocol type, they put the protocol type in the length field. A host can distibguish this because the protocol type is a high enough number that it would result in an illegally large packet. This is a kludge, and it's not a very good idea to use 802.3 IPX because of this. Most NetWare servers can do both frame types simultaneously, and you can run both frame types on the same wire successfully. One major advantage is that you can run NetWare for UNIX and Pathworks for VMS (NetWare) if you use Ethernrt II IPX. If you don't run Ethernet II, then you will have to load dual stacks on some NetWare server so it can act as a gateway. The Ethernet II IPX machines will not be able to respond to "GetNearestServer" requests. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.