On Sun, Apr 07, 2002 at 07:07:54PM +0300, Dotan Shavit wrote:
> Thank you all for the comments.
> I took a second look at "tcpreplay" and still tcpdump it my preferred way to
> solve my problem. tcpreplay only reads the packets and throw them to the
> network, while, with tcpdump, I can use the powerfull filtering capabilities
> which are allready implemented
Then perhaps the correct answer is to use tcpdump to do the filtering
and pipe its output to another program to send the packets, rather than
sticking the sending capabilities into tcpdump. Pipes, filters, tools,
and all that....
E.g.:
tcpdump -r capture -w - {filter expression} | \
tcpreplay -
or add the ability to filter the input packets to tcpreplay (the
"powerful filtering capabilities" are part of libpcap, not tcpdump, so
they're available to all programs that use libpcap to capture packets
*or* read capture files).
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
