Ethereal-users: [Ethereal-users] Why capture at multiple places of TCP Stream?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Anup Patel <bugzbunny@xxxxxxxxx>
Date: Fri, 11 Mar 2005 11:07:33 -0500
Hello,

I am trying to figure out why would one want to capture at multiple
places of a TCP Stream? Below is the scenario.

Originator of a session ->(Router) intermediate LAN segment ->(Router)
LAN where the  Application resides on a server (Assume 3 hops)

Is there a need to run a capture at each of these locations, meaning
on the request originator, intermediate LAN where capture will be done
by source IP address of the originator and next to the application
server again capture done by the source ip address of the originator.
Capture at all three places and than combining those captures?
Shouldn't capture at the originator tell me latency, packet loss,
etc..? What additional data can I get by doing multiple captures?

I am looking to timestamp my captures with GPS if I were to do
multiple captures so it is easier to combine the captures based on
timestamps. Should I even bother?

I am in a bit of technical debate with my colleague who wants to
capture at all location.

What am I missing? Any help will be greatly appreciated. 

Thanks a Lot,
Anup