From owner-freebsd-current  Wed Sep 11 15:50:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA10288
          for current-outgoing; Wed, 11 Sep 1996 15:50:52 -0700 (PDT)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA10281
          for <current@freebsd.org>; Wed, 11 Sep 1996 15:50:49 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id WAA18408; Wed, 11 Sep 1996 22:49:04 GMT
Date: Thu, 12 Sep 1996 07:49:04 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Terry Lambert <terry@lambert.org>
cc: John Hay <jhay@mikom.csir.co.za>, jkh@time.cdrom.com, current@freebsd.org
Subject: Re: Does IPX routing work? ... Of course. :-)
In-Reply-To: <199609112000.NAA05402@phaeton.artisoft.com>
Message-ID: <Pine.SV4.3.93.960912074731.18328A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 11 Sep 1996, Terry Lambert wrote:

> > 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.

I thought it was just implemented before IEEE fully defined it.

Regards,


Mike Hancock