From: "Venkatesh. K" <venkatesh@cbayscribe.com>
To: Daniel Chemko <dchemko@smgtec.com>,
netfilter@lists.netfilter.org,
Fernando Barrocal <fbarrocal@uol.com.br>
Subject: Re: iptables1.2.7 + pptp + rh9
Date: Wed, 22 Oct 2003 06:30:13 +0530 [thread overview]
Message-ID: <009501c39837$e1883850$2800a8c0@karu> (raw)
In-Reply-To: 6.0.0.22.0.20031021210350.01b66818@pop3.uol.com.br
----- Original Message -----
From: "Fernando Barrocal" <fbarrocal@uol.com.br>
To: "Daniel Chemko" <dchemko@smgtec.com>; <netfilter@lists.netfilter.org>
Sent: Wednesday, October 22, 2003 4:35 AM
Subject: RE: iptables1.2.7 + pptp + rh9
>
> Let me ask another question ... a newbie one ...
>
> Is that order correct ?
>
> - apply pptp patch
> - compile iptables
> - compile kernel (config, dep, clean, image, modules)
>
Apply patch
Compile Kernel
Compile IPtables
Venkatesh K
>
>
> At 20:06 21/10/2003, Daniel Chemko wrote:
> >Um, yeah. You need to compile the userspace tools against the kernel
> >that you are installing.
> >
> >-----Original Message-----
> >From: Fernando Barrocal [mailto:fbarrocal@uol.com.br]
> >Sent: Tuesday, October 21, 2003 3:00 PM
> >To: Daniel Chemko; netfilter@lists.netfilter.org
> >Subject: RE: iptables1.2.7 + pptp + rh9
> >
> >
> >Still after installing 1.2.8 it does not work. Do I need to compile ipt
> >?
> >and the kernel ?
> >
> >At 19:15 21/10/2003, Daniel Chemko wrote:
> > >Download ipt 1.2.8 or 1.2.9 if it is out.
> > >Or, use the CVS userspace
> > >
> > ># KERNEL_DIR=<yourkerneldir> make
> > ># make install
> > >
> > >You might want to change the destination directories in the Makefile to
> > >conform to the Redhat deployment layout
> > >LIBDIR=/lib/
> > >MANDIR=/usr/man
> > >etc..
> > >
> > >-----Original Message-----
> > >From: Fernando Barrocal [mailto:fbarrocal@uol.com.br]
> > >Sent: Tuesday, October 21, 2003 2:04 PM
> > >To: netfilter@lists.netfilter.org
> > >Subject: iptables1.2.7 + pptp + rh9
> > >
> > >
> > >Hi,
> > >
> > >I am applying the pptp patch with patch-o-matic in my redhat 9.0.
> > >Somebody
> > >have somer step by step to patch the kernel, compile the iptable
> > >userspace
> > >and compile the kernel to accept DNAT ?
> > >
> > >Thanks in advance
> > >
> > >Fernando Barrocal
>
>
>
>
next prev parent reply other threads:[~2003-10-22 1:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 22:06 iptables1.2.7 + pptp + rh9 Daniel Chemko
[not found] ` <7C9884991ADAE0479C14F10C858BCDF52E375B@alderaan.smgtec.com >
2003-10-21 23:05 ` Fernando Barrocal
2003-10-22 1:00 ` Venkatesh. K [this message]
2003-10-22 19:55 ` Arnt Karlsen
2003-10-23 11:45 ` Arnt Karlsen
2003-10-25 13:40 ` SO HOW! iptables: invalid argument John Paul
2003-10-25 13:55 ` Alistair Tonner
2003-10-25 14:11 ` John Paul
2003-10-25 14:13 ` John Paul
2003-10-25 15:16 ` Alistair Tonner
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 21:15 iptables1.2.7 + pptp + rh9 Daniel Chemko
[not found] ` <7C9884991ADAE0479C14F10C858BCDF5122E76@alderaan.smgtec.com >
2003-10-21 21:59 ` Fernando Barrocal
2003-10-21 23:50 ` Evan Davies
2003-10-22 13:09 ` Fernando Barrocal
2003-10-21 21:03 Fernando Barrocal
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='009501c39837$e1883850$2800a8c0@karu' \
--to=venkatesh@cbayscribe.com \
--cc=dchemko@smgtec.com \
--cc=fbarrocal@uol.com.br \
--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