All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Craig <philipc@snapgear.com>
To: "Ehrhardt René" <r.ehrhardt@eviatec.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: pptp-conntrack-nat and kernel 2.6.7
Date: Fri, 06 Aug 2004 10:58:42 +1000	[thread overview]
Message-ID: <4112D7C2.8000105@snapgear.com> (raw)
In-Reply-To: <94F30CDB27E39547A10F4E71E9AF114B2DEE8A@dlb-dc02.intern-eviatec.de>

Ehrhardt René wrote:
> i´m running a debian sarge beta 4 box with iptables 1.2.10, I have to install the pptp-conntrack-nat patch. 
> 
> I have the newest CVS build of pom

You should be using pomng, not pom (which is no longer maintained).

> Testing... pptp-conntrack-nat.patch NOT APPLIED (1 missing files) The extra/pptp-conntrack-nat patch:
> 
>    Author: Harald Welte <laforge@netfilter.org>
> 
>    Status: Beta
> 
> ...
> 
> ...
> 
> ...
> 
> Testing patch extra/pptp-conntrack-nat.patch...
> 
> Warning - no help text file could be found in either /usr/src/linux/net/ipv4/netfilter/Config.help
> 
> or /usr/src/linux/Documentation/Configure.help
> 
> grep: /usr/src/linux/net/ipv4/netfilter/Config.in: Datei oder Verzeichnis nicht gefunden Could not find place to slot in Config.in line
> 
>  
> 
> What does this mean?? 

It means that the patch is trying to apply to the 2.4.x style config
files, but you are using a 2.6.x kernel which does not have these.

> Is there any way to get this thing working?

Unfortunately no.  Noone has ported the pptp patch to 2.6.x yet.

-- 
Philip Craig - SnapGear, A CyberGuard Company - http://www.SnapGear.com



      reply	other threads:[~2004-08-06  0:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 11:54 pptp-conntrack-nat and kernel 2.6.7 Ehrhardt René
2004-08-06  0:58 ` Philip Craig [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=4112D7C2.8000105@snapgear.com \
    --to=philipc@snapgear.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=r.ehrhardt@eviatec.de \
    /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.