From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Interesting QEMU + OpenVPN
Date: Wed, 2 Aug 2006 14:57:51 +0100 [thread overview]
Message-ID: <200608021457.52230.paul@codesourcery.com> (raw)
In-Reply-To: <200608020955.59856.it@tidetamerboatlifts.com>
> I have used OpenVPN in this scenario and it works exceptionally well,
> especially since you can bridge the adapters on the host and transparently
> connect the guest to your internal LAN. Maybe one day qemu will have
> builtin OpenVPN support so it won't have to be installed on the guest?
You can already bridge the host and gues using the existing networking options
(and/or VDE - http://vde.sf.net), without the encryption overhead and without
needing any special setup on the guest.
If you actually need the encryption then IMHO that's best left to dedicated
packages like OpenVPN.
Paul
next prev parent reply other threads:[~2006-08-02 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 20:29 [Qemu-devel] Interesting QEMU + OpenVPN Jonathan Kalbfeld
2006-08-02 4:53 ` Dirk Behme
2006-08-02 13:55 ` Joseph Miller
2006-08-02 13:57 ` Paul Brook [this message]
2006-09-10 12:36 ` [Qemu-devel] " Samuel Tardieu
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=200608021457.52230.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).