From: John <futurasci@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Strange ip_conntrack values
Date: Sun, 18 Jul 2004 15:56:55 +0200 [thread overview]
Message-ID: <ef83df6b04071806565f854eb6@mail.gmail.com> (raw)
In-Reply-To: <200407181313.47640.Antony@Soft-Solutions.co.uk>
> Tcpdump is a good packet sniffer but it does not show the data in a
> user-friendly format.
ok I've made another tcpdump for ethereal and it's ok;
I've checked and I get a lot of this scheme :
No. Time Source Destination Protocol Info
10 0.004569 24.33.232.227 mydomain TCP
1488 > http [SYN] Seq=0 Ack=0 Win=64240 Len=0 MSS=1460
11 0.004626 mydomain 24.33.232.227 TCP
http > 1488 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460
255 0.162181 24.33.232.227 mydomain TCP
1488 > http [ACK] Seq=1 Ack=1 Win=64240 Len=0
258 0.165191 24.33.232.227 mydomain TCP
1488 > http [FIN, ACK] Seq=1 Ack=1 Win=64240 Len=0
259 0.165313 mydomain 24.33.232.227 TCP
http > 1488 [FIN, ACK] Seq=1 Ack=2 Win=5840 Len=0
385 0.311935 24.33.232.227 mydomain TCP
1488 > http [ACK] Seq=2 Ack=2 Win=64240 Len=0
(this is the whole tcp stream)
for others I get the complete http exchange : get ...
is it normal ?
Ethereal is brand new for me so if you have some good tips to help me
find some interesting information ... thanks a lot
John
next prev parent reply other threads:[~2004-07-18 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 10:31 Strange ip_conntrack values John
2004-07-18 10:46 ` Antony Stone
2004-07-18 11:28 ` John
2004-07-18 12:13 ` Antony Stone
2004-07-18 13:16 ` John
2004-07-18 13:56 ` John [this message]
2004-07-18 15:17 ` Antony Stone
2004-07-18 16:19 ` John
2004-07-18 16:31 ` Antony Stone
2004-07-18 16:40 ` John
2004-07-18 17:31 ` Stephen Smoogen
-- strict thread matches above, loose matches on Subject: below --
2004-07-18 10:22 FS
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=ef83df6b04071806565f854eb6@mail.gmail.com \
--to=futurasci@gmail.com \
--cc=netfilter@lists.netfilter.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.