Hey Clifford,

Can you send me a pcap?  Hard to diagnose the problem without being
able to reproduce it.

Thanks,
Aaron

On Feb 7, 2008 1:27 AM, Clifford Bailey <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm a new user of tcpreplay. I am trying to use it to test a firewall, much 
> as in the example you have on the site. The problem I have is that tcpprep 
> seems to be classifying my traffic the wrong way round consistently. I tried 
> just swapping over the values for server and client, but tcpreplay then sends 
> out the client traffic after the server traffic, so I get my ack before my 
> request, which the firewall doesn't like very much! I am using the following 
> script to generate the pcap file:
>
> tcpprep -i ${CAP_UNICAST} -p -o ${CACHE}
>
> # rewrite -- works but server and client the wrong way round
> tcprewrite -c ${CACHE} --enet-dmac=${FW_MAC_EXT},${FW_MAC_INT} 
> --enet-smac=${SERVER_MAC},${CLIENT_MAC} --endpoints=${SERVER_IP}:${CLIENT_IP} 
> -i ${CAP_UNICAST} -o ${PCAPOUT}
>
> If I then view the pcap file created, the macs assigned are all the wrong way 
> round. I tried just swapping over the macs, which works to a point, in that 
> the pcap file then looks right, but it seems that because the traffic has 
> been classified as server/client tcpreplay sends it in a specific order, 
> rather than the order on the file.
>
> (I run replay with the command: tcpreplay -M 100 -l 0 -i $SERVER_INT -I 
> $CLIENT_INT -c $CACHE $PCAPOUT). I've read and re-read the man pages, and as 
> far as I can see this is correct, however I could well have made a mistake. 
> Is it glaringly obvious to anyone what I've done wrong?
> Thanks,
>
> Cliff.

-------------------------------------------------------------------------
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

Reply via email to