qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John R. Hogerhuis" <jhoger@pobox.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Feature request: option to disable protection in user mode networking
Date: Thu, 30 Sep 2004 12:57:11 -0700	[thread overview]
Message-ID: <1096574231.10584.10.camel@aragorn> (raw)
In-Reply-To: <20040930092541.A692@bbland>

On Thu, 2004-09-30 at 00:25, Lionel Ulmer wrote:
> > User mode networking is nifty++. I was wondering, though if it would be
> > possible to disable the guest OS protection as a runtime option.
> 
> This is not possible as (AFAIK), QEMU's ethernet adaptator emulation layer
> has absolutely no idea on which ports the guest OS is listening to. So to do
> what you want, it would entail opening all possible ports on the QEMU side
> and 'forward' them to the guest OS.
> 
> This is already possible, but I doubt that you want to DoS your Linux box by
> using all possible ports :-)
> 
>             Lionel

Why would you consider a "forward-all" option to be a DoS?

All cheapo NAT boxes have this and gamers who don't know any better
often use it to get games to work rather than finding the handful or
bank of ports they actually need to open. NAT is kind of analagous to
user-mode networking in QEMU, but not quite...

I think the real problem here is that to listen on a port, slirp (the
host) has to create a listening socket. If you want to effectively have
a "forward all" you would either have to have a listen open on every
port. Add to that the fact that some ports will already have listens on
them, and that as an average user qemu won't have access privileged
ports at all.

So I think the original poster needs to use TUN/TAP networking if he
wants to experiment with the guests's firewall.

-- John.

  reply	other threads:[~2004-09-30 20:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28  4:36 [Qemu-devel] Feature request: option to disable protection in user mode networking Mike MacCana
2004-09-30  7:25 ` Lionel Ulmer
2004-09-30 19:57   ` John R. Hogerhuis [this message]
2004-09-30 20:04     ` Lionel Ulmer
2004-09-30  8:45 ` Johannes Schindelin

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=1096574231.10584.10.camel@aragorn \
    --to=jhoger@pobox.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).