From: J Sloan <jjs@toyota.com>
To: kees <kees@schoen.nl>
Cc: J Sloan <jjs@toyota.com>, Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: report: tun device
Date: Tue, 13 Nov 2001 12:47:25 -0800 [thread overview]
Message-ID: <3BF186DD.A71B796D@lexus.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111132131330.29497-100000@schoen3.schoen.nl>
kees wrote:
> Hi,
>
> I referred to KERNEL 2.4.14 with patch-2.4.15pre3
>
> I did recompile vtund AFTER my new kernel installment and startup and it
> didn't help.
> I traced vtund and it opens /dev/net/tun
> the ioctl call after it returns the error
Yes, but the big questions remained unanswered:
1. What version of vtund are you running?
2. Under what kernel did vtund last work?
cu
jjs
next prev parent reply other threads:[~2001-11-13 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 7:44 report: tun device kees
2001-11-13 9:55 ` J Sloan
2001-11-13 10:38 ` kees
2001-11-13 10:45 ` David S. Miller
2001-11-13 20:06 ` J Sloan
2001-11-13 20:03 ` J Sloan
2001-11-13 20:37 ` kees
2001-11-13 20:47 ` J Sloan [this message]
2001-11-14 7:14 ` kees
2001-11-14 9:47 ` J Sloan
[not found] <3BF23D21.B8F356DA@pobox.com>
2001-11-14 11:04 ` kees
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=3BF186DD.A71B796D@lexus.com \
--to=jjs@toyota.com \
--cc=kees@schoen.nl \
--cc=linux-kernel@vger.kernel.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