From: chris friedhoff <chris@friedhoff.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu and kernel 2.6.18
Date: Sat, 14 Oct 2006 09:47:06 +0200 [thread overview]
Message-ID: <20061014094706.a59e3e33.chris@friedhoff.org> (raw)
In-Reply-To: <9b0d5f320610131000x744ce6cagd549f4ec0e1ac9f7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]
Hello,
bringing up the tun/tap interface depends now on the capability CAP_NET_ADMIN, which usually only root has.
This patch just removes this dependency, so normal user rights suffices again to bring up the tun/tap interface.
diff -ruN linux-2.6.18-orig/drivers/net/tun.c linux-2.6.18/drivers/net/tun.c
--- linux-2.6.18-orig/drivers/net/tun.c 2006-09-20 05:42:06.000000000 +0200
+++ linux-2.6.18/drivers/net/tun.c 2006-10-02 09:21:52.000000000 +0200
@@ -489,9 +489,6 @@
err = -EINVAL;
- if (!capable(CAP_NET_ADMIN))
- return -EPERM;
-
/* Set dev type */
if (ifr->ifr_flags & IFF_TUN) {
/* TUN device */
chris
######################################
On Fri, 13 Oct 2006 13:00:10 -0400
WaxDragon <waxdragon@gmail.com> wrote:
> This came up in IRC a few days ago, it seems you need to use the UML
> util 'tunctl' to assign permissions to the tap device. I found this
> change annoying.
>
> On 10/13/06, G Portokalidis <georgios.portokalidis@gmail.com> wrote:
> > Hello all,
> > I have recently installed the latest linux kernel, and i have been
> > having problems with the tap interface since.
> >
> > I have been getting the following cryptic message:
> > warning: could not configure /dev/net/tun: no virtual network emulation
> > Could not initialize device 'tap'
> >
> > The tun driver is loaded, and /dev/net/tun is 'rw'.
> > Any ideas what this is about? Could i have misconfigured something in
> > the kernel?
> >
> > Cheers,
> > George
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
>
>
> --
> 22:38 <@WaxDragon> false ^ true
> 22:39 < false> :(
> 22:39 < false> dont you think you can XOR me and get away with it! I
> always return!
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
--------------------
Chris Friedhoff
chris@friedhoff.org
[-- Attachment #2: 2.6.18-tun-without-cap_net_admin-capability.patch.bz2 --]
[-- Type: application/octet-stream, Size: 306 bytes --]
next prev parent reply other threads:[~2006-10-14 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 15:31 [Qemu-devel] qemu and kernel 2.6.18 G Portokalidis
2006-10-13 17:00 ` WaxDragon
2006-10-14 7:47 ` chris friedhoff [this message]
2006-10-15 7:31 ` Tace
2006-10-16 8:36 ` chris friedhoff
2006-10-17 12:29 ` G Portokalidis
2006-11-06 16:20 ` Chris Friedhoff
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=20061014094706.a59e3e33.chris@friedhoff.org \
--to=chris@friedhoff.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.