> I suspect packets replayed through tcpreplay didn't reach the tcp/ip
stack.
That is possible. You can check, by running a tcpdump or wireshark or
whatever on the same network ... even on the same host and interface as
tcpreplay.
If you have a setup problem of some sort, you'll only see the packets
tcpreplay is emitting.
If you are doing everything right, you'll also see the RST that your server
emits, when it sees the now bogus ACK spat out by tcpreplay. A valid ACK
has a TCP sequence number copied from the SYNACK that the server sent in
response to the recorded SYN that tcpreplay re-played.
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Tcpreplay-users mailing list
Tcpreplay-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
Support Information: http://tcpreplay.synfin.net/trac/wiki/Support
