From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chris Miller" Subject: PPTP reviisted Date: Sun, 28 Sep 2003 01:56:05 -0400 Sender: netfilter-admin@lists.netfilter.org Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C38563.AFAEA260" Return-path: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: To: netfilter@lists.netfilter.org This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C38563.AFAEA260 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I've seen a few things in the netfilter archive about PPTP, but no one has ever really said anything about getting it to work. Here's the deal: I've got a Windows box (192.168.1.10) sitting behind my Linux firewall. On the firewall runs Debian Woody with iptables 1.2.6a. The Linux box acts as a NAT to all the hosts behind it. Currently I forward TCP port 1723 to 192.168.1.10, but clients cannot connect. I know it's got something to do with GRE? I saw something on Google about an ip_conntrac_pptp module, or something to that nature, but I've not been able to find it anywhere. I'd love to compile it and give it a try if it's made to fix this issue. So could someone fill me in with what my options are as far as getting my VPN working through my NAT? What exactly is going on? Thanks, Chris Miller Compuville Computers www.compuville.net 423.276.6692 ------=_NextPart_000_000D_01C38563.AFAEA260 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’ve seen a few things in the netfilter archive = about PPTP, but no one has ever really said anything about getting it to = work.

 

Here’s the deal: I’ve got a Windows box (192.168.1.10) sitting behind my Linux firewall. On the firewall runs = Debian Woody with iptables 1.2.6a. The Linux box acts as a NAT to all the hosts = behind it. Currently I forward TCP port 1723 to 192.168.1.10, but clients = cannot connect. I know it’s got something to do with = GRE?

 

I saw something on Google about an ip_conntrac_pptp = module, or something to that nature, but I’ve not been able to find it = anywhere. I’d love to compile it and give it a try if it’s made to fix = this issue.

 

So could someone fill me in with what my options are = as far as getting my VPN working through my NAT? What exactly is going = on?

 

 

Thanks,

 

Chris Miller

Compuville Computers

www.compuville.net

423.276.6692

 

------=_NextPart_000_000D_01C38563.AFAEA260-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Chemko Subject: Re: PPTP reviisted Date: Sun, 28 Sep 2003 00:27:32 -0700 Sender: netfilter-admin@lists.netfilter.org Message-ID: <3F768D64.3080703@smgtec.com> References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------070203060703060301000009" Return-path: In-Reply-To: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: To: Chris Miller Cc: netfilter@lists.netfilter.org This is a multi-part message in MIME format. --------------070203060703060301000009 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit If you want to enable conntrack for Linux you will need: 1. A Recent Kernel, I know anything later than 2.4.20 can work fine. 2. Kernel patches from pptpclient.sourceforge.net if you want the firewall itself setting up the pptp tunnel, if not, ignore this step 3. CVS download the netfilter code from netfilter.org 4. Apply the patch-o-matic directory to your kernel sources directory like so: # KERNEL_DIR=/usr/src/ ./runme extra 5. Apply all patches that you really care for, but I would recommend anything that doesn't fail out on your configuration.Make sure to include the connectrack patch 6. Build the kernel with the new netfilter options turned on as modules 7. Install Kernel 8. Execute the following every time you want pptp (once per boot): # modprobe ip_conntrack_proto_gre # modprobe ip_nat_proto_gre # modprobe ip_conntrack_pptp # modprobe ip_nat_pptp Chris Miller wrote: > I've seen a few things in the netfilter archive about PPTP, but no one > has ever really said anything about getting it to work. > > > > Here's the deal: I've got a Windows box (192.168.1.10) sitting behind > my Linux firewall. On the firewall runs Debian Woody with iptables > 1.2.6a. The Linux box acts as a NAT to all the hosts behind it. > Currently I forward TCP port 1723 to 192.168.1.10, but clients cannot > connect. I know it's got something to do with GRE? > > > > I saw something on Google about an ip_conntrac_pptp module, or > something to that nature, but I've not been able to find it anywhere. > I'd love to compile it and give it a try if it's made to fix this issue. > > > > So could someone fill me in with what my options are as far as getting > my VPN working through my NAT? What exactly is going on? > > > > > > Thanks, > > > > Chris Miller > > Compuville Computers > > www.compuville.net > > 423.276.6692 > > > --------------070203060703060301000009 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit If you want to enable conntrack for Linux you will need:

