From: Patrick McHardy <kaber@trash.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Andreas Jaggi <aj@open.ch>,
Jing Min Zhao <zhaojingmin@users.sourceforge.net>,
netdev@vger.kernel.org
Subject: Re: H.245v10+ support in nf_conntrack_h323?
Date: Tue, 01 Sep 2009 13:25:22 +0200 [thread overview]
Message-ID: <4A9D04A2.60307@trash.net> (raw)
In-Reply-To: <20090901100230.GA18651@sirena.org.uk>
Mark Brown wrote:
> On Tue, Sep 01, 2009 at 11:29:10AM +0200, Andreas Jaggi wrote:
>
>> The videoconferencing devices use version 10 of the H.245 protocol,
>> but nf_conntrack_h323 supports version 7 (according to the comments in
>> include/linux/nf_conntrack_h323.h).
>
>> Are there any plans to include support for version 10 (or higher) of
>> H.245 in nf_conntrack_h323?
AFAIK Jing Min isn't able to do further development of the H.323 helper.
> I'd be surprised if the H.245 version were the source of your problems
> here - the new protocol versions are backwards compatible and I don't
> remember any changes in any of the stuff that's relevant for firewall
> transit.
Good point. The helper should also log packets dropped due to parsing
errors. If you don't get any messages, I'd suggest to use the iptables
TRACE target to figure out where the packets are dropped exactly.
next prev parent reply other threads:[~2009-09-01 11:25 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 [this message]
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
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=4A9D04A2.60307@trash.net \
--to=kaber@trash.net \
--cc=aj@open.ch \
--cc=broonie@opensource.wolfsonmicro.com \
--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).