From: davidsen@tmr.com (bill davidsen)
To: rreid@studio3arc.com
Subject: Re: Microsoft PPTP VPN server behind FIREWALL
Date: Tue, 25 Mar 2003 13:34:18 -0500 [thread overview]
Message-ID: <200303251834.NAA02380@gatekeeper.tmr.com> (raw)
In-Reply-To: <001501c2f2f5$2b662920$1001a8c0@s3ac>
In article <001501c2f2f5$2b662920$1001a8c0@s3ac> you write:
|
| >
| > I tried to use this command to make a forward to itenal IP
| > address: iptables -t nat -A PREROUTING -d $EXTERNALIP -p tcp
| > --dport 1723 -j DNAT --to 192.168.1.150:1723 But it doesn't
| > work, I mean I cannot connect to my VPN server from outside.
| >
| > Any ideas or issues?
|
|
| FYI iptables does not support pptp filtering. In order to support it you
| need to apply the pptp patch from patchomatic. In my experience it's not
| worth it. I ended up using FreeSwan installed on myfirewall gateway as
| my VPN solution.
I believe there is a userspace IPsec package, reasonably high overhead
but runable where a patched kernel is politacally incorrect. Does that
ring a bell with anyone?
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-03-25 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 20:08 ipv6 and state matching Trever L. Adams
2003-03-25 8:33 ` Jozsef Kadlecsik
2003-03-25 13:08 ` Microsoft PPTP VPN server behind FIREWALL Remus
2003-03-25 15:22 ` Ilguiz Latypov
2003-03-25 17:37 ` Rowan Reid
2003-03-25 18:34 ` bill davidsen [this message]
2003-03-25 15:53 ` ipv6 and state matching Trever L. Adams
2003-03-25 23:33 ` Jozsef Kadlecsik
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 16:57 Microsoft PPTP VPN server behind FIREWALL Daniel Chemko
2003-03-27 20:46 Steve M Bibayoff
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=200303251834.NAA02380@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=rreid@studio3arc.com \
/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