All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Deti Fliegl <deti@fliegl.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: problem with conntrack utility and kernel 2.6.14
Date: Mon, 31 Oct 2005 05:41:59 +0100	[thread overview]
Message-ID: <4365A097.1080001@eurodev.net> (raw)
In-Reply-To: <436398C7.4070402@fliegl.de>

Hi,

JFYI, I just commited the following changes to libconntrack_netfilter:

o Replace misleading flag NFCT_ANY_GROUP by NFCT_ALL_GROUPS
o Update test file to use NFCT_ALL_GROUPS
o Add missing check of CTA_PROTOINFO_TCP that resulted in a segfault in
conjuction with events
o Fix ICMP conntracks output
o Add missing prototype definition of nfct_default_expect_display_id in
libnetfilter_conntrack.h

and the following to conntrack:

o Replace misleading message "Not enough memory" by "Can't open handler"
o New option -i for expectation dumping: conntrack -L expect [-i]
o sed 's/VERSION/CONNTRACK_VERSION/g'
o Fix nfct_open flags, now uses NFCT_ALL_GROUPS when needed
o Bumped version to 0.94

AFAIK these fix the problems concerned with the dumping. The problem 
wasn't 64 bits arch specific at all, actually the matter was that I 
required some fast hardware to reproduce them that I don't have. Thanks 
to Deti Fiegl for providing me such fast hardware via SSH to reproduce 
the bugs ;)

I've been giving some testing to the conntrack tool and seems to work 
fine under big stress situation. If you spot any other bug, please let 
me know. I'm willing to do the first 1.0 official as soon as people 
don't complain about bugs.

-- 
Pablo

  reply	other threads:[~2005-10-31  4:41 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28  9:08 problem with conntrack utility and kernel 2.6.14 Deti Fliegl
2005-10-28  9:26 ` Pablo Neira
2005-10-28  9:26   ` Deti Fliegl
2005-10-28 10:01 ` Pablo Neira
2005-10-28 11:48   ` Deti Fliegl
2005-10-28 19:22     ` Pablo Neira
2005-10-28 19:53       ` Deti Fliegl
2005-10-29 13:06         ` Pablo Neira
2005-10-29 15:34           ` Deti Fliegl
2005-10-29 18:35             ` Pablo Neira
2005-10-29 15:44           ` Deti Fliegl
2005-10-31  4:41             ` Pablo Neira [this message]
2005-10-31  8:28               ` Krzysztof Oledzki
2005-11-01  1:09                 ` Pablo Neira
2005-11-01 10:29                   ` Krzysztof Oledzki
2005-11-01 13:55                     ` Pablo Neira
2005-11-01 15:17                       ` Krzysztof Oledzki
2005-11-01 16:39                         ` Pablo Neira
2005-11-01 18:49                           ` Krzysztof Oledzki
2005-11-01 19:27                             ` Pablo Neira
2005-11-01 19:39                               ` Krzysztof Oledzki
2005-11-01 20:07                             ` Pablo Neira
2005-11-01 20:21                               ` Krzysztof Oledzki
2005-11-02 16:04                                 ` Pablo Neira
2005-10-31 11:10               ` Deti Fliegl
2005-12-04  2:14         ` Pablo Neira Ayuso
2005-12-04 16:09           ` Patrick McHardy
2005-12-04 16:53             ` Deti Fliegl
2005-12-04 17:10           ` Yasuyuki KOZAKAI
2005-12-04 18:44             ` Deti Fliegl
2005-12-04 19:56               ` Patrick McHardy
2005-12-05  5:51                 ` Yasuyuki KOZAKAI
2005-12-15 12:49               ` problem with conntrack utility and kernel 2.6.14 - still with 2.6.14.4 Deti Fliegl
2005-12-15 13:05                 ` Pablo Neira Ayuso
2005-12-15 17:21                 ` Krzysztof Oledzki
     [not found]           ` <200512041004.37192.romary@nikoon.com>
2005-12-04 20:04             ` Major problem with conntrack utility and kernel 2.6.14.3 Patrick McHardy
2005-12-04 23:08               ` Deti Fliegl
2005-12-05 10:24               ` Krzysztof Oledzki
2005-12-05 15:17                 ` Patrick McHardy
2005-10-28 13:39   ` problem with conntrack utility and kernel 2.6.14 Deti Fliegl

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=4365A097.1080001@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=deti@fliegl.de \
    --cc=netfilter-devel@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.