1. A Recent Kernel, I know anything later than 2.4.20 can work fine.
2. Kernel patches from pptpclient.sourceforge.net if you want the firewall itself setting up the pptp tunnel, if not, ignore this step
3. CVS download the netfilter code from netfilter.org
4. Apply the patch-o-matic directory to your kernel sources directory like so:
# KERNEL_DIR=/usr/src/<kerneldir> ./runme extra
5. Apply all patches that you really care for, but I would recommend anything that doesn't fail out on your configuration.Make sure to include the connectrack patch
6. Build the kernel with the new netfilter options turned on as modules
7. Install Kernel
8. Execute the following every time you want pptp (once per boot):
# modprobe ip_conntrack_proto_gre
# modprobe ip_nat_proto_gre
# modprobe ip_conntrack_pptp
# modprobe ip_nat_pptp

Chris Miller wrote:

I’ve seen a few things in the netfilter archive about PPTP, but no one has ever really said anything about getting it to work.

 

Here’s the deal: I’ve got a Windows box (192.168.1.10) sitting behind my Linux firewall. On the firewall runs Debian Woody with iptables 1.2.6a. The Linux box acts as a NAT to all the hosts behind it. Currently I forward TCP port 1723 to 192.168.1.10, but clients cannot connect. I know it’s got something to do with GRE?

 

I saw something on Google about an ip_conntrac_pptp module, or something to that nature, but I’ve not been able to find it anywhere. I’d love to compile it and give it a try if it’s made to fix this issue.

 

So could someone fill me in with what my options are as far as getting my VPN working through my NAT? What exactly is going on?

 

 

Thanks,

 

Chris Miller

Compuville Computers

www.compuville.net

423.276.6692

 

--------------070203060703060301000009-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jon Pol" Subject: REDIRECT incoming Port to IP Date: Mon, 29 Sep 2003 11:34:10 +0800 Sender: netfilter-admin@lists.netfilter.org Message-ID: <006c01c3863a$8c3785e0$51df7dcb@expi> References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0069_01C3867D.99DF0630" Return-path: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: To: netfilter@lists.netfilter.org This is a multi-part message in MIME format. ------=_NextPart_000_0069_01C3867D.99DF0630 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Just a quick newbie Q: I want to redirect incoming/outgoing traffic ports (1024-65535) to a = certain IP Address (192.168.0.10). that is; incoming/outgoing traffic ---- > 203.x.x.x(destination port 1024-65535) = -----> REDIRECT -----> (192.168.0.10) any hint? Thanks. JP ------=_NextPart_000_0069_01C3867D.99DF0630 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Just a quick newbie Q:
 
I want to redirect incoming/outgoing=20 traffic ports (1024-65535)  to a certain IP Address = (192.168.0.10).=20 that is;
 
incoming/outgoing traffic ---- >=20 203.x.x.x(destination port 1024-65535) -----> REDIRECT ----->=20 (192.168.0.10)
 
any hint?
 
Thanks.
JP
 
 
------=_NextPart_000_0069_01C3867D.99DF0630-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jon Pol" Subject: Re: REDIRECT incoming Port to IP Date: Mon, 29 Sep 2003 12:14:58 +0800 Sender: netfilter-admin@lists.netfilter.org Message-ID: <008301c38640$3e8b6ea0$51df7dcb@expi> References: <006c01c3863a$8c3785e0$51df7dcb@expi> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0080_01C38683.4C94BE00" Return-path: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: To: Jon Pol , netfilter@lists.netfilter.org This is a multi-part message in MIME format. ------=_NextPart_000_0080_01C38683.4C94BE00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable thanks. got it to work :-) ----- Original Message -----=20 From: Jon Pol=20 To: netfilter@lists.netfilter.org=20 Sent: Monday, September 29, 2003 11:34 AM Subject: REDIRECT incoming Port to IP Just a quick newbie Q: I want to redirect incoming/outgoing traffic ports (1024-65535) to a = certain IP Address (192.168.0.10). that is; incoming/outgoing traffic ---- > 203.x.x.x(destination port = 1024-65535) -----> REDIRECT -----> (192.168.0.10) any hint? Thanks. JP ------=_NextPart_000_0080_01C38683.4C94BE00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
thanks. got it to work :-)
----- Original Message -----
From:=20 Jon=20 Pol
To: netfilter@lists.netfilter.o= rg=20
Sent: Monday, September 29, = 2003 11:34=20 AM
Subject: REDIRECT incoming Port = to=20 IP

