From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] VPN Solution
Date: Tue, 21 Nov 2006 06:15:05 +0000 [thread overview]
Message-ID: <45629969.9050208@riverviewtech.net> (raw)
On 11/21/06 00:20, Rangi Biddle wrote:
> What I want to do is have a VPN (PPTP/IPSEC/CIPE/etc) server, but it
> must support more than one simultaneous connection.
>
> I currently have a PPTP VPN server setup that has port 1723 and protocol
> 47 DNAT’d through to the internal IP address of the VPN server and I
> have not been able to have more than one connection at a time. I am
> considering setting up the VPN server as a gateway (for lack of a better
> word) and instead of DNATing the connections through to the internal IP
> I would setup a DMZ with the VPN server as the only host. My only
> concern in doing so is that if it does not work what other options do I
> have besides getting a different connection type such as fibre? I’m
> trying to do this as cheaply as possible.
Can / will you provide some more information such as what type of client
will be connecting to the VPN concentrator?
I believe the 1 concurrent connection you are referring to is a limitation
of IPTables match extension for PPTP tunnels. If you put the VPN
Concentrator such that it is directly routable you should have better luck.
Beyond PPTP, you can look in to IPSec or SSLTunnel, or any number of other
products. However to be able to determine which of the products is best
suited to your situation, we need to know more about your situation.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-11-21 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 6:15 Grant Taylor [this message]
2006-11-21 6:20 ` [LARTC] VPN Solution Rangi Biddle
2007-02-04 2:49 ` Nyamul Hassaan
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=45629969.9050208@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.