Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!ASYLUM.SF.CA.US!romkey
From: romkey@ASYLUM.SF.CA.US (John Romkey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NE1000 Clarkson PD strangeness
Message-ID: <9103060805.AA10658@asylum.sf.ca.us>
Date: 6 Mar 91 16:05:49 GMT
References: <1991Mar06.004805.5386@nestroy.wu-wien.ac.at>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 10

Returning a length that's too long shouldn't hurt things with a good
IP implementation (which KA9Q is). IP carries its own length field in
its header; the IP layer tends to make sure that there are at least
enough bytes and then go ahead and process the packet using the IP
length instead of the hardware length.

This is necessary in part because ethernet has a minimum of 60 bytes,
which is longer than many IP packets would be.
		- john romkey			Epilogue Technology
USENET/UUCP/Internet:  romkey@asylum.sf.ca.us	FAX: 415 594-1141