Just a quick newbie Q:
 
I want to redirect incoming/outgoing=20 traffic ports (1024-65535)  to a certain IP Address = (192.168.0.10).=20 that is;
 
incoming/outgoing traffic ---- >=20 203.x.x.x(destination port 1024-65535) -----> REDIRECT ----->=20 (192.168.0.10)
 
any hint?
 
Thanks.
JP
 
 
------=_NextPart_000_0080_01C38683.4C94BE00-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chris Miller" Subject: RE: PPTP reviisted Date: Mon, 29 Sep 2003 15:26:52 -0400 Sender: netfilter-admin@lists.netfilter.org Message-ID: References: <3F768D64.3080703@smgtec.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C3869E.22350280" Return-path: In-Reply-To: <3F768D64.3080703@smgtec.com> Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: To: 'Daniel Chemko' Cc: netfilter@lists.netfilter.org This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C3869E.22350280 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Now I've got another problem. Here are the steps and what I did: 1) I got kernel 2.4.22 2) Didn't need this 3) Done. 4) Done. 5) Did almost all of them. Didn't do the ones like ipv6 stuff. Everything went fine. Done. 6) Done. 7) Booted new kernel. Everything seems fine. SSH in so I can apply a rule that for some reason didn't get applied at boot. Here's what happenend: # iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -j MASQUERADE iptables: Invalid argument # So, you can see my problem. I've tried -j MASQ and iptables tells me it can't find that target. I've got ipt_MASQUERADE loaded, and a mod-info shows it's the right one for my kernel. I've also tried it with -o eth1. eth1 is inside, eth2 is outside (eth0 is nothing as of now). Outside is DHCP or I'd use SNAT. However, I replaced MASQUERADE with SNAT and got the same error. What gives? I'm getting closer at least. Thanks, Chris Miller Compuville Computers www.compuville.net _____ From: Daniel Chemko [mailto:dchemko@smgtec.com] Sent: Sunday, September 28, 2003 3:28 AM To: Chris Miller Cc: netfilter@lists.netfilter.org Subject: Re: PPTP reviisted If you want to enable conntrack for Linux you will need: 1. A Recent Kernel, I know anything later than 2.4.20 can work fine. 2. Kernel patches from pptpclient.sourceforge.net if you want the firewall itself setting up the pptp tunnel, if not, ignore this step 3. CVS download the netfilter code from netfilter.org 4. Apply the patch-o-matic directory to your kernel sources directory like so: # KERNEL_DIR=/usr/src/ ./runme extra 5. Apply all patches that you really care for, but I would recommend anything that doesn't fail out on your configuration.Make sure to include the connectrack patch 6. Build the kernel with the new netfilter options turned on as modules 7. Install Kernel 8. Execute the following every time you want pptp (once per boot): # modprobe ip_conntrack_proto_gre # modprobe ip_nat_proto_gre # modprobe ip_conntrack_pptp # modprobe ip_nat_pptp Chris Miller wrote: I've seen a few things in the netfilter archive about PPTP, but no one has ever really said anything about getting it to work. Here's the deal: I've got a Windows box (192.168.1.10) sitting behind my Linux firewall. On the firewall runs Debian Woody with iptables 1.2.6a. The Linux box acts as a NAT to all the hosts behind it. Currently I forward TCP port 1723 to 192.168.1.10, but clients cannot connect. I know it's got something to do with GRE? I saw something on Google about an ip_conntrac_pptp module, or something to that nature, but I've not been able to find it anywhere. I'd love to compile it and give it a try if it's made to fix this issue. So could someone fill me in with what my options are as far as getting my VPN working through my NAT? What exactly is going on? Thanks, Chris Miller Compuville Computers www.compuville.net 423.276.6692 ------=_NextPart_000_0006_01C3869E.22350280 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Now I’ve got another problem. = Here are the steps and what I did:

 

