From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: "Ryan Mack" <rmack@mackman.net>, <max_mk@yahoo.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [BUG?] vtund broken by tun driver changes in 2.4.6
Date: Sat, 7 Jul 2001 09:12:37 -0700 [thread overview]
Message-ID: <009601c106ff$a3cb2070$6baaa8c0@kevin> (raw)
In-Reply-To: <Pine.LNX.4.33.0107070058350.29490-100000@mackman.net>
Recompile your VTUND daemon with the new kernel headers (and also updated to
2.5 vtund, it has some small patches) and you will be fine.
----- Original Message -----
From: "Ryan Mack" <rmack@mackman.net>
To: <max_mk@yahoo.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, July 07, 2001 1:02 AM
Subject: [BUG?] vtund broken by tun driver changes in 2.4.6
> I recently upgraded a server running vtund 2.4 (4/18/01) to stock 2.4.6
> kernel. It seems the changes to the tun driver have broken vtund. Now my
> syslog gets filled with the following messages when a client attempts to
> connect:
>
> Jul 5 10:15:53 mackman vtund[4011]: Session
> mackman-vpn[64.169.117.25:2359] opened
> Jul 5 10:15:53 mackman vtund[4011]: Can't allocate tun device. File
> descriptor in bad state(77)
> Jul 5 10:15:53 mackman vtund[4011]: Session mackman-vpn closed
> Jul 5 10:16:04 mackman vtund[4014]: Session
> mackman-vpn[64.169.117.25:2360] opened
> Jul 5 10:16:04 mackman vtund[4014]: Can't allocate tun device. File
> descriptor in bad state(77)
> Jul 5 10:16:04 mackman vtund[4014]: Session mackman-vpn closed
>
> Eventually the client gives up. Do you have any suggestions or know of
> any fixes?
>
> Thanks, Ryan Mack
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2001-07-07 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 8:02 [BUG?] vtund broken by tun driver changes in 2.4.6 Ryan Mack
2001-07-07 16:12 ` Kevin P. Fleming [this message]
[not found] <Pine.LNX.4.33.0107070058350.29490-100000@mackman.net.suse.lists.linux.kernel>
[not found] ` <009601c106ff$a3cb2070$6baaa8c0@kevin.suse.lists.linux.kernel>
2001-07-13 13:33 ` Joerg Reuter
2001-07-13 15:58 ` Maksim Krasnyanskiy
2001-07-13 17:43 ` Joerg Reuter
2001-07-13 19:44 ` Maksim Krasnyanskiy
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='009601c106ff$a3cb2070$6baaa8c0@kevin' \
--to=kevin@labsysgrp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=max_mk@yahoo.com \
--cc=rmack@mackman.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.