Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Stephen Jones <hivemynd@hivemynd.net>
To: Ali <ali@infomed.sld.cu>
Cc: netfilter@lists.netfilter.org
Subject: Re: pptp conntrack patch missing argument
Date: Sun, 12 Dec 2004 00:32:11 -0600	[thread overview]
Message-ID: <41BBE5EB.50603@hivemynd.net> (raw)
In-Reply-To: <1102718548.41ba265486969@webmail.sld.cu>

Hi Ali,

Thanks for the info!  I should be able to give this a spin, against a 
2.4.28 source tree, and test it in the next week or so!  Thanks again 
for pointing this out.  I didn't think of scanning the rest of the 
sources for calls to the same function in other sources, very good plan!

Best regards,

SJ

PS: I CC'd the netfilter list with your suggestion in the hopes that it 
does indeed fix the problem with the latest pom-ng release.

Ali wrote:

>Hi Stephen,
>
>While compiling a 2.4.27 kernel i suffered of the same problem you reported
>on the netfilter list and as you, searching on the web don't provide me any
>solution, but digging in the source i found that all calls to ip_nat_used_tuple
>in net/ipv4/netfilter/ip_nat_proto_* used the same convention:
>  if (!ip_nat_used_tuple(tuple, conntrack, maniptype, range->flags))
>changing line 108 in ip_nat_proto_gre.c to that make it compile cleanly. So far
>i haven't yet tested if it works ok but thougth that you may be interested :).
>
>Best regards,
>  Ali
>
>Pd: i'm not in the netfilter list (found your message in google) that's the reason to
>me writing you directly
>
>
>-------------------------------------------------
>Este mensaje fue enviado usando el servicio de correo en web de Infomed
>http://webmail.sld.cu
>
>
>  
>




       reply	other threads:[~2004-12-12  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1102718548.41ba265486969@webmail.sld.cu>
2004-12-12  6:32 ` Stephen Jones [this message]
     [not found] <1102910163.41bd12d377f0a@webmail.sld.cu>
2004-12-13  4:28 ` pptp conntrack patch missing argument Stephen Jones

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=41BBE5EB.50603@hivemynd.net \
    --to=hivemynd@hivemynd.net \
    --cc=ali@infomed.sld.cu \
    --cc=netfilter@lists.netfilter.org \
    /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