report: tun device

report: tun device

[kees]

Hi

I have build 2.4.15pre3 but stil can't use /dev/net/tun (vtund).

from logfile:

Nov 13 08:38:29 schoen3 vtund[16676]: Session merin[xxx.xxx.xxx.xxx:1402]
opened
Nov 13 08:38:29 schoen3 vtund[16676]: Can't allocate tun device. File
descriptorNov 13 08:38:29 schoen3 vtund[16676]: Session merin closed
Nov 13 08:38:35 schoen3 vtund[16677]: Session merin[xxx.xxx.xxx.xxx:1403]
opened
Nov 13 08:38:35 schoen3 vtund[16677]: Can't allocate tun device. File
descriptorNov 13 08:38:35 schoen3 vtund[16677]: Session merin closed

kees

Re: report: tun device

[J Sloan]

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

Re: report: tun device

[kees]

Hi

No I downloaded 2.4.14 and applied patch-2.4.15.pre3

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
>
>

Re: report: tun device

[David S. Miller]

   From: kees <kees@schoen.nl>
   Date: Tue, 13 Nov 2001 11:38:32 +0100 (CET)

   No I downloaded 2.4.14 and applied patch-2.4.15.pre3
   
I think he's referring to the tun userland utilities version, not the
kernel version.  There is a required tun utility upgrade, if I
remember.

Franks a lot,
David S. Miller
davem@redhat.com

Re: report: tun device

[J Sloan]

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
> >
> >

Re: report: tun device

[J Sloan]

"David S. Miller" wrote:

>    From: kees <kees@schoen.nl>
>    Date: Tue, 13 Nov 2001 11:38:32 +0100 (CET)
>
>    No I downloaded 2.4.14 and applied patch-2.4.15.pre3
>
> I think he's referring to the tun userland utilities version, not the
> kernel version.  There is a required tun utility upgrade, if I
> remember.

Both actually - there was a change around
kernel 2.4.6 IIRC that required a new version
of vtund (2.5b1) - so if vtund was working in
e.g.  a vanilla RH 7.1 install, and he upgraded
to 2.4.14, vtund would be broken and he'd
have to upgrade to the latest version.

cu

jjs

Re: report: tun device

[kees]

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

----------------------------------------- from the trace

writev(2, [{"vtund[27645]: Session demo_s[127"..., 51}, {"\n", 1}], 2) = 52
rt_sigaction(SIGPIPE, {0x40137270, [], 0x4000000}, {SIG_IGN}, 8) = 0
send(4, "<30>Nov 13 19:37:48 vtund[27645]"..., 71, 0) = 71
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
open("/dev/net/tun", O_RDWR)            = 7
ioctl(7, 0x54ca, 0xbffff18c)            = -1 EBADFD (File descriptor in
bad statclose(7)                                = 0
time([1005676668])                      = 1005676668
getpid()                                = 27645
writev(2, [{"vtund[27645]: Can\'t allocate tun"..., 73}, {"\n", 1}], 2) = 74
rt_sigaction(SIGPIPE, {0x40137270, [], 0x4000000}, {SIG_IGN}, 8) = 0

----------------------------------------

I'm willing and able to do more tests

regards
Kees


On Tue, 13 Nov 2001, J Sloan wrote:

> 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
> > >
> > >
>

Re: report: tun device

[J Sloan]

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

Re: report: tun device

[kees]

Hi,

answers:

1) vtun-2.5b1.tar.gz
2) none, it was the first time I build and tried to run it

Kees



> > I referred to KERNEL 2.4.14 with patch-2.4.15pre3
> >
>
> 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
>

Re: report: tun device

[J Sloan]

kees wrote:

> Hi,
>
> answers:
>
> 1) vtun-2.5b1.tar.gz
> 2) none, it was the first time I build and tried to run it
>

Ah, now we are getting somewhere.

2 more questions to round out the info:

Are you running a distro that ships kernel
headers separately from the kernel itself?
(BTW what distro was that again?) and if
so, do you perhaps have the original kernel
headers package installed?

cu

jjs

Re: report: tun device

[kees]

On Wed, 14 Nov 2001, J Sloan wrote:

> kees wrote:
>
> > Hi,
> >
> > answers:
> >
> > 1) vtun-2.5b1.tar.gz
> > 2) none, it was the first time I build and tried to run it
>
> Ah, now we are getting somewhere.
>
> 2 more questions to round out the info:
>
> Are you running a distro that ships kernel

I'm running  SuSE 7.2 but the kernel I downloaded recently


> headers separately from the kernel itself?
> Most distros do nowdays - and if so, do
> you perhaps have an old kernel headers
> package installed? (like the original)
I would have sworn  <-------!!!!

 that /usr/include/linux had pointed to
/usr/src/linux/include/linux
and /usr/include/asm to /usr/src/linux/include/asm-i386

BUT   THEY DON'T!!

blush blush, it must have been changed back while upgrading from
SuSE 7.0 to SuSE 7.2

I will revert it and test again.

thanks

Kees



>
> BTW what distro is it, if I may ask?
>
> cu
>
> jjs
>