The usage is correct, indeed. However, pcap_sendqueue_transmit respects the timestamps within the queue, but not between two different calls to the same function.
Suppose that the last packet in the queue has a timestamp of 10s, and the first packet of the next queue has a timestamp of 11s. When pcap_sendqueue_transmit transmits the second queue, it will not respect the timestamp of the first packet(11s), it will send it immediately. Have a nice day GV ----- Original Message ----- From: "Noam Cohen" <[email protected]> To: <[email protected]> Sent: Tuesday, October 27, 2009 4:09 AM Subject: [Winpcap-users] correct usage of pcap_sendqueue_transmit? > GV, > I have a PCAP file of 400MB which has to be played in endless loop. I read > a packet and send it using the Transmit() described in the pseudo code. > In the wireshark tutorial, "sendcap", the whole file is added into the > transmit queue and then transmitted. This does not work with large files > (or when a loop play is needed). > In the Transmit(), I fill the queue with packets and when near fullness, > call pcap_sendqueue_transmit(). I would expect it to *clear* the queue but > it does not happen. The only way I see to reuse the queue is to destroy > and then allocate it again. Is this the way it is meant to be ?! > > Are the packets which are added to the queue actually copied? I assume so > since there is no other mechanism to keep the memory valid. > > Thanks > Noam > _______________________________________________ > Winpcap-users mailing list > [email protected] > https://www.winpcap.org/mailman/listinfo/winpcap-users _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users
