From owner-freebsd-current  Wed Sep 11 13:03:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA25153
          for current-outgoing; Wed, 11 Sep 1996 13:03:10 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA25146
          for <current@freebsd.org>; Wed, 11 Sep 1996 13:03:06 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA05402; Wed, 11 Sep 1996 13:00:54 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199609112000.NAA05402@phaeton.artisoft.com>
Subject: Re: Does IPX routing work? ... Of course. :-)
To: jhay@mikom.csir.co.za (John Hay)
Date: Wed, 11 Sep 1996 13:00:54 -0700 (MST)
Cc: jkh@time.cdrom.com, current@freebsd.org
In-Reply-To: <199609111512.RAA18065@zibbi.mikom.csir.co.za> from "John Hay" at Sep 11, 96 05:12:08 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-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Three things I can think of.
> 
> Our IPX only support ETHERNET_II framing. NOT 802.3 (yet)
> 

You can not support 802.3 framing in a Novell IPX environment.

Novell implemented 802.3 encapsulation incorrectly.  It is only the
coincidence that the packet type for IPX is an illegal length which
allows it to be detected and function at all.

You will need to similarly hack the IPX for FreeBSD if you wish to
support what Novell calls 802.3 -- there is no encapsulation header,
and this is the implementation error.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.