qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Eric S. Johansson" <esj@harvee.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: suitability for extension encapsulation in firewall
Date: Fri, 06 Jul 2007 13:36:23 -0400	[thread overview]
Message-ID: <f6luk9$teg$1@sea.gmane.org> (raw)
In-Reply-To: <200707061527.48372.paul@codesourcery.com>

Paul Brook wrote:

> 
> If you use tap networking (recommended for this situation) it's just like any 
> other network interface.

what I was looking for was the ability to place the qemu tap interface on the 
same subnet as the DMZ network and outside of the firewall rules so that it 
behaves exactly the same as a machine in the DMZ.  that is, it is 
protected/blocked by the orange network rules and can access any other machine 
on the DMZ without any hindrance.  I need to think about this a bit.  Both in 
terms of how to set up a simulated firewall environment and how I would 
configure the tap interface.  I can just see myself running qemu inside of qemu 
and 3 virtual networks.

---eric

      reply	other threads:[~2007-07-06 17:37 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
2007-07-06 17:36   ` Eric S. Johansson [this message]

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='f6luk9$teg$1@sea.gmane.org' \
    --to=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).