All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Jian <lark@linux.net.cn>
To: netfilter-devel@lists.netfilter.org
Subject: nfnetlink/ctnetlink from pom-ng r3884
Date: Tue, 19 Apr 2005 21:37:19 +0800	[thread overview]
Message-ID: <20050419212858.039E.LARK@linux.net.cn> (raw)

Hi,

I now use conntrack/ + libctnetlink/ + libnfnetlink/ + nfnetlink/ +
ctnetlink/ + conntrack-event-api/, all are from r3884. I also enable
CT_ACCT.

First issue is this kind of duplicate in event message

type: [NEW] src=192.168.0.27 dst=192.168.0.254 sport=22 dport=2846 src=192.168.0.254 dst=192.168.0.27 sport=2846 dport=22 status:8 timeout:432000 tcp 6 orig_packets=1 orig_bytes=0, reply_packets=268 reply_bytes=0 
type: [UPDATE] src=192.168.0.27 dst=192.168.0.254 sport=22 dport=2846 src=192.168.0.254 dst=192.168.0.27 sport=2846 dport=22 status:10 timeout:432000 orig_packets=1 orig_bytes=0, reply_packets=268 reply_bytes=0 
orig_packets=1 orig_bytes=0, reply_packets=268 reply_bytes=0 

See the second event message. account information is printed twice, that
means the netlink message has duplicated account information.


And

# ./conntrack -E conntrack
...
type: [UPDATE] src=192.168.0.254 dst=192.168.0.27 sport=4347 dport=22 src=192.168.0.27 dst=192.168.0.254 sport=22 dport=4347 timeout:120 tcp 6 orig_packets=5 orig_bytes=0, reply_packets=270 reply_bytes=0 
type: [DESTROY] src=192.168.0.254 dst=192.168.0.27 sport=4347 dport=22 src=192.168.0.27 dst=192.168.0.254 sport=22 dport=4347 orig_packets=5 orig_bytes=0, reply_packets=270 reply_bytes=0 
Segmentation fault (core dumped)

core dumps again. This time the backtrace is

[root@qos conntrack]# gdb conntrack core.31335 
Loaded symbols for extensions/libct_proto_tcp.so
#0  0x0804a258 in event_handler (sock=0xbffff700, nlh=0xbfffd760, 
    arg=0xbffff760) at src/libct.c:186
186                     while (NFA_OK(attr, attrlen)) {
(gdb) bt
#0  0x0804a258 in event_handler (sock=0xbffff700, nlh=0xbfffd760, 
    arg=0xbffff760) at src/libct.c:186
#1  0x0804b03c in list_conntrack_handler ()
#2  0x0804bceb in nfnl_listen ()
#3  0x0804b22d in ctnl_event_conntrack ()
#4  0x0804ac02 in event_conntrack () at src/libct.c:451
#5  0x08049d51 in main (argc=3, argv=0xbffff8f4) at src/conntrack.c:473
(gdb) print attr
$1 = (struct nfattr *) 0xc00063c4
(gdb) print attrlen
$2 = 1525387413

Pablo, if you need more information, just tell me.


-- 
  lark

             reply	other threads:[~2005-04-19 13:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 13:37 Wang Jian [this message]
2005-04-20  0:55 ` nfnetlink/ctnetlink from pom-ng r3884 Pablo Neira
2005-04-21  8:21   ` Wang Jian
2005-04-21 11:05     ` Pablo Neira
2005-04-21 11:29       ` Wang Jian
2005-04-20 13:41 ` Amin Azez
2005-04-20 14:17   ` Samuel Liddicott
2005-04-20 22:44   ` Pablo Neira
2005-04-21  8:07     ` Amin Azez
2005-04-21  9:25     ` extending conntrack event data Amin Azez
2005-04-21  9:49       ` Amin Azez
2005-04-21 10:14         ` Wang Jian
2005-04-21 11:04           ` Pablo Neira
2005-04-25 13:51             ` Amin Azez
2005-04-25 16:35               ` IPCT_NEW comes from was " Amin Azez
2005-04-25 16:43                 ` Amin Azez
2005-04-26 13:37                   ` BUG/CONFLICT conntrack with preroute/postroute mangle table Samuel Liddicott
2005-04-26 13:38                   ` Amin Azez
2005-05-05 11:08                     ` Amin Azez
2005-05-05 13:36                       ` RFC for fix? Was " Amin Azez
2005-05-05 16:05                       ` Pablo Neira
2005-05-09 11:11                         ` Amin Azez
2005-05-09 13:48                           ` Amin Azez
2005-04-21 11:04           ` extending conntrack event data Amin Azez

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=20050419212858.039E.LARK@linux.net.cn \
    --to=lark@linux.net.cn \
    --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.