Re: [BUG?] vtund broken by tun driver changes in 2.4.6
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" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG?] vtund broken by tun driver changes in 2.4.6
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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
