Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: interfacing to packet drivers Message-ID: Date: 5 Dec 90 21:43:45 GMT References: <1990Dec3.083313.7039@quagga.ru.ac.za> Sender: @grape.ecs.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 17 In-Reply-To: ccdw@quagga.ru.ac.za's message of 3 Dec 90 08:33:13 GMT In article <1990Dec3.083313.7039@quagga.ru.ac.za> ccdw@quagga.ru.ac.za (Dave Wilson) writes: I have been able to get most of the calls to the packet driver to work, with the exception of 'send_pkt'. The pd spec is not clear on how much information must be given to the pd - do I need to supply the complete Ethernet frame, including preamble, Ethernet addresses, and CRC? You don't need the preamble, nor the CRC. Start right off with the Ethernet addresses, the type code word, etc. So, if you wanted to send a completely empty packet, you would set the count to 14 (2*6 bytes address + 2 bytes type code). -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600 It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.