Date: Thu, 12 Oct 1995 10:37:42 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: jhay@mikom.csir.co.za (John Hay) Cc: julian@ref.tfs.com, hackers@FreeBSD.ORG Subject: Re: IPX now available Message-ID: <199510121737.KAA15390@phaeton.artisoft.com> In-Reply-To: <199510120558.HAA23234@zibbi.mikom.csir.co.za> from "John Hay" at Oct 12, 95 07:58:32 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510121737.KAA15390>