All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: "René Gallati" <draxinusom@gmail.com>
Cc: Nick Drage <nickd@metastasis.org.uk>,
	Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: vpn
Date: Wed, 15 Sep 2004 07:37:41 -0400	[thread overview]
Message-ID: <1095248261.2070.137.camel@localhost> (raw)
In-Reply-To: <50f03b970409150142291aaa96@mail.gmail.com>

On Wed, 2004-09-15 at 04:42, René Gallati wrote:
<snip>
> As far as I know openvpn uses it
> (http://openvpn.sourceforge.net/index.html) It is fairly easy to
> install and far more flexible and robust if one or both sides of the
> tunnels have dynamic ip addresses. I've used FreeSwan for some years
> and always had stability troubles when one side went down but the
> tunnel wasn't properly terminated on the other side and such things.
> I've switched to openvpn after the removal of the ipsec pseudodevices
> which made my firewall rules unusable.
> 
> Now with openvpn you again have a device per tunnel on which you can
> easily filter as before with ipsecN, just now they are called tunN
> and/or tapN (depending on which type of tunnel you want)
> 
> You can furthermore do some things that ipsec cannot or are very
> difficult. Using the tap's it emulates a virtual network card, so you
> have arp running over it. You can easily do dhcp over taps and
> furthermore broadcasts and multicast simply works over these pseudo
> devices. It's just like both ends of the vpn have an additional nic
> that is directly connected to each other.
> 
> I currently use it in a project where many peers connect to one vpn
> server which then bridges together all these vpn endpoints and thus
> creates one big "lan" segment where the peers can communicate to each
> other mainly using broadcast and multicast. (it's a network testbed
> for multihop routing protocols)
OpenVPN does look like a very flexible technology.  We are very
interested in integrating other forms of VPN besides IPSec with iptables
in the ISCS project including OpenVPN.  As a slight aside, is anyone
interested in working on the OpenVPN module for ISCS (or SSL for that
matter)? The idea is that someone can describe their environment and
ISCS will go out and create and automatically distribute rule sets and
configurations that will make iptables and whatever VPN method work
together to provide a secure communications system.  An introduction is
available at http://iscs.sourceforge.net Thanks - John
-- 
John A. Sullivan III
Open Source Development Corporation
Financially sustainable open source development
http://www.opensourcedevel.com



  reply	other threads:[~2004-09-15 11:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 13:46 vpn Peter Marshall
2004-09-14 13:55 ` vpn George Ross
2004-09-14 14:22 ` vpn Brent Clark
2004-09-14 14:31 ` vpn Michael Gale
2004-09-14 14:42 ` vpn John A. Sullivan III
2004-09-14 16:07   ` vpn Nick Drage
2004-09-15  3:01     ` vpn Ted Kaczmarek
2004-09-15  8:42     ` vpn René Gallati
2004-09-15 11:37       ` John A. Sullivan III [this message]
2004-09-14 17:20 ` vpn Jason Opperisano
  -- strict thread matches above, loose matches on Subject: below --
2004-06-30 16:34 VPN paulobruck1
2004-06-30 16:52 ` VPN John A. Sullivan III

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=1095248261.2070.137.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=draxinusom@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=nickd@metastasis.org.uk \
    /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.