From: Patrick McHardy <kaber@trash.net>
To: Chris Rankin <rankincj@yahoo.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: H323 connection tracking in Linux 2.6.20.1
Date: Mon, 26 Feb 2007 17:54:24 +0100 [thread overview]
Message-ID: <45E310C0.7050902@trash.net> (raw)
In-Reply-To: <117085.22319.qm@web52904.mail.yahoo.com>
Chris Rankin wrote:
> I am trying the H323 connection tracking in Linux 2.6.20.1, but am getting the following errors:
>
> Feb 25 20:42:59 wellhouse kernel: nf_ct_h245: packet dropped
> Feb 25 20:43:04 wellhouse last message repeated 10 times
> Feb 25 20:43:17 wellhouse kernel: printk: 1 messages suppressed.
> Feb 25 20:43:17 wellhouse kernel: nf_ct_h245: packet dropped
> Feb 25 20:43:23 wellhouse last message repeated 2 times
> Feb 25 20:43:24 wellhouse kernel: printk: 5 messages suppressed.
> Feb 25 20:43:24 wellhouse kernel: nf_ct_h245: packet dropped
> Feb 25 20:43:44 wellhouse kernel: printk: 9 messages suppressed.
> Feb 25 20:43:44 wellhouse kernel: nf_ct_q931: decoding error: out of bound
> Feb 25 20:43:44 wellhouse kernel: nf_ct_q931: decoding error: out of bound
Please enable debugging in net/netfilter/nf_conntrack_h323_main.c
(change "#if 0" at about line 40 to "#if 1") and
net/netfilter/nf_conntrack_h323_asn1.c (change #define H323_TRACE
0 => 1) and post the output.
> I suspect that this is related to my GNU Gatekeeper 2.0.8, which I have running on my firewall
> machine. At the moment, the only way that I have managed to make a H323 connection has been to
> disable H245 in Ekiga. However, I don't need the firewall rule to allow the UDP traffic explicitly
> any more.
>
> Cheers,
> Chris
>
> P.S. Removing the nf_conntrack_h323 module quickly kills my machine.
Please try to capure the oops and post it.
next prev parent reply other threads:[~2007-02-26 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 20:56 H323 connection tracking in Linux 2.6.20.1 Chris Rankin
2007-02-26 16:54 ` Patrick McHardy [this message]
2007-02-26 17:00 ` Jing Min Zhao
2007-02-26 21:02 ` Chris Rankin
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=45E310C0.7050902@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rankincj@yahoo.com \
/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.