qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Christian de Rivaz <jc@eclis.ch>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] tun/tap networking
Date: Sat, 01 Oct 2005 22:24:03 +0200	[thread overview]
Message-ID: <433EF063.3080101@eclis.ch> (raw)
In-Reply-To: <20051001131215.GB28444@jbrown.mylinuxbox.org>


>>You point the real question: why it has been impossible to get accepted 
>>any patch that fixed this. I has proposed one myself and I get no 
>>comment at all. I see similar effort from others and obviousely there 
>>failed almost the same way. No getting any valuable comment about why a 
>>idea proposed by many peopoles is not applyed make this subject very hard.
>>
> 
> 
> The change I was talking about is a one line patch...
> 
> It's annoying that Fabrice has said nothing about it. But it doesn't actually
> mess anything up, it's just confusing for advanced users.
> 
> I presume that the device qemu makes is called tun0 because Fabrice wants to
> make clear that he doesnt use (and wont support) the ethertap device. Not a
> very good reason.
> 
> (Or maybe he wants to keep it tun0 because if he changed the name he'd have
> to change the option -tun-fd to -tap-fd and that'd break some scripts.)
> 
> 
>>I hope that we can resolve this subject, because in my point of view, 
>>using a existing "tun" is far more simpler than create one the way quemu 
>>do;
> 
> 
> I never mentioned that. At all.

Agree. Sorry, I extented the subjet beyon the initial subjet of this thread.

> And qemu already supports that, via the -tun-fd option.

Can you please give me an exemple how to use the -tun-fd option to open 
an existing tun (i.e: tun-alice) ? This option only work for already 
opened tap/tun interface as I understand.

> 
>>and this open a lot of new uses in terme of the network managment of 
>>the quemu instance. The very first one for me is to allow only root to 
>>setup a DHCP server and to assign "tuns" interfaces to the users that 
>>needs it, so there don't even have to think about the network setup, 
>>ther just boot into quemu an OS with a DHCP client.
>>
> 
> 
> That is a little tricky to do - but qemu can do it.

The problem is exactly because this is tricky! Simply telling quemu to 
use a existing tun and boot a OS with a DHCP client is the simplest 
operation you can imagine to allow testing network experiment. Network 
setup is the job of root. Users just use the setup and that must be dead 
simple.

Regards,
-- 
Jean-Christian de Rivaz

  reply	other threads:[~2005-10-01 20:25 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 22:13 [Qemu-devel] tun/tap networking Don Kitchen
2005-09-30 22:21 ` Henrik Nordstrom
2005-09-30 22:21 ` Paul Brook
2005-09-30 23:01 ` Jim C. Brown
2005-10-01  8:12   ` Jean-Christian de Rivaz
2005-10-01 13:12     ` Jim C. Brown
2005-10-01 20:24       ` Jean-Christian de Rivaz [this message]
2005-10-01 21:09         ` Jim C. Brown
2005-10-01 21:17           ` Jean-Christian de Rivaz
2005-10-01 20:47       ` [Qemu-devel] tun/tap networking: patch for existing tun Jean-Christian de Rivaz
2005-10-02  2:42         ` Henrik Nordstrom
2005-10-02  7:56           ` Jean-Christian de Rivaz
2005-10-02 10:24             ` Henrik Nordstrom
2005-10-02 16:53               ` Lars Munch
2005-10-02 17:50                 ` Jean-Christian de Rivaz
2005-10-02 19:47                   ` Jim C. Brown
2005-10-02 20:27                     ` Jean-Christian de Rivaz
2005-10-02 18:45             ` Anthony Liguori
2005-10-02 19:39               ` Jim C. Brown
2005-10-02 20:23                 ` Jean-Christian de Rivaz
2005-10-02 22:37                   ` Jim C. Brown
2005-10-03  9:46                     ` Jean-Christian de Rivaz
2005-10-03 12:04                       ` Jim C. Brown
2005-10-03 13:10                         ` Jean-Christian de Rivaz
2005-10-03 13:19                         ` Henrik Nordstrom
2005-10-03 13:13                       ` Henrik Nordstrom
2005-10-03 14:14                         ` Jean-Christian de Rivaz
2005-10-03 13:07                     ` Henrik Nordstrom
2005-10-03 14:00                       ` Jean-Christian de Rivaz
2005-10-03 15:04                       ` Jim C. Brown
2005-10-03 13:01                   ` Henrik Nordstrom
2005-10-03 13:58                     ` Jean-Christian de Rivaz
2005-10-03 15:06                     ` Jim C. Brown
2005-10-03 12:54                 ` Henrik Nordstrom
2005-10-03 15:14                   ` Jim C. Brown
2005-10-03 18:29                     ` Fabrice Bellard
2005-10-03 19:22                       ` Christian MICHON
2005-10-03 20:29                         ` Jean-Christian de Rivaz
2005-10-04  7:09                           ` Christian MICHON
2005-10-04  7:56                             ` Jean-Christian de Rivaz
2005-10-03 21:36                       ` Jim C. Brown
2005-10-04  8:23                       ` Matteo
2005-10-04 11:34                         ` Jim C. Brown
2005-10-01 17:49     ` [Qemu-devel] tun/tap networking Henrik Nordstrom
2005-10-01 20:54       ` Jean-Christian de Rivaz
2005-10-01 11:30   ` Oliver Gerlich
2005-10-01 13:07     ` Jim C. Brown
2005-10-01 13:50       ` Paul Brook
2005-10-01 21:15         ` Jim C. Brown
2005-10-02  2:21           ` Henrik Nordstrom
2005-10-01 17:52     ` 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=433EF063.3080101@eclis.ch \
    --to=jc@eclis.ch \
    --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).