1)       = I got kernel 2.4.22

2)       = Didn’t need this

3)       = Done.

4)       = Done.

5)       = Did almost all of them. Didn’t do the ones like ipv6 = stuff. Everything went fine. Done.

6)       = Done.

7)       = Booted new kernel. Everything seems fine. SSH in so I can = apply a rule that for some reason didn’t get applied at boot. Here’s = what happenend:

 =

# iptables -t = nat -A POSTROUTING -s 192.168.1.0/24 –j MASQUERADE

iptables: = Invalid argument

#

 =

So, you can see my problem. = I’ve tried –j MASQ and iptables tells me it can’t find that = target. I’ve got ipt_MASQUERADE loaded, and a mod-info shows it’s the right one = for my kernel. I’ve also tried it with –o eth1. eth1 is inside, = eth2 is outside (eth0 is nothing as of now). Outside is DHCP or I’d use = SNAT. However, I replaced MASQUERADE with SNAT and got the same = error.

 

What gives? I’m getting = closer at least…

 

 

Thanks,

=

 

Chris = Miller

Compuville = Computers

www.compuville.net=

 


From: = Daniel Chemko [mailto:dchemko@smgtec.com]
Sent: Sunday, September = 28, 2003 3:28 AM
To: Chris Miller
Cc: netfilter@lists.netfilter.org
Subject: Re: PPTP = reviisted

 

If you want to enable conntrack for Linux you will need:

1. A Recent Kernel, I know anything later than 2.4.20 can work fine.
2. Kernel patches from pptpclient.sourceforge.net if you want the = firewall itself setting up the pptp tunnel, if not, ignore this step
3. CVS download the netfilter code from netfilter.org
4. Apply the patch-o-matic directory to your kernel sources directory = like so:
# KERNEL_DIR=3D/usr/src/<kerneldir> ./runme extra
5. Apply all patches that you really care for, but I would recommend = anything that doesn't fail out on your configuration.Make sure to include the connectrack patch
6. Build the kernel with the new netfilter options turned on as = modules
7. Install Kernel
8. Execute the following every time you want pptp (once per boot):
# modprobe ip_conntrack_proto_gre
# modprobe ip_nat_proto_gre
# modprobe ip_conntrack_pptp
# modprobe ip_nat_pptp

Chris Miller wrote:

I’ve seen a few things in the netfilter archive = about PPTP, but no one has ever really said anything about getting it to = work.

 

Here’s the deal: I’ve got a Windows box (192.168.1.10) sitting behind my Linux firewall. On the firewall runs = Debian Woody with iptables 1.2.6a. The Linux box acts as a NAT to all the hosts = behind it. Currently I forward TCP port 1723 to 192.168.1.10, but clients = cannot connect. I know it’s got something to do with = GRE?

 

I saw something on Google about an ip_conntrac_pptp = module, or something to that nature, but I’ve not been able to find it = anywhere. I’d love to compile it and give it a try if it’s made to fix = this issue.

 

So could someone fill me in with what my options are = as far as getting my VPN working through my NAT? What exactly is going = on?

 

 

Thanks,

 

Chris = Miller

Compuville = Computers

www.compuville.net

423.276.6692

=

 

------=_NextPart_000_0006_01C3869E.22350280-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philip Craig Subject: Re: PPTP reviisted Date: Tue, 30 Sep 2003 09:58:50 +1000 Sender: netfilter-admin@lists.netfilter.org Message-ID: <3F78C73A.8060003@snapgear.com> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Chris Miller Cc: netfilter@lists.netfilter.org Chris Miller wrote: > 7) Booted new kernel. Everything seems fine. SSH in so I can apply a > rule that for some reason didn't get applied at boot. Here's what happenend: > > > > # iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -j MASQUERADE > > iptables: Invalid argument From the help for the latest pptp-conntrack-nat.patch: - you have to recompile your iptables userspace program since some structure sizes change -- Philip Craig - philipc@snapgear.com - http://www.SnapGear.com SnapGear - Custom Embedded Solutions and Security Appliances