Yes, using /dev/stdin or a dash (-) will cause tcpreplay to read from stdin. I'm not at all familar with dumpcap/airdecap-ng, and it may not be generating a valid libpcap file stream. That means it needs to have a valid libpcap file header, not just the packets.
an easy test: sudo dumpcap -i ath2 -w - | airdecap-ng - >test.pcap then you can try loading up test.pcap file in wireshark to make sure you've got valid ethernet frames. Let me know how that works. -- Aaron Turner http://synfin.net/ http://tcpreplay.synfin.net/ - Pcap editing & replay tools for Unix They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin On Jan 30, 2008 8:10 AM, Craig Carl <[EMAIL PROTECTED]> wrote: > All - > I want to send a stream of packets from my 802.11 interface to a > monitoring application that does not support 802.11 headers. I think I > am on the right track with - > > sudo dumpcap -i ath2 -w - | airdecap-ng - | sudo tcpreplay --intf1=eth0 > /dev/stdin > > I am running a patched version of airdecap-ng that supports > reading/writing to stdin/stdout. I have confirmed that is working. I set > the monitoring tool to monitor eth0, it retuns zero packets. I run > tcpdump -i eth0, no packets. > > Environment - > tcpreplay 3.2.5 > Ubuntu 7.10, fully patched > > > What am I doing wrong, is there a better way to do this? ------------------------------------------------------------------------- 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 Tcpreplay-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
