From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Eric S. Johansson" <esj@harvee.org>
Subject: Re: [Qemu-devel] suitability for extension encapsulation in firewall
Date: Fri, 6 Jul 2007 15:27:47 +0100 [thread overview]
Message-ID: <200707061527.48372.paul@codesourcery.com> (raw)
In-Reply-To: <f6l2jd$nm0$1@sea.gmane.org>
On Friday 06 July 2007, Eric S. Johansson wrote:
> I'm looking for a way to encapsulate applications on a firewall (IPCop).
> My line of reasoning is an encapsulated extension environment would help
> protect the integrity of the firewall and give users greater latitude in
> creating extension applications. What I would like to do is install qemu
> as a "virtual server" residing on the DMZ/Orange network with its interface
> fully controlled by the Orange network firewall rules. I've run qemu and
> am slightly familiar with the tun/tap setup but I don't know its
> relationship to IP tables. Does is sit outside the rules like the raw
> device or inside?
If you use usermode networking it's just like any other application running on
that machine.
If you use tap networking (recommended for this situation) it's just like any
other network interface.
Paul
next prev parent reply other threads:[~2007-07-06 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 9:38 [Qemu-devel] suitability for extension encapsulation in firewall Eric S. Johansson
2007-07-06 14:27 ` Paul Brook [this message]
2007-07-06 17:36 ` [Qemu-devel] " Eric S. Johansson
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=200707061527.48372.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=esj@harvee.org \
--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).