It could also be possible that the server has already seen the packet (identifier) and so it just drops the packet. Tcp has an identifier in it, so if you use a TCP socket, it could be that the stack just drops it and answers, not the server. This is the time-window in TCP...
-----Original Message----- From: Sergej Kononov [mailto:[EMAIL PROTECTED] Sent: vrijdag 28 februari 2003 14:35 To: Alasdair Yates Subject: Re[2]: [WinPcap-users] Send a TCP packet already intercepted AY> You may need to change the source and destination IP addresses. AY> If you swap them over then the checksum will be the same, but if you AY> change them you'll have to recalculate the checksum. AY> Assuming the source and destination TCP ports are the same you can leave AY> them as they are (or swap them over). AY> If you just want to retransmit the packet then you don't need to do AY> anything. For a test scope I have written a simple TCP server which listens to the port, accepts bytes(symbols) and sends them back. I have intercepted (with help of WinPcap) a packet, sent to the server and now I want to sent it once more, but the server does not answer me and sends an empty packet composed of 40 bytes (IP + TCP headers). ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ================================================================== ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
