From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] networking
Date: Sun, 23 May 2004 14:00:58 -0400 [thread overview]
Message-ID: <20040523180058.GA664@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <20040522011010.7767fc2a.user05@kyberwelt.de>
On Sat, May 22, 2004 at 01:10:10AM +0200, ich hier wrote:
>
> Hi!
>
> Something i did not understand until now (after playing for a while
> with this nice piece of software :) ) is the usage of tun/tap devices.
> As far as i understood, qemu (the running task) just allocates free
> device-names (tunX) as needed and runs a script /etc/qemu-ifup (if
> available) and thats it.
"qemu -n other-script" will let you use a script other than /etc/qemu-ifup,
if you want.
> But is there any way, to tell qemu which exact (preconfigured)
> devices to use? Or do i have to catch the allocated devicenames,
> as qemu throws them at me (or my script :) ) and try to make
> something useful with this names (such as bridging or routing)???
You could use "qemu -tun-fd fd", but I'm not sure how as I've never used
it directly. The man page says that an example is available at
http://bellard.org/qemu/tetrinet.html
> It would be very nice, if there is some way (like in user-mode-linux
> for example) to tell qemu with arguments, how to map each emulated
> network-device to a predefined tun device. This way someone could
> configure various sets of tundevices with fixed names. Management
> would be much easier.
> Also bridging of devices would be much cleaner and other tools which
> use tun/tap devices could be hardwired (even with names like "tunX"
> :) )
I prefer using VDE myself. It uses tap0 for ALL emulated machines on the
network, instead of tun0 for machine 1, tun1 for machine 2, etc. No bridging
required. Needs a bit more work to set up tho.
>
> THNX in advance for your answers. Maybe i just had tomatoes on my eyes.
> (like we would say here in germany)
>
You can also try "qemu -user-net" if you wanted. Its not as good as tuntap,
but a lot easier to set up. It also might be slightly buggier.
> user05
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2004-05-23 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 23:10 [Qemu-devel] networking ich hier
2004-05-23 18:00 ` Jim C. Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-23 3:02 liebrecht
2019-01-24 10:16 ` Stefan Hajnoczi
2005-06-24 19:20 [Qemu-devel] Networking wrichter
2005-06-24 18:31 Wolfgang Richter
2005-06-24 18:51 ` Renzo Davoli
2005-06-24 18:52 ` Tom Sandholm
2005-06-25 22:25 ` Henrik Nordstrom
2005-06-25 22:58 ` Jim C. Brown
2004-02-10 18:47 [Qemu-devel] networking pietro capriata
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=20040523180058.GA664@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).