From owner-freebsd-hackers Mon Jul 14 11:52:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07656 for hackers-outgoing; Mon, 14 Jul 1997 11:52:33 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07651 for ; Mon, 14 Jul 1997 11:52:31 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01772; Mon, 14 Jul 1997 11:44:35 -0700 From: Terry Lambert Message-Id: <199707141844.LAA01772@phaeton.artisoft.com> Subject: Re: IPX routing? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 14 Jul 1997 11:44:35 -0700 (MST) Cc: jhay@mikom.csir.co.za, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199707140949.TAA09576@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 14, 97 07:19:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Why? I don't know of any clients that can't do Ethernet_II framing. > > Well, when I asked why half of their workstations used 802.2 and the > other half used 802.3, they complained that it was "too hard" to have > them all work the same. Getting them to move all of them to > Ethernet_II would, I think, have been difficult without a Very Good > Argument. If you have one, I'm all ears of course 8) One good argument is that the 802.3 framining use incomplete packet headers, and is adulterated. The reason it works is because the IPX packet type uses an ID which is an invalid length in a correctly encoded packet, and you can make an exception in recognition on that basis. In reality, IPX on 802.3 is not correctly encapsulated according to the 802.3 specification. How's that? 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.