From: Marco Shaw <marco@nbnet.nb.ca>
To: netfilter@lists.netfilter.org
Subject: Re: TWO ROUTING
Date: Wed, 19 Nov 2003 19:58:39 -0400 [thread overview]
Message-ID: <1069286319.8297.17.camel@rhelas3> (raw)
In-Reply-To: <200311202234.hAKMYY723743@onyx.rockstone.co.uk>
> > There was talk before about using CONNTRACK and marking packets on the list
> > before.. I think this is the solution but I didn't see a successful
> > response..
>
> You can MARK packets on their way through netfilter, and do various
> interesting and possibly useful things to the packet on the basis of the mark
> which was assigned, however I do not think there is any way of identifying
> the packets which come in later as replies to these, and thereby doing
> anything based on the mark which was assigned to the first packet on its way
> through.
Something I'm working on (or at least thinking really hard about) is a
user-space Perl script that will (somehow) record sequence and
acknowledgment numbers for outgoing packets, then possibly act on the
returning packets depending on the ack and seq numbers found.
Am I way off, or would this help/apply here?
Marco
next prev parent reply other threads:[~2003-11-19 23:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 21:44 TWO ROUTING George Vieira
2003-11-20 22:34 ` Antony Stone
2003-11-19 23:58 ` Marco Shaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 15:27 Miguel Laborde
2003-11-19 15:17 José Gomes
2003-11-19 15:24 ` Sylvain BERTRAND
2003-11-20 13:28 ` Jeffrey Laramie
2003-11-20 13:40 ` Antony Stone
2003-11-20 14:43 ` Jeffrey Laramie
2003-11-20 14:59 ` Antony Stone
2003-11-20 16:42 ` Ramin Dousti
2003-11-20 16:16 ` Jeffrey Laramie
2003-11-20 18:25 ` Ramin Dousti
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=1069286319.8297.17.camel@rhelas3 \
--to=marco@nbnet.nb.ca \
--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.