From: narke <nar...@gm...> - 2011-10-13 02:06:49
|
On 13 October 2011 02:46, Aaron Turner <syn...@gm...> wrote: > Actually, it's more then just TCP windowing. Probably the single > biggest issue is that tcpreplay *never* EVER reads from the network. > So yeah, when the server replies to your TCP Syn with a Syn/Ack and > sets it's initial sequence number, it never reads that and can't even > complete a 3 way handshake. > > So yeah, the FAQ is correct. I didn't just write that to confuse people. :) > > As for the name, well I actually didn't name tcpreplay... I just took > over the project something like 10 years ago. I'm pretty sure it was > named this way as an opposite of tcpdump, which as you know does more > then just TCP too. > > -Aaron > Aaron, Thanks for the explanation. For my testing purpose -- to test a simple TCP server application -- do you think what tool I can use (together with tcpdump of course)? The Wireplay seems too old, I currently don't have a successful compile on it (but I will find time to try again). Best Regards, -- Life is the only flaw in an otherwise perfect nonexistence -- Schopenhauer narke public key at http://subkeys.pgp.net:11371 (nar...@gm...) |