[PARTIALY SOLVED] TINC (vpn daemon) has stopped working after compiling kernel

[Martin Rusko]

Hi folks,
I still don't know, why I'm not able to compile kernel 2.4.18 from 
Debian sources such way, that it will work with tinc. But compiled 
kernel 2.4.19 is working just fine, so I won't investigate it any 
futher. ;-))

          Thanks

                mARTin


Martin Rusko wrote:
> 
> 
> Eric Estabrooks wrote:
>  > Martin Rusko wrote:
>  >
>  >> Hi folks, after recompiling of kernel (need quota support), tinc
>  >> daemon has stopped working. Messages from log file are: ... Nov 21
>  >> 14:45:02 m61 tinc.sunnet[326]: tincd 1.0pre7 starting Nov 21
>  >> 14:45:02 m61 tinc.sunnet[326]: /dev/net/tun is a Linux ethertap
>  >> device Nov 21 14:45:02 m61 tinc.sunnet[326]: Process 327 (tinc-up)
>  >> exited with non-zero status 255 Nov 21 14:45:02 m61
>  >> tinc.sunnet[326]: Ready Nov 21 14:45:02 m61 tinc.sunnet[326]: Error
>  >> while reading from Linux ethertap device /dev/net/tun: File
>  >> descriptor in bad state Nov 21 14:45:07 m61 last message repeated
>  >> 13683 times
>  >
>  >
>  >
>  > I had this exact same problem when working with vtun which uses the
>  > tun/tap kernel module.  The IOCTL numbers changed between kernel
>  > versions, I updated my /usr/include/linux files to match my kernel
>  > and recompiled vtun to get rid of the problem.  I believe in
>  > particular it was IOR or IOWR numbers that changed.  It was a while
>  > ago so I don't remember the specifics, but it did take me a while to
>  > track it down.
>  >
>  > Eric
>  >
>  >
> Hi Eric,
> thank you very much for your interest.
> 
> Well, I know about this issue. It was discussed in the tinc mailing 
> list. But I'm compiling kernel with the same kernel version (2.4.18) as 
> the distribution kernel have. And I'm compiling kernel from the same 
> sources, as the distribution kernel has been compiled (probably, I 
> didn't do it personaly ;-)).
> 
> Anyway, as I wrote: I did compile tinc against my custom kernel, and it 
> didn't work again. But the same tinc (compiled against custom kernel 
> headers) WORKS on distribution kernel. And that fact, brings me an idea, 
> that something wrong is in a way, how I'm compiling kernel.
> 
> I'm just going to compile kernel from kernel-source-2.4.18 package with 
> config file attached to kernel-image-2.4.18-sun4u package. So I should 
> obtain exactly the same kernel, as the working kernel from woody is.
> 
> Thank you for your time and sorry my poor English. ;-)
> 
>        Best regards
> 
>                 mARTin
> 


-- 
Martin Rusko
PhD student
Department of Automation and Measurement
Faculty of Mechanical Engineering
Slovak University of Technology
--
E-mail: rusko at sunsite.mine.nu
Web:    http://sunsite.mine.nu/~rusko
--
motto: We are Microsoft! Resistance is futile. Open your
        source code and prepare for assimilation.

Tinc:         Discussion list about the tinc VPN daemon
Archive:      http://mail.nl.linux.org/lists/
Tinc site:    http://tinc.nl.linux.org/