All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Feng <rfeng@wurldtech.com>
To: netfilter@vger.kernel.org
Subject: conntrack-tools 0.9.14 can not block the connection
Date: Thu, 6 May 2010 16:51:40 -0700	[thread overview]
Message-ID: <201005061651.40203.rfeng@wurldtech.com> (raw)

Hi,

I am using Linux 2.6.29. I have the problem for using 'conntrack' 
(version:0.9.14) to block the traffic.
Using the following command as example:
  conntrack -D -s 1.1.1.1 -d 2.2.2.2
After execution, it appears the connection info was deleted -
  conntrack -L | grep 1.1.1.1 -- shows the entry was deleted.

However, the connection is still active - is this the correct behaviour? 

From the documentation (from conntrack-tools.netfilter.org), somewhere it says 
that "have to set /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal to 
zero".There is simply no 'netfilter' folder under my 
folder '/proc/sys/net/ipv4'. Is this the problem? How could I fix it?


Thanks,
Richard Feng

             reply	other threads:[~2010-05-06 23:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 23:51 Richard Feng [this message]
2010-05-07  7:55 ` conntrack-tools 0.9.14 can not block the connection Jan Engelhardt
2010-05-07  8:49   ` Rob Sterenborg
2010-05-07  9:50     ` Jan Engelhardt
2010-05-07 16:17   ` Richard Feng
2010-05-07 16:27     ` Jan Engelhardt
2010-05-07 19:13       ` Pablo Neira Ayuso
2010-05-07 19:14         ` Pablo Neira Ayuso
2010-05-07 19:46           ` Jan Engelhardt
2010-05-07 20:13             ` Pascal Hambourg
2010-05-08 20:33               ` Jozsef Kadlecsik
2010-05-08 20:39                 ` Jan Engelhardt
2010-05-10 11:11                   ` Pascal Hambourg
2010-05-09 23:16                 ` Pablo Neira Ayuso
2010-05-07  9:57 ` Pascal Hambourg
2010-05-07 16:22   ` Richard Feng
2010-05-07 18:51     ` Pascal Hambourg
2010-05-07 19:04       ` Richard Feng

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=201005061651.40203.rfeng@wurldtech.com \
    --to=rfeng@wurldtech.com \
    --cc=netfilter@vger.kernel.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.