qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] question for QEMU users
Date: Wed, 17 Nov 2004 17:23:25 -0500	[thread overview]
Message-ID: <20041117222325.GA10291@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <874qjog9z8.fsf@Janik.cz>

On Wed, Nov 17, 2004 at 09:23:23AM +0100, Pavel Jan?k wrote:
>    From: Hetz Ben Hamo <hetzbh@gmail.com>
>    Date: Wed, 17 Nov 2004 03:07:36 +0200
> 
> Hi,
> 
>    > * Others (if you have suggestions - go ahead)..
> 
> - use vmnet like approach for networking where you simply get IP from your
>   local network, no bridges, etc.
> -- 
> Pavel Jan?k

	I do not know how vmnet works. VDE does this (you get your IP from
the local network(1) and you don't have to deal with bridges). The problem
is that you do have firewall/router headaches sometimes.

	It would be nice if we could just run a script or program that works
on all linux systems and fixes up firewall trouble ... this is actually not
difficult to do (assuming the script knows what tapN device (basicly a kind
of ethN device) VDE is using and what the ip addresses are) it is just no one
has bothered to write a generic script to handle this yet. This script could
easily handle automaticly setting up routing as well (but for some people that
includes a kernel recompile).

	It would be nicer if the program could be used on non-nix OSes as well
(modifying a script so it works on various *nixes is not a trivial task but it
is far from unreasonably difficult). But I only use *nix OSes for qemu hosts
so I don't have to think about this part at all.

(1) This "local" network is actually a virtual network. So qemu would get its
IP for the virtual network but it would not be visible on your real LAN without
some router work. Hence the need for that magic script.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  parent reply	other threads:[~2004-11-17 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17  1:07 [Qemu-devel] question for QEMU users Hetz Ben Hamo
2004-11-17  2:49 ` John R. Hogerhuis
2004-11-17 13:05   ` Philipp Gühring
2004-11-17 19:14     ` Tim
2004-11-17 21:15       ` Joe Batt
2004-11-17 21:24         ` Carlos Valiente
2004-11-17  8:23 ` Pavel Janík
2004-11-17  9:43   ` Gwenole Beauchesne
2004-11-17 22:23   ` Jim C. Brown [this message]
2004-11-17 12:08 ` Johannes Schindelin
2004-11-17 14:30 ` malc
2004-12-05 22:00   ` Derek Fawcus
2004-11-17 16:52 ` jeebs
2004-11-17 18:14 ` Lennert Buytenhek
2004-11-17 19:14   ` brian
2004-11-18  9:40 ` vaise
2004-11-28 15:40 ` [Qemu-devel] " Emmanuel Charpentier
2004-11-28 18:22   ` Richard Neill

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=20041117222325.GA10291@jbrown.mylinuxbox.org \
    --to=jbrown106@phreaker.net \
    --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).