From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andreas Jaggi <aj@open.ch>
Cc: Patrick McHardy <kaber@trash.net>,
Jing Min Zhao <zhaojingmin@users.sourceforge.net>,
netdev@vger.kernel.org
Subject: Re: H.245v10+ support in nf_conntrack_h323?
Date: Tue, 1 Sep 2009 13:32:40 +0100 [thread overview]
Message-ID: <20090901123240.GE18651@sirena.org.uk> (raw)
In-Reply-To: <20090901121033.GA18731@urbino.open.ch>
On Tue, Sep 01, 2009 at 02:10:33PM +0200, Andreas Jaggi wrote:
> For me it looks like nf_conntrack_h323 is not only doing connection
> tracking, but also doing protocol enforcement (by dropping packets which
> do not correspond exactly to H.245v7).
> Perhaps there should be a config option to disable the protocol
> enforcement?
It's not going to be a deliberate attempt at enforcement that's the
issue here - doing any substantial enforcement would require a full
decode of the PER messages, involving having a full copy of the (rather
large) ASN.1 in the kernel. It's much more likely that a shortcut taken
in decoding the message is getting confused by something that the
endpoint is choosing to send, a brief glance at the ASN.1 code certainly
suggests that to me. Chances are it's not even a new v10 feature that's
causing the issue.
prev parent reply other threads:[~2009-09-01 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 9:29 H.245v10+ support in nf_conntrack_h323? Andreas Jaggi
2009-09-01 10:02 ` Mark Brown
2009-09-01 11:25 ` Patrick McHardy
2009-09-01 12:10 ` Andreas Jaggi
2009-09-01 12:20 ` Patrick McHardy
2009-09-02 8:05 ` Andreas Jaggi
2009-09-08 13:04 ` Andreas Jaggi
2009-09-01 12:32 ` Mark Brown [this message]
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=20090901123240.GE18651@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=aj@open.ch \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=zhaojingmin@users.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).