Re: OPNET - End user experience - Analyzing TCP packets

It could do differencial tests between icmp and tcp processing.
Pings are usually answered with very little/no cpu involvement, and
would give a baseline to compare to.
-Carlos

Sirhan Khan @ 31/07/2013 04:59 -0300 dixit:
> Hi Chad
>
> sequence numbers + latency would not give us an idea of end user TCP stack
> process time.
>
>
> On Wed, Jul 31, 2013 at 9:39 AM, Chad Bunker <cbunker_at_gmail.com> wrote:
>
>> sequence numbers + latency?
>>
>>
>> On Wed, Jul 31, 2013 at 3:06 AM, Sirhan Khan <khan.sirhan_at_gmail.com>wrote:
>>
>>> Hi Guys
>>>
>>> Just a quick question, I just left a meeting now and have been monitoring
>>> packets on wireshark for some time but don't see how this is possible.
>>>
>>> Topology:
>>>
>>> USER -- LAN -- WAN -- OPNET PROBE -- PE -- DATA CENTRE
>>>
>>> Looking at the position of the OPNET probe, can the opnet device look at
>>> the processing time of the USER machine ( how long the client machine's
>>> processor takes to process the tcp packet ).
>>>
>>> According to OPNET, this is possible by looking at certain variables on
>>> the
>>> packet header. Is this possible?
>>>
>>> Regards
>>> Sirhan
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>

-- 
Carlos G Mendioroz  <tron_at_huapi.ba.ar>  LW7 EQI  Argentina
Blogs and organic groups at http://www.ccie.net