From: "bino-psn" <bino@indoakses-online.com>
To: netfilter@lists.netfilter.org
Subject: Re: request and reply/respon packets
Date: Wed, 3 Mar 2004 08:04:19 +0700 [thread overview]
Message-ID: <074a01c400bb$755f4a00$0103a8c0@indoaksesbno> (raw)
In-Reply-To: 200403030059.40173.Antony@Soft-Solutions.co.uk
Hi Antony,
I think you made a better description .. thx..
And .. How to implement it in side the rule ?
well ... How to let's say MARK any http-ACK coming via an interface ?
Sincerely
-bino-
----- Original Message -----
From: "Antony Stone" <Antony@Soft-Solutions.co.uk>
To: <netfilter@lists.netfilter.org>
Sent: Wednesday, March 03, 2004 8:02 AM
Subject: Re: request and reply/respon packets
> On Wednesday 03 March 2004 12:35 am, bino-psn wrote:
>
> > Dear All.
> > Is there any way to know whter a packet is a "request" or "reply/respon"
> > packets ?
>
> I'm not sure if I understand you correctly, but let me make a few
definitions
> of my own, and see if they match yours...
>
> "Requests" come from a client to a server. "Responses" and the reply
from
> the server to the client.
>
> Requests start with a SYN packet (I'm assuming we're talking about TCP
> connections here?), and responses start with a SYN/ACK packet.
Thereafter,
> all packets have ACK set.
>
> So, you can detect the first packet of a request from the fact that SYN
(only)
> is set, and you can detect the first packet of a response from that fact
that
> SYN and ACK are set.
>
> Does that help answer your question?
>
> Antony.
>
> --
> Perfection in design is achieved not when there is nothing left to add,
but
> rather when there is nothing left to take away.
>
> - Antoine de Saint-Exupery
>
> Please reply to the
list;
> please don't CC
me.
>
>
>
next prev parent reply other threads:[~2004-03-03 1:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 0:35 request and reply/respon packets bino-psn
2004-03-03 1:02 ` Antony Stone
2004-03-03 1:04 ` bino-psn [this message]
2004-03-03 8:05 ` Cedric Blancher
2004-03-03 11:14 ` Alexis
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='074a01c400bb$755f4a00$0103a8c0@indoaksesbno' \
--to=bino@indoakses-online.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox