Good luck!

On Sun, Apr 8, 2012 at 9:31 PM, Senthil Kumar S
<senthilkuma...@sasken.com> wrote:
> Hi Aaron,
>
> Thanks. I am not opening a socket connection in the code. Infact I am a 
> tester, not a dev. My aim is, I just give some traffic to the 
> software/application developed by us.
>
> Anyway, we figured out tcpreplay cannot do a client-server communication.We 
> are going to try Tomahawk(thx to tcpreplay FAQ) and hope for the best.
>
>> If you're not able to do that on a public forum, I'm available as a 
>> consultant and I can sign an NDA >>
>
> This is completely out of my hands. I feel Sorry about it.
>
> A request, In the usage examples available in the tcpreplay, this link 
> (http://tcpreplay.synfin.net/attachment/wiki/usage/NAT-Example.gif) is not 
> working. No example diagram found.
>
> Regards,
> S. Senthil kumar
>
>
>
> -----Original Message-----
> From: Aaron Turner [mailto:synfina...@gmail.com]
> Sent: Friday, April 06, 2012 9:00 PM
> To: Main forum for tcpreplay
> Subject: Re: [Tcpreplay-users] tcpreplay Client Server communication
>
> On Fri, Apr 6, 2012 at 5:33 AM, Senthil Kumar S <senthilkuma...@sasken.com> 
> wrote:
>> Hi Aaron,
>>
>> Thanks for a brief explanation. Our aplication/software actually does not 
>> listen in any interface. Application/Software runs in centos pc as already 
>> mentioned.
>>
>> Our application/software takes the packets from the tcp/ip stack (after the 
>> packets reached the tcp/ip stack of cent-os) and then do some processing.
>>
>> Due to the confidentiality of this app/software, I am really sorry that I 
>> cannot go beyond this limit, but this is how our app/soft works.
>>
>> I suspect packets replayed through tcpreplay didn't reach the tcp/ip stack.
>>
>> Am I doing anything wrong in the modification of pcap ???
>
> The way you're describing your DUT makes me believe that you're opening a 
> standard TCP socket on both DUT interfaces.  And then you're trying to use 
> tcpreplay to send client traffic to one socket/interface and server traffic 
> to the other.  As I explained in an earlier thread, you can't use tcpreplay 
> to send traffic to DUT's which listen on a standard TCP socket.
>
> Ie: if you're doing something like this in your code:
>
> fd = socket(AF_INET, SOCK_STREAM, 0);
>
> then you have a 0% chance of it ever working because tcpreplay doesn't know 
> how to respond to the TCP 3 way handshake required of a real TCP/IP stack on 
> an endpoint.  Game over.
>
> If you're not doing what I've just described above, you're going to have to 
> pull back the veil of secrecy a little and explain what you are doing and how 
> your DUT works.  If you're not able to do that on a public forum, I'm 
> available as a consultant and I can sign an NDA.  If interested, email me 
> off-list and we can talk further.  But if you can't explain it any more then 
> sorry, but I won't be able to help you further.
>
> Regards,
> Aaron
>
>
> --
> Aaron Turner
> http://synfin.net/         Twitter: @synfinatic http://tcpreplay.synfin.net/ 
> - Pcap editing and replay tools for Unix & Windows Those who would give up 
> essential Liberty, to purchase a little temporary Safety, deserve neither 
> Liberty nor Safety.
>    -- Benjamin Franklin
> "carpe diem quam minimum credula postero"
>
> ------------------------------------------------------------------------------
> 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
>
> SASKEN BUSINESS DISCLAIMER: This message may contain confidential, 
> proprietary or legally privileged information. In case you are not the 
> original intended Recipient of the message, you must not, directly or 
> indirectly, use, disclose, distribute, print, or copy any part of this 
> message and you are requested to delete it and inform the sender. Any views 
> expressed in this message are those of the individual sender unless otherwise 
> stated. Nothing contained in this message shall be construed as an offer or 
> acceptance of any offer by Sasken Communication Technologies Limited 
> ("Sasken") unless sent with that express intent and with due authority of 
> Sasken. Sasken has taken enough precautions to prevent the spread of viruses. 
> However the company accepts no liability for any damage caused by any virus 
> transmitted by this email.
> Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html
>
> ------------------------------------------------------------------------------
> 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



-- 
Aaron Turner
http://synfin.net/         Twitter: @synfinatic
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
    -- Benjamin Franklin
"carpe diem quam minimum credula postero"

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

Reply via email to