On Fri, May 05, 2017 at 08:55:12AM +0800, gfree.wind@xxxxxxxxxxx wrote:
> diff --git a/net/ipv4/netfilter/nf_nat_h323.c b/net/ipv4/netfilter/nf_nat_h323.c
> index 346e764..ce2095c 100644
> --- a/net/ipv4/netfilter/nf_nat_h323.c
> +++ b/net/ipv4/netfilter/nf_nat_h323.c
> @@ -21,6 +21,26 @@
> #include <linux/netfilter/nf_conntrack_h323.h>
>
> /****************************************************************************/
> +static void ip_nat_q931_expect(struct nf_conn *new,
> + struct nf_conntrack_expect *this);
> +static void ip_nat_callforwarding_expect(struct nf_conn *new,
> + struct nf_conntrack_expect *this);
> +
> +static struct nf_ct_nat_helper q931_nat = {
> + .name = "Q.931",
> + .expectfn = ip_nat_q931_expect,
> +};
> +
> +static struct nf_ct_nat_helper callforwarding_nat = {
> + .name = "callforwarding",
> + .expectfn = ip_nat_callforwarding_expect,
> +};
Almost there...
> +static struct nf_ct_nat_helper follow_master_nat = {
> + .name = "h323-nat-follow-master",
This is a new symbol. There was no "h323-nat-follow-master" before
this patch, and this is exposed to userspace.
This should be "nat-follow-master" instead, so you need a way to
register this for several helpers that support this.
Probably you need a type field, eg.
static struct nf_ct_nat_helper h323_follow_master_nat = {
.type = NF_CT_HELPER_H323,
.name = "nat-follow-master",
...
};
So we can keep using "nat-follow-master" from different helpers, as it
happens currently. This should also allow us to validate if someone
wants to attach a expectfn symbol that is not support by the helper.
We need a way to relate the helper itself with this new
nf_ct_nat_helper structure that doesn't exist in the code yet.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
