Linux Netfilter discussions
 help / color / mirror / Atom feed
From: fming@borderware.com
To: netfilter <netfilter@lists.netfilter.org>,
	Antony Stone <Antony@Soft-Solutions.co.uk>
Subject: Re: selective connection tracking?
Date: Wed, 12 May 2004 14:50:16 -0400 (EDT)	[thread overview]
Message-ID: <1084387816.40a271e8dee50@mail.borderware.com> (raw)
In-Reply-To: <200405121858.30104.Antony@Soft-Solutions.co.uk>

Quoting Antony Stone <Antony@Soft-Solutions.co.uk>:
> 
> 
> > Looks to me once I loaded the conn_track modules, everything was
> tracked.
> 
> Correct.
> 
> > Is there a way I can specify, for example, that I only want http to
> be
> > tracked? All other traffic will be dropped anyway, tracked or not.
> 
> If it's going to be dropped, there won't be a connection, therefore the
> other 
> traffic won't consume any connection tracking resources.

I believe the connection tracking is useful for the FORWARD filter, however, 
for the INPUT filter, its the job of Linux TCP/UDP to take care of those 
things. Keep another set of stat below the IP layer does not make sense to me. 
The upper layer protocol has a better knowledge of the connection state than 
the conn_track anyway.

> 
> Regards,
> 
> Antony.
> 
> -- 
> How I want a drink, alcoholic of course, after the heavy chapters
> involving 
> quantum mechanics.
> 
>  - 3.14159265358979
> 
>                                                      Please reply to the
> list;
>                                                            please don't
> CC me.
> 
> 


  reply	other threads:[~2004-05-12 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12 17:42 selective connection tracking? fming
2004-05-12 17:53 ` clister
2004-05-12 18:05   ` Antony Stone
2004-05-12 17:58 ` Antony Stone
2004-05-12 18:50   ` fming [this message]
2004-05-13 16:28 ` Michael Gale
2004-05-13 16:35   ` Michael Gale

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=1084387816.40a271e8dee50@mail.borderware.com \
    --to=fming@borderware.com \
    --cc=Antony@Soft-Solutions.co.uk \
    --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