From: "Jim C. Brown" <jma5@umd.edu>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] make qemu use tap0 instead of tun0
Date: Wed, 6 Jul 2005 22:19:13 -0400 [thread overview]
Message-ID: <20050707021913.GA16038@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <20050707020551.GA15727@jbrown.mylinuxbox.org>
On Wed, Jul 06, 2005 at 10:05:51PM -0400, Jim C. Brown wrote:
> I know this. Actually that page seems out of date, as Linux's tuntap now sends
> all accesses to /dev/net/tun regardless of the type of device (tun or tap).
>
I should also add that on Linux, you can set the device name to what you want -
the requirement for tapX for tap devices and tunX for tun devices is not
enforced.
Note that for BSD, the function tun_open() in vl.c does open /dev/tap.
> The current NE2000 emulation (or any hardware nic emulation for that matter)
> would not work if qemu used an actual tun device.
>
Ok this is not 100% true either. It wouldn't be too difficult to add a layer on
top of the nic hw emulation that did ethernet frame to ip frame and vice versa
before passing the frames to a tun device. (The user mode networking code
already does ethernet frame conversion.) So it wouldn't be that difficult to
get to work, and you wouldn't lose too much either (only IP-based protocols
such as TCP or UDP would work, but I've never heard of anyone trying to use
IPX or even IPv6 with qemu so that probably is not an issue).
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-07-07 2:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 23:08 [Qemu-devel] make qemu use tap0 instead of tun0 Jim C. Brown
2005-07-07 1:55 ` Herbert Poetzl
2005-07-07 2:06 ` Jim C. Brown
[not found] ` <20050707020551.GA15727@jbrown.mylinuxbox.org>
2005-07-07 2:19 ` Jim C. Brown [this message]
2005-07-10 5:07 ` Henrik Nordstrom
2005-07-10 5:03 ` Henrik Nordstrom
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=20050707021913.GA16038@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=herbert@13thfloor.at \
--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).