So in theory if this is working - sudo dumpcap -i ath2 -w - | airdecap-ng - | sudo tcpreplay --intf1=eth0 /dev/stdin
and receiving a constant flow of traffic and then at the same time in a different window I run sudo tcpdump -i eth0 I should see the traffic coming off of ath2? If I've got that much right conceptually I can start troubleshooting the details. I guess I am a little confused by the idea of "in" and "out" on an interface. Is tcpreplay sending the traffic "out" and tcpdump is looking for traffic coming "in"? Thanks, Craig ________________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Aaron Turner [EMAIL PROTECTED] Sent: Wednesday, January 30, 2008 10:48 AM To: Main forum for tcpreplay Subject: Re: [Tcpreplay-users] Is tcpreplay the correct tool? Not sure why you're not seeing the packets... what's this "monitoring tool" you're referring to? Maybe that's the problem. As a side note though, you're not capturing the entire packet- they're being truncated at about 60bytes. -Aaron On Jan 30, 2008 9:19 AM, Craig Carl <[EMAIL PROTECTED]> wrote: > Wireshark opens that file with no problem, looks absolutely correct. > > Craig > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Tcpreplay-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tcpreplay-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Tcpreplay-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
