From: Luke Deryckx <luke@westaironline.com>
To: Boingo <b0ing0@yahoo.com>,
Netfilter list <netfilter@lists.netfilter.org>
Subject: Re: PPTP and NAT
Date: Wed, 28 Apr 2004 10:33:52 -0700 [thread overview]
Message-ID: <BCB53910.7D8C%luke@westaironline.com> (raw)
In-Reply-To: <20040428162242.44965.qmail@web80505.mail.yahoo.com>
You'll also need to recompile iptables to work properly with your newly
patched kernel. I couldn't tell from your message if you had done that or
not.
When I went through this process I had my kernel source (2.4.25) sym linked
to /usr/src/linux and my iptables source (1.2.7a) symlinked to
/usr/src/iptables when I ran the patch-o-matic. I never was sure if the
patch-o-matic actually changed the iptables source at all or not but that's
how I had it. After building and booting your new kernel, just go into
/usr/src/iptables and run a super easy make & make install.
Note though that on my Redhat 9 machine I needed to modify the Makefile and
change the install location(s) so that the newly patched iptables would
overwrite the old one, and the system could find it.
Luke
On 4/28/04 9:22 AM, "Boingo" <b0ing0@yahoo.com> wrote:
> Hi there,
> I had RH9 (default out of box) installed. I could
> do everything I needed to on iptables except get
> outside connections to our internal Win2k PPTP server
> to work. So I went and got the kernel source (2.4.26)
> from kernel.org and patched it with CVS patch-o-matic
> (CVS date: April 27, 2004). I only added patches
> related to PPTP (ipv4 only). Recompiled and booted
> into the new kernel.
>
> Now even my old port forwards to internal nat'ed
> servers wont work. When restarting iptables I get an
> "iptables-restore: line X failed" (with X being the
> actual line number). If I take out that line, then it
> errors on a different line. It continues like this,
> until all the line with PREROUTING or POSTROUTING are
> removed. These lines (minus the PPTP ones) all worked
> fined before the patch/recompile. I have included my
> iptables file below, external ip is 1.2.3.4 (real ip
> changed to protect the innocent). All the entries in
> the nat table worked before the patch. Can anyone
> shed light on this issue? Thanks in advance for any
> help you can provide.
>
>
>
> *nat
> :OUTPUT ACCEPT [0:0]
> :PREROUTING ACCEPT [0:0]
> :POSTROUTING ACCEPT [0:0]
> -A POSTROUTING -o eth0 -s 192.168.10.0/24 -d 0/0 -j
> MASQUERADE
> -A POSTROUTING -d 192.168.10.1 -j SNAT --to
> 192.168.10.3
> -A POSTROUTING -d 192.168.10.2 -j SNAT --to
> 192.168.10.3
> -A PREROUTING -p tcp -m tcp -d 1.2.3.4 --dport 25 -j
> DNAT --to-destination 192.168.10.2:25
> -A PREROUTING -p udp -m udp -d 1.2.3.4 --dport 47 -j
> DNAT --to-destination 192.168.10.1:47
> -A PREROUTING -p tcp -m tcp -d 1.2.3.4 --dport 80 -j
> DNAT --to-destination 192.168.10.2:80
> -A PREROUTING -p tcp -m tcp -d 1.2.3.4 --dport 99 -j
> DNAT --to-destination 192.168.10.2:99
> -A PREROUTING -p tcp -m tcp -d 1.2.3.4 --dport 110 -j
> DNAT --to-destination 192.168.10.2:110
> -A PREROUTING -p tcp -m tcp -d 1.2.3.4 --dport 1723 -j
> DNAT --to-destination 192.168.10.1:1723
> -A PREROUTING -p tcp -m tcp -d 1.2.3.4 --dport 1974 -j
> DNAT --to-destination 192.168.10.2:1974
> -A PREROUTING -p tcp -m tcp -d 1.2.3.4 --dport 1975 -j
> DNAT --to-destination 192.168.10.2:1975
> -A PREROUTING -p tcp -m tcp -d 1.2.3.4 --dport 3389 -j
> DNAT --to-destination 192.168.10.1:3389
> COMMIT
> *mangle
> :PREROUTING ACCEPT [92:7225]
> :INPUT ACCEPT [92:7225]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [92:7225]
> :POSTROUTING ACCEPT [92:7225]
> COMMIT
> *filter
> :FORWARD DROP [0:0]
> :INPUT ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> -A INPUT -i eth1 -j ACCEPT
> -A INPUT -i lo -j ACCEPT
> -A INPUT -s 1.2.3.4 -j ACCEPT
> -A FORWARD -p tcp -m tcp -d 192.168.10.2 -i eth0
> --dport 25 -j ACCEPT
> -A FORWARD -p udp -m udp -d 192.168.10.1 -i eth0
> --dport 47 -j ACCEPT
> -A FORWARD -p tcp -m tcp -d 192.168.10.2 -i eth0
> --dport 80 -j ACCEPT
> -A FORWARD -p tcp -m tcp -d 192.168.10.2 -i eth0
> --dport 99 -j ACCEPT
> -A FORWARD -p tcp -m tcp -d 192.168.10.2 -i eth0
> --dport 110 -j ACCEPT
> -A FORWARD -p tcp -m tcp -d 192.168.10.1 -i eth0
> --dport 1723 -j ACCEPT
> -A FORWARD -p tcp -m tcp -d 192.168.10.2 -i eth0
> --dport 1974 -j ACCEPT
> -A FORWARD -p tcp -m tcp -d 192.168.10.2 -i eth0
> --dport 1975 -j ACCEPT
> -A FORWARD -p tcp -m tcp -d 192.168.10.1 -i eth0
> --dport 3389 -j ACCEPT
> -A INPUT -p tcp -m tcp --dport 10000 -j ACCEPT
> -A FORWARD -i eth1 -m state --state
> NEW,ESTABLISHED,RELATED -j ACCEPT
> -A FORWARD -i eth0 -m state --state
> ESTABLISHED,RELATED -j ACCEPT
> -A FORWARD -p tcp -d 192.168.10.1 --dport 1723 -m
> state --state NEW -j ACCEPT
> COMMIT
next prev parent reply other threads:[~2004-04-28 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 16:22 PPTP and NAT Boingo
2004-04-28 17:33 ` Luke Deryckx [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-22 10:49 [Fwd: PPTP in 2.4.20] Harald Welte
2003-12-22 12:52 ` PPTP and NAT Jan Kaastrup
2002-09-24 3:46 pptp and nat Lane Brooks
2002-09-27 22:12 ` Darrell Dieringer
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=BCB53910.7D8C%luke@westaironline.com \
--to=luke@westaironline.com \
--cc=b0ing0@yahoo.com \
--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