All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Scott MacKay <scottmackay@yahoo.com>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: vpn under linux
Date: Mon, 12 Apr 2004 12:01:00 -0400	[thread overview]
Message-ID: <1081785660.16834.13.camel@localhost> (raw)
In-Reply-To: <20040412122513.2441.qmail@web13908.mail.yahoo.com>

I'm afraid I don't have time to answer in depth today but here are a few
quick answers regarding *swan:

On Mon, 2004-04-12 at 08:25, Scott MacKay wrote:
> I had a couple questions about the different methods
> talked about here, probably focusing on CIPE,
> FreeSWAN/OpenSWAN, and the OpenVPN (along with any
> others users may chime in with)
> 1.  Where in the netfilter path do these solutions
> package up data?  Important to know if we see
> tunnel/VPN packets or the contents which are going
> into them, both incoming and outgoing
*swan makes this convenient by passing the traffic from the physical
interface to an ipsec interface, e.g., eth0 -> ipsec0.  I believe there
are extensive diagrams of how this works in the training section at
http://iscs.sourceforge.net
> 2.  Which of these guys support broadcast or
> multicast?
> 3.  Do any of these support non-encrypted
> transmission?  The reason for this would be if a
> higher level/later service provided the encryption
> over the risky sections of a transmission
> 4.  What kind of overhead do these cost?  I was
> curious from the perspective of initialization/updates
> and also any additional packet headers (rough guess). 
There are some performance benchmarks buries somewhere in the extensive
*swan documentation.
> 
<snip>
-- 
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net 



  reply	other threads:[~2004-04-12 16:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  9:01 vpn under linux Gianni Pucciani
2004-04-10  9:18 ` Antony Stone
2004-04-10  9:31   ` Gianni Pucciani
2004-04-10  9:44     ` Antony Stone
2004-04-10  9:41   ` Gianni Pucciani
2004-04-10 10:00     ` Antony Stone
2004-04-10 10:15       ` Gianni Pucciani
2004-04-10 23:41       ` Alexander Samad
2004-04-11  0:09         ` Aaron P. Martinez
2004-04-12 12:25         ` Scott MacKay
2004-04-12 16:01           ` John A. Sullivan III [this message]
2004-04-12 18:58             ` Dick St.Peters
2004-04-10  9:47   ` Victor Julien
2004-04-10 12:30 ` John A. Sullivan III
2004-04-10 17:23   ` Tony Earnshaw

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=1081785660.16834.13.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=scottmackay@yahoo.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 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.