From: Andreas Jaggi <aj@open.ch>
To: Patrick McHardy <kaber@trash.net>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jing Min Zhao <zhaojingmin@users.sourceforge.net>,
netdev@vger.kernel.org
Subject: Re: H.245v10+ support in nf_conntrack_h323?
Date: Wed, 2 Sep 2009 10:05:16 +0200 [thread overview]
Message-ID: <20090902080516.GA6766@urbino.open.ch> (raw)
In-Reply-To: <4A9D11A3.5070809@trash.net>
On Tue, Sep 01, 2009 at 02:20:51PM +0200, Patrick McHardy wrote:
> Its unfortunately necessary to drop packets in some cases after parsing
> errors when the helper might have already (partially) mangled the
> packet.
Do the helpers also mangle packets when there is no NAT involved?
(in out setup we don't use NAT, btw)
If they don't, would it be reasonable to return NF_ACCEPT when there is
no NAT. For example like in the patch below?
> You could try this patch in combination with ulogd and the pcap output
> plugin to capture the packets which are dropped by the helper for
> analysis.
Unfortunately the videoconferencing system is currently not available
for testing (and might be so for while). But I can have some tcpdumps from
both sides of the Linux Gateway from which I can extract the packets that
were dropped by the H.323 helper.
Andreas
--- a/net/netfilter/nf_conntrack_h323_main.c 2009-05-19 01:52:34.000000000 +0200
+++ b/net/netfilter/nf_conntrack_h323_main.c 2009-09-01 17:36:08.000000000 +0200
@@ -596,8 +596,12 @@
}
/* Process H.245 signal */
- if (process_h245(skb, ct, ctinfo, &data, dataoff, &mscm) < 0)
- goto drop;
+ if (process_h245(skb, ct, ctinfo, &data, dataoff, &mscm) < 0) {
+ if (ct->status & IPS_NAT_MASK)
+ goto drop;
+ else
+ break;
+ }
}
spin_unlock_bh(&nf_h323_lock);
@@ -1141,8 +1145,12 @@
}
/* Process Q.931 signal */
- if (process_q931(skb, ct, ctinfo, &data, dataoff, &q931) < 0)
- goto drop;
+ if (process_q931(skb, ct, ctinfo, &data, dataoff, &q931) < 0) {
+ if (ct->status & IPS_NAT_MASK)
+ goto drop;
+ else
+ break;
+ }
}
spin_unlock_bh(&nf_h323_lock);
@@ -1716,7 +1724,8 @@
}
/* Process RAS message */
- if (process_ras(skb, ct, ctinfo, &data, &ras) < 0)
+ if ((process_ras(skb, ct, ctinfo, &data, &ras) < 0) &&
+ (ct->status & IPS_NAT_MASK))
goto drop;
accept:
next prev parent reply other threads:[~2009-09-02 8:04 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 [this message]
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=20090902080516.GA6766@urbino.open.ch \
--to=aj@open.ch \
--cc=broonie@opensource.wolfsonmicro.com \
--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).