From: Hans-Werner Hilse <hilse@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] tun/tap - ifconfig tun0 - device not found
Date: Sat, 8 Jul 2006 18:53:05 +0200 [thread overview]
Message-ID: <20060708185305.badad17c.hilse@web.de> (raw)
In-Reply-To: <fd8aab850607071504t135d174ai1c83b6edd02f7f60@mail.gmail.com>
Hi,
On Fri, 7 Jul 2006 19:04:41 -0300
"Claudinei Matos" <claudineimatos@gmail.com> wrote:
> I'm trying to use tun/tap to assign some ip to my server (since I'll need it
> to my LVS solution) and I think it's a trivial task to put tun to work, but
> I'm trying in 3 different machines (with 2 different kernels) and in both
> they when I try to ifconfig tun0 I get the follow message:
> tun0: error fetching interface information: Device not found
>
> Well, I'd try to look if is something wrong with my kernel configuration but
> is everything ok since it just need tun/tap support to be compiled (I did
> tried both module and built-in).
>
> /dev/net/tun is a valid character device with 10, 200 (major/minor)
...and, is at first all you get by enabling TUN support in the kernel.
See /usr/src/linux/Documentation/networking/tuntap.txt for more
information about the ioctl() you have to issue in order to register a
tun network device (TUNSETIFF). The docs have a code example, too.
Oh, and I think OpenVPN has inbuilt functionality to create or remove
tun network devices (independent from OpenVPNs other functionality).
I've not completely understood what your usage scenario was, but maybe
a dummy network device is enough?
-hwh
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-08 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 22:04 [gentoo-user] tun/tap - ifconfig tun0 - device not found Claudinei Matos
2006-07-08 16:53 ` Hans-Werner Hilse [this message]
2006-07-08 18:01 ` Claudinei Matos
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=20060708185305.badad17c.hilse@web.de \
--to=hilse@web.de \
--cc=gentoo-user@lists.gentoo.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