Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!usc!apple!agate!ucbvax!ASYLUM.SF.CA.US!romkey
From: romkey@ASYLUM.SF.CA.US (John Romkey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: re: interfacing to packet drivers
Message-ID: <9012051051.AA08373@asylum.sf.ca.us>
Date: 5 Dec 90 18:51:59 GMT
References: <1990Dec3.083313.7039@quagga.ru.ac.za>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 14

No. Just provide the ethernet packet starting at the first byte of the
MAC header (the first byte of the destination address) and ending with
the last byte of the ethernet packet's data. It would be absurd for
the application to have to provide preamble and CRC, but it's
necessary to provide ethernet addresses, otherwise how do you control
where the packet is sent?

Two things I don't remember: you may have to be sure that the packet
is at least the length of the minimum ethernet packet size (60 bytes
or so), and you may have to make sure your source ethernet address is
set because not all ethernet chips/boards set it for you. The spec
doesn't say anything about this.
		- john romkey			Epilogue Technology
USENET/UUCP/Internet:  romkey@asylum.sf.ca.us	FAX: 415 594-1141