All of lore.kernel.org
 help / color / mirror / Atom feed
From: Friedrich Lobenstock <fl@fl.priv.at>
To: netfilter-devel@lists.netfilter.org
Cc: Harald Welte <laforge@netfilter.org>
Subject: Re: extra/pptp-conntrack-nat.patch
Date: Fri, 11 Apr 2003 12:48:40 +0200	[thread overview]
Message-ID: <3E969D88.4070005@fl.priv.at> (raw)
In-Reply-To: <Pine.GSO.4.03.10304101552590.4253-100000@shemp.vdata.com>

Jeff Hall wrote:
> On Thu, 10 Apr 2003, Friedrich Lobenstock wrote:
>> May I recall that I really have to remove the // to get it running.
>> 
>> /* track caller id inside control connection, call expect_related */
>> static int
>> conntrack_pptp_help(const struct iphdr *iph, size_t len,
>>                      struct ip_conntrack *ct, enum ip_conntrack_info ctinfo)
>> 
>> { ...
>> 
>>          /* checksum invalid? */
>>          if (tcp_v4_check(tcph, tcplen, iph->saddr, iph->daddr,
>>                          csum_partial((char *) tcph, tcplen, 0))) {
>>                  printk(KERN_NOTICE __FILE__ ": bad csum\n");
>> //             return NF_ACCEPT;
>>          }
>> 
>> If I take a look at the cvs version of the patch there's a comment
>> above the // line that says that w2k servers send out false csums.
>> 
>> So do I understand this correct that if I remove the //, the pptp
>> contrack module actually is more RFC conform than before? Or is
>> it just the other way round? 
>
> If you remove the comment and include the line "return NF_ACCEPT", then any
> packet with an invalid checksum is NOT processed by the PPTP helper function.
> With the line commented out the incorrect checksum is ignored and the packet
> is processed by the rest of the PPTP helper function. Why this solved your
> problem I can't say.

I don't know either. Because of this I ask the author of this module to
make this an option to the module, so I do not have to create two different
versions of devil linux to support both possibilities.

-- 
MfG / Regards
Friedrich Lobenstock

  reply	other threads:[~2003-04-11 10:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.03.10304092023000.11290-100000@shemp.vdata.com>
2003-04-10 13:28 ` extra/pptp-conntrack-nat.patch Friedrich Lobenstock
2003-04-10 20:11   ` extra/pptp-conntrack-nat.patch Jeff Hall
2003-04-11 10:48     ` Friedrich Lobenstock [this message]
2003-04-11 11:09       ` extra/pptp-conntrack-nat.patch Ilguiz Latypov
2003-04-11 16:40         ` extra/pptp-conntrack-nat.patch Friedrich Lobenstock
2003-04-11 17:00           ` extra/pptp-conntrack-nat.patch Martin Josefsson
2003-04-11 19:42             ` extra/pptp-conntrack-nat.patch Martin Josefsson
2003-04-11 21:08               ` extra/pptp-conntrack-nat.patch Friedrich Lobenstock
2003-04-11 19:12           ` extra/pptp-conntrack-nat.patch Ilguiz Latypov
2003-04-11 21:26             ` extra/pptp-conntrack-nat.patch Friedrich Lobenstock
     [not found] <3E8832B4.8030901@fl.priv.at>
2003-03-31 12:31 ` extra/pptp-conntrack-nat.patch Harald Welte
2003-03-31 12:44   ` extra/pptp-conntrack-nat.patch Friedrich Lobenstock
2003-03-31 13:07     ` extra/pptp-conntrack-nat.patch Harald Welte
2003-04-01 19:37       ` extra/pptp-conntrack-nat.patch Friedrich Lobenstock

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=3E969D88.4070005@fl.priv.at \
    --to=fl@fl.priv.at \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.