From owner-freebsd-hackers  Thu Oct 12 10:44:10 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id KAA23197
          for hackers-outgoing; Thu, 12 Oct 1995 10:44:10 -0700
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA23189
          for <hackers@FreeBSD.ORG>; Thu, 12 Oct 1995 10:44:06 -0700
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA15390; Thu, 12 Oct 1995 10:37:42 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199510121737.KAA15390@phaeton.artisoft.com>
Subject: Re: IPX now available
To: jhay@mikom.csir.co.za (John Hay)
Date: Thu, 12 Oct 1995 10:37:42 -0700 (MST)
Cc: julian@ref.tfs.com, hackers@FreeBSD.ORG
In-Reply-To: <199510120558.HAA23234@zibbi.mikom.csir.co.za> from "John Hay" at Oct 12, 95 07:58:32 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1167      
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

> > I've never gotten to the bottom of what the difference is..
> > 
> > > It isn't difficult to support 802.3. The problem is in setting it from the
> > > userlevel. If it is just a kernel compile time option it should be easy. I
> > > have thought of using one of the link flags in the ifnet structure, then
> > > you can just add it to the ifconfig commandline. It would mean the minimum
> > > changes. I think you would only need to change if_ethersubr.c then.
> > > 
> The ethernet II header consists of:
> 6 bytes destination address | 6 bytes source address | 2 bytes protocol type.
>                                                        eg: ip, ipx, etc
> 
> The ethernet 802.3 header consists of:
> 6 bytes destination address | 6 bytes source address | 2 bytes packet length.

Note that IPX 802.3 packets are not valid 802.3 packets, quite.  The
header encapsulation is abbreviated.  Watching the wire should be enough
to figure this out, but you won't get a real 802.3 unless you watch non-IPX,
non-Novell traffic.


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