From: Matthew Schumacher <schu@design-pt.com>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: question about pptp connection tracking
Date: Fri, 19 Dec 2003 10:38:39 -0900 [thread overview]
Message-ID: <3FE353BF.30902@design-pt.com> (raw)
In-Reply-To: <20031219082252.GB2794@obroa-skai.de.gnumonks.org>
Sorry to make you repeat this... I was mostly just wondering if this
should work or not.
To answer your questions, it's a plain 2.4.23 from kernel.org. The only
patches are the bsd-mppe patches from pptpd and pptp-conntrack-nat from
pom 20030912.
I'll give the CVS stuff a whirl.
Thanks,
schu
Harald Welte wrote:
> On Thu, Dec 18, 2003 at 04:04:56PM -0900, Matthew Schumacher wrote:
>
>>Confirmed, compiling the pptp-conntrack-nat patch as modules and not
>>loading them causes my pptpd server to work again, loading them causes
>>it to break. Since iptables doesn't seem to be dropping packets I'm
>>assuming that either (1) I have not configured iptables correctly, (2) I
>>have found a bug, or (3) this module isn't supposed to work that way.
>
>
> *sigh*. How often do I have to state this on the mailinglist:
>
> a) which exact kernel version are you running? Plain source from
> kernel.org, vendor sources?
> b) which patches [apart from pptp] from what version_ of patch-o-matic
> did you apply?
>
> Do you have any idea how much changes there are in pom and the kernel
> over time? How can I guess whcih particular combination you are
> running, and which potential bugs have been solved since then?
>
>
>>>I'm using pptp-conntrack-nat from pom 20030912.
>
>
> that's most likely the problem. please try using a more recent version
> (latest cvs snapshot or even CVS).
>
>
prev parent reply other threads:[~2003-12-19 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FE235CA.5050306@design-pt.com>
[not found] ` <3FE24EB8.4080604@design-pt.com>
2003-12-19 8:22 ` question about pptp connection tracking Harald Welte
2003-12-19 19:38 ` Matthew Schumacher [this message]
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=3FE353BF.30902@design-pt.com \
--to=schu@design-pt.com \
--cc=laforge@netfilter.org \
--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