Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Martijn Lievaart <m@rtij.nl>
To: Rohit Grover <rgrover1@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: using packet filtering to discover TCP end-to-end latency
Date: Mon, 21 May 2007 19:25:05 +0200	[thread overview]
Message-ID: <4651D5F1.2080701@rtij.nl> (raw)
In-Reply-To: <C4794891-5098-4238-BC18-2D54D2CB9859@gmail.com>

Rohit Grover wrote:
> Hello,
>
> I need to discover the TCP end-to-end latency between web clients and 
> servers transparently (i.e. without altering the clients or the 
> servers in any way). I have squid running as a proxy server on a linux 
> box, sitting between the clients and the servers. I can have the 
> clients change their proxy settings to have requests pass through 
> squid. Squid can measure latencies between itself and the web servers. 
> The problem is to measure the network latency when squid tries to 
> forward the server responses back to clients.
>
> Can packet filtering help me with this? Can I, for example, filter for 
> the client ACK of the last bit of data sent from squid back to the 
> client?
>
> Also, I still need to device a solution to measure network latency 
> experienced by the client's SYN sent to the squid box. Any ideas?
>

I would hire a packeteer for this. Expensive, but is perfect for this 
job. Otherwise, capture with wireshark (formerly Ethereal), export to 
csv, write a small program. (I don't think wireshark has a plugin for 
exactly this).

I would NOT do this with packet filtering unless I need (near) realtime 
analysis. And even then.

HTH,
M4



      reply	other threads:[~2007-05-21 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21  4:05 using packet filtering to discover TCP end-to-end latency Rohit Grover
2007-05-21 17:25 ` Martijn Lievaart [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4651D5F1.2080701@rtij.nl \
    --to=m@rtij.nl \
    --cc=netfilter@lists.netfilter.org \
    --cc=rgrover1@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox