Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Leonardo Rodrigues Magalhães" <leolistas@solucoesip.net>
To: netfilter ML <netfilter@lists.samba.org>
Subject: question on ip_conntrack log entries and behavior
Date: Thu, 20 Mar 2003 10:22:09 -0300	[thread overview]
Message-ID: <00d101c2eee3$b64a6170$3201a8c0@ESTACAO> (raw)

[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]


    Hello Guys,

    I got a firewall running kernel 2.4.20 with some p-o-m patches,
including tcp-window-tracking which allows me change timeout stuff in
runtime.

    Well ...... my /proc/net/ip_conntrack log is PLENTY of CLOSE
connections, just like:

tcp 6 386819 CLOSE src=192.168.1.2 dst=200.220.254.156 sport=47617 dport=80
src=200.220.254.156 dst=200.241.238.254 sport=80 dport=47617 use=1
tcp 6 21172 CLOSE src=192.168.1.2 dst=200.208.28.191 sport=41786 dport=80
src=200.208.28.191 dst=200.241.238.254 sport=80 dport=41786 use=1
tcp 6 340817 CLOSE src=192.168.1.2 dst=216.136.226.78 sport=60094 dport=80
src=216.136.226.78 dst=200.241.238.254 sport=80 dport=60094 use=1
tcp 6 87811 CLOSE src=192.168.1.2 dst=200.208.28.224 sport=58142 dport=80
src=200.208.28.224 dst=200.241.238.254 sport=80 dport=58142 use=1
tcp 6 399392 CLOSE src=192.168.1.2 dst=200.220.254.156 sport=52780 dport=80
src=200.220.254.156 dst=200.241.238.254 sport=80 dport=52780 use=1
tcp 6 379271 CLOSE src=192.168.1.2 dst=64.191.34.195 sport=44823 dport=80
src=64.191.34.195 dst=200.241.238.254 sport=80 dport=44823 use=1

    These entries seems to be NOT cleaned after timeout, which are:

[root@firewall netfilter]# pwd
/proc/sys/net/ipv4/netfilter
[root@firewall netfilter]# cat ip_conntrack_tcp_timeout_close
10
[root@firewall netfilter]# cat ip_conntrack_tcp_timeout_close_wait
300

    These timeout values are changed in the very beggining of script
firewall.

    Seems to me that connections are not being erased because i got NO night
traffic and amount of connections seems to be stable ( please check MRTG
graph attached ).

    And, the most strange at all, I got exactly same configuration ( kernel
version, kernel patchs, iptables 1.2.7a and firewall script ) running in
other machines that do NOT shows this problem ....

    Have you ever seen something like this ? Any hint ? Any configuration
change ? Any idea ? :)


    Sincerily and thanks for your replies,
    Leonardo Rodrigues

[-- Attachment #2: conexoes-day.png --]
[-- Type: image/png, Size: 2868 bytes --]

             reply	other threads:[~2003-03-20 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 13:22 Leonardo Rodrigues Magalhães [this message]
2003-03-20 14:04 ` question on ip_conntrack log entries and behavior Jozsef Kadlecsik
2003-03-21 11:32   ` Leonardo Rodrigues Magalhaes

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='00d101c2eee3$b64a6170$3201a8c0@ESTACAO' \
    --to=leolistas@solucoesip.net \
    --cc=netfilter@lists.samba.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