From: Thomas Kirk <thomas@arkena.com>
To: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
Cc: netfilter@lists.netfilter.org,
Roksana Boreli <Roksana.Boreli@nicta.com.au>
Subject: Re: Multiple IPSEC VPNs through a firewall based on 2.4.2X kernel
Date: Thu, 26 Aug 2004 11:13:28 +0200 [thread overview]
Message-ID: <20040826091328.GD18545@arkena.dk> (raw)
In-Reply-To: <1093339912.2050.208.camel@localhost>
Hi
On Tue, Aug 24, 2004 at 05:31:52AM -0400, John A. Sullivan III wrote:
> The answer depends on what exactly you are trying to do. If you are
> branching together two networks, you may wish to consider moving the
> IPSec stack to the Linux gateway and creating a LAN-to-LAN connection.
> If you wish to restrict access to just those few clients, you can make
> such restrictions in iptables.
Excusing me for interrupting the discussion but in a situation where i
would like to make a LAN-to-LAN IPsec VPN between to offices both
running iptables on the gateways. Ive been lurking on the liste for
some time but i have a few questions regarding this. First each site
have a link to internet howto specify which protocols that should go
over VPN and which should go to internet? Which IPsec implementation
would be the most stable and secure solution to use. Currently im
using a couple of retired pcworkstations running debian woody so i
would prefer something that is supported by debian but its not
absolutly neccessary :)
Thanks in advance
--
Venlig Hilsen/Kind Regards
Thomas Kirk
IT-chef
ARKENA A/S
Mejlgade 27-29, DK-8000 Aarhus C
Havnegade 39, DK-1058 København K
Telephone Direct: +45 8620 4264
Telephone Office: +45 7023 3456
Telephone Mobile: +45 2612 3237
Office FAX: +45 8620 4270
WWW: http://www.arkena.com
--
"I've always wondered if there was a god. And now I know there is --
and it's me." -- Homer Simpson
next prev parent reply other threads:[~2004-08-26 9:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 5:11 Multiple IPSEC VPNs through a firewall based on 2.4.2X kernel Roksana Boreli
2004-08-24 5:46 ` Ming-Ching Tiew
2004-08-24 7:32 ` Payal Rathod
2004-08-24 7:50 ` Ming-Ching Tiew
2004-08-24 8:53 ` bridge + transparent proxy ArioS
2004-08-24 9:31 ` Multiple IPSEC VPNs through a firewall based on 2.4.2X kernel John A. Sullivan III
2004-08-26 9:13 ` Thomas Kirk [this message]
2004-08-26 10:39 ` John A. Sullivan III
2004-08-26 14:14 ` Tom Eastep
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 11:56 Jason Opperisano
2004-08-25 7:24 Roksana Boreli
2004-08-25 11:29 ` John A. Sullivan III
2004-08-25 11:44 Jason Opperisano
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=20040826091328.GD18545@arkena.dk \
--to=thomas@arkena.com \
--cc=Roksana.Boreli@nicta.com.au \
--cc=john.sullivan@nexusmgmt.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 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.