All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] tun interface
Date: Thu, 26 Aug 2004 19:44:32 -0400	[thread overview]
Message-ID: <20040826234432.GA12212@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200408271137.23491.andrej@paradise.net.nz>

On Fri, Aug 27, 2004 at 11:37:23AM +1200, Andrej wrote:
> On Fri, 27 Aug 2004 09:20, Joe Menola wrote:
> Hi Joe,
> 
> Thanks for the response.
> > You need kernel support for tun (modprobe tun).
> 
> > You'll find it under "Networking support" using xconfig. Once
> > the module is loaded /dev/net/tun will be created.
> It is present, but qemu doesn't create anything under
> /dev/net/tun even with tun pre-loaded. Do I  need to 
> make the executable SUID or something?
> 
> 
> > -jm
> Andrej
> 
> 

Keep in mind that the tun device is created in the ethernet namespace, not in
the /dev tree. So, to see it, you'll need to use ifconfig.

/dev/net/tun is accessable by root only, by default. You either need root
perms or you have to change the permissions on /dev/net/tun to let
qemu use it.

> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2004-08-26 23:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 20:30 [Qemu-devel] tun interface Andrej
2004-08-26 21:20 ` Joe Menola
2004-08-26 23:37   ` Andrej
2004-08-26 23:44     ` Jim C. Brown [this message]
2004-08-26 23:52       ` Andrej
2004-08-27  0:02     ` Joe Menola
2004-08-27  6:43       ` Renzo Davoli
2004-08-27 23:15       ` Andrej
2004-08-28  5:37         ` Joe Menola

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=20040826234432.GA12212@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 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.