From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] tun/tap support for 9vx
Date: Fri, 7 May 2010 11:57:02 -0700 [thread overview]
Message-ID: <20100507185703.2EDDB5B3E@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 08 May 2010 03:54:26 +1000." <20100507175426.GA24219@diamond.realm.of.chaos>
On Sat, 08 May 2010 03:54:26 +1000 Tully Gray <tullygray@arc.net.au> wrote:
>
> I have modified Erik Quanstrom's raw socket ethernet driver
> for 9vx so that it uses the Linux kernel's "tap" device.
Neat!
> < if((fd = socket(PF_PACKET, SOCK_RAW, htons(ETH_P_ALL))) < 0)
> ---
> > if((fd = open("/dev/net/tun", O_RDWR)) < 0){
On *BSD tun is for IP frames, tap is for ethernet frames
so there you'd use /dev/tap. You may wish to see how Qemu
handles tap differences & multiple tap interfaces on various
platforms.
On Fri, 07 May 2010 19:14:58 BST "Devon H. O'Dell" <devon.odell@gmail.com> wrot
e:
>
> Yes. The tap(4) interface allows you to clone an existing ethernet
> device on the system, and it's what most virtualization platforms use.
Sorry for nitpicking! "tap" appears as a completely separate
virtual ethernet interface to the host. The "other end" of
tap is a device, to be open()ed by a program. One can bridge
the host side interface to existing physical ethernet
interfaces but you don't have to.
prev parent reply other threads:[~2010-05-07 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 17:54 Tully Gray
2010-05-07 18:00 ` Devon H. O'Dell
2010-05-07 18:04 ` erik quanstrom
2010-05-07 18:08 ` erik quanstrom
2010-05-07 18:14 ` Devon H. O'Dell
2010-05-07 18:47 ` Tully Gray
2010-05-07 18:57 ` Bakul Shah [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=20100507185703.2EDDB5B3E@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.com \
--cc=9fans@9fans.net \
/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).