All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: delete NAT conntrack entry.
Date: Thu, 10 May 2007 12:16:55 -0400	[thread overview]
Message-ID: <20070510161655.GA29151@animx.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0705101442020.32349@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
> 
> On May 10 2007 07:14, Wakko Warner wrote:
> >
> >If it were possible that when a rule like that is deleted, all
> >active conntrack entries that this rule causes would be removed.
> 
> Problem 1: We would have to record in a ct entry what rule caused
> the ct to come alive. What if we have an empty ruleset? Conntracking
> still runs even when no iptables rules are in position.

I figured something like that would be required.  I do realize that
conntrack tracks connections regardless of iptable rules.

> Problem 2: If I wanted to move a rule inside a chain,
> deleting/reinserting it would kill the ct entry and - given some
> ruleset* (there are many more that would apply) - stops all
> connections immediately.
> 
>   -P INPUT DROP
>   -A INPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT
>   -A INPUT -m conntrack --ctstate NEW -p tcp --syn -j ACCEPT

I understood this before I wrote it.  How often does one move things around
in their firewall (after their experiemental stage)?

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


      reply	other threads:[~2007-05-10 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  7:10 delete NAT conntrack entry ???
2007-05-10  9:52 ` Jan Engelhardt
2007-05-10 11:14   ` Wakko Warner
2007-05-10 12:48     ` Jan Engelhardt
2007-05-10 16:16       ` Wakko Warner [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=20070510161655.GA29151@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=jengelh@linux01.gwdg.de \
    --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.