Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Packet Driver Spec. and Novell.
Message-ID: <8810061458.AA11891@vax.ftp.com>
Date: 6 Oct 88 14:58:56 GMT
References: <8809301744.aa14758@Louie.UDEL.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23

For the standard Novell not-quite-802.2 headers, would it be reasonable
to use a Packet Driver that implemented IEE 802.2 headers on Ethernet as
a separate "class" from Dec-Intel-Xerox Ethernet?  If so, I would assume
you could call access_type() with:

char Novell_ssapdsap[] = {0x11, 0x11};

	if_class = 11;				/* Ether w/802.2 headers */
	type = (char far *) Novell_ssapdsap;
	typelen = 2;				/* Should identify Novell */
	access_type(if_class, 0xFF, 0, type, typelen, novell_receiver);

I assume normal 802.2 usage would usually use typelen = 3 or typelen = 4.

On a related topic, I am working on v1.07 of the packet driver spec, which
will incorporate some of Phil Karn's suggestions regarding not requiring
a handle on driver_info(), and allowing a type of NULL to indicate that
a LAN monitoring program will want all packets (note that this has some
inefficiencies for Netwatch-style monitoring software).  I will post when
I have it available.

James VanBokkelen
FTP Software Inc.