From: J Sloan <jjs@toyota.com>
To: kees <kees@schoen.nl>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: report: tun device
Date: Tue, 13 Nov 2001 12:03:37 -0800 [thread overview]
Message-ID: <3BF17C99.A11BDAA0@lexus.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111131138001.16924-100000@schoen3.schoen.nl>
kees wrote:
> Hi
>
> No I downloaded 2.4.14 and applied patch-2.4.15.pre3
OK, let me rephrase the question:
What kernel version were you running when
vtun last worked?
Also, what version of vtun have you?
cu
jjs
>
>
> Kees
>
> On Tue, 13 Nov 2001, J Sloan wrote:
>
> > kees wrote:
> >
> > > Hi
> > >
> > > I have build 2.4.15pre3 but stil can't use /dev/net/tun (vtund).
> > >
> > >
> > > Nov 13 08:38:29 schoen3 vtund[16676]: Can't allocate tun device. File
> >
> > Did you upgrade from a pre-2.4.6 kernel?
> >
> > mirai.cx: /home/jjs
> > (tty/dev/pts/2): bash: 1003 > uname -a
> > Linux mirai.cx 2.4.15-pre4 #2 Mon Nov 12 22:55:11 PST 2001 i686 GenuineIntel
> > mirai.cx: /home/jjs
> > (tty/dev/pts/2): bash: 1002 > ifconfig tun0
> > tun0 Link encap:Point-to-Point Protocol
> > inet addr:192.168.111.254 P-t-P:192.168.111.253
> > Mask:255.255.255.255
> > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1450 Metric:1
> > RX packets:17 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:10
> >
> >
next prev parent reply other threads:[~2001-11-13 20:04 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 [this message]
2001-11-13 20:37 ` kees
2001-11-13 20:47 ` J Sloan
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=3BF17C99.A11BDAA0@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