Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "John Paul" <john@pinoylinux.sytes.net>
To: Filip Sneppe <filip.sneppe@cronos.be>
Cc: George Vieira <georgev@citadelcomputer.com.au>,
	Esteban <esteban@alstec.fr>,
	netfilter@lists.netfilter.org
Subject: Re: Nat problem with GRE (Solved!)
Date: Wed, 4 Jun 2003 18:14:17 +0800	[thread overview]
Message-ID: <003101c32a82$0ec78e20$fd00a8c0@homes> (raw)
In-Reply-To: 1054714668.454.3.camel@xbox

Thanks to those who responded to this email. What i did actually is;

1. patched the kernel with ip_pptp_* P.O.M. (KERNEL_DIR=/usr/src/linux
./runme bla bla bla)
2. recompile iptables (source)
3. recompile the kernel (make menuconfig; make dep; make bzImage, make
modules; make modules_install)
4. reboot machine

viola! works like a charm.

cheers!


----- Original Message -----
From: "Filip Sneppe" <filip.sneppe@cronos.be>
To: "John Paul" <john@pinoylinux.sytes.net>
Cc: "George Vieira" <georgev@citadelcomputer.com.au>; "Esteban"
<esteban@alstec.fr>; <netfilter@lists.netfilter.org>
Sent: Wednesday, June 04, 2003 4:17 PM
Subject: Re: Nat problem with GRE


> On Wed, 2003-06-04 at 02:10, John Paul wrote:
> > George, et al.
> >
> > I actually have the same problem. I successfully patched my
kernel(2.4.20)
> > with ip_pptp_conntrack (P-O-M) but after recompiling my kernel, iptables
> > doesnt recognize  NAT  anymore. How could this happen?
> >
> Hi,
>
> Recompile your iptables userspace program against those
> patched kernel sources & reinstall it.
>
> Regards,
> Filip
>
>



      reply	other threads:[~2003-06-04 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 22:12 Nat problem with GRE George Vieira
2003-06-04  0:10 ` John Paul
2003-06-04  8:17   ` Filip Sneppe
2003-06-04 10:14     ` John Paul [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='003101c32a82$0ec78e20$fd00a8c0@homes' \
    --to=john@pinoylinux.sytes.net \
    --cc=esteban@alstec.fr \
    --cc=filip.sneppe@cronos.be \
    --cc=georgev@citadelcomputer.com.au \
    --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