Date: Thu, 12 Oct 1995 17:28:28 +0200 (SAT) From: John Hay <jhay@mikom.csir.co.za> To: dennis@etinc.com (dennis) Cc: hackers@freebsd.org Subject: Re: IPX now available Message-ID: <199510121528.RAA03363@zibbi.mikom.csir.co.za> In-Reply-To: <199510121522.LAA06679@etinc.com> from "dennis" at Oct 12, 95 11:22:54 am
next in thread | previous in thread | raw e-mail | index | archive | help
> >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. > > > I don't know how you wrote your code, but it isn't that difficult, its just > another case. When you > get an 802.3 packet, you can add an additional sanity test by looking at the > header to try to verify that > it is an IPX packet. There's no perfect way to do it, but people have been > doing it for years without > much impact on anything else. > Yes the receiving side is easy. It is the transmit part that is difficult. Not to do it, but to know when to use 802.3 and when to use Ethernet_II. You must have some kind of flag to know which protocol to use, or you must wait and hope someone will transmit a packet so that you can see which protocol is being used. John -- John Hay -- John.Hay@csir.co.za
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510121528.RAA03363>