Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Dennis J." <dennisml@conversis.de>
To: "Покотиленко Костик" <casper@meteor.dp.ua>
Cc: netfilter@vger.kernel.org
Subject: Re: NOTRACK not working
Date: Tue, 26 Jan 2010 21:15:50 +0100	[thread overview]
Message-ID: <4B5F4D76.200@conversis.de> (raw)
In-Reply-To: <1264531798.4004.67.camel@casper.meteor.dp.ua>

On 01/26/2010 07:49 PM, Покотиленко Костик wrote:
> В Вто, 26/01/2010 в 19:38 +0100, Dennis J. пишет:
>> Hi,
>> For a while now I excluded two IPs on my firewall from connection tracking
>> which works very well. Now I tried adding another IP but that doesn't seem
>> to work. I added the following rules:
>>
>> iptables -t raw -A PREROUTING -s 192.168.10.10 -j NOTRACK
>> iptables -t raw -A PREROUTING -d 192.168.10.10 -j NOTRACK
>>
>> Yet when I look in /proc/net/ip_conntrack I still see 192.168.10.10 using
>> up most of the entries.
>> Is there something else that needs to be done to exclude this IP completely
>> from the connection tracking table?
>
> Probably conntrack has seen packets from this IP before you added those
> rules, they will remain until connection is "closed" and/or timeout
> occurs. Quick hack is to do "conntrack -F; conntrack -F expect".
>

Makes sense. Where can I find the conntrack command? This is a regular 
centos 5 system but I can't find any packages that contain this command.

Regards,
   Dennis

  reply	other threads:[~2010-01-26 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 18:38 NOTRACK not working Dennis J.
2010-01-26 18:49 ` Покотиленко Костик
2010-01-26 20:15   ` Dennis J. [this message]
2010-01-26 20:35     ` Покотиленко Костик
2010-01-27 15:47       ` Dennis J.
2010-01-26 20:43     ` Покотиленко Костик
2010-01-26 18:57 ` Jozsef Kadlecsik
2010-01-26 19:01 ` Steven Kath

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=4B5F4D76.200@conversis.de \
    --to=dennisml@conversis.de \
    --cc=casper@meteor.dp.ua \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox