Hi.
Sorry for the long delay in the answer.
I think you are "queuing" packets by using something like pcap_dump or similar. WinPcap (or better, libpcap) prepends each packet in a savefile with a 16 bytes header containing the oroginal and captured length of the packet, and the timestamp of the packet.
Exactly, which APIs do you want to use to send packets? Have you read the winpcap manuals?
Why don't you use the winpcap standard APIs to read and write capture files?
Have a nice day GV
----- Original Message ----- From: "Venkatramani, Bharath" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 15, 2004 3:49 PM
Subject: [WinPcap-users] Sending packets in a queue
When I send packets using queues, I notice something. In ethereal, the total number of bytes off the wire is, for instance, 92 bytes. However, when I put that same packet in a queue, I notice that caplen is (packetsize + 16) bytes all the time (in this case, it is 108 bytes). Why is this so?
I have dissected the packet into its Link-layer, header, data and trailer parts. Can I simply recombine these parts and shove the packet in a queue to send it? Thanks.
================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/winpcap-users@winpcap.polito.it/
To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/winpcap-users@winpcap.polito.it/
To unsubscribe use mailto: [EMAIL PROTECTED]
==================================================================
