Alberto Gonzalez Iniesta <a...@inittab.org> said: > Hi all, > > After I decided to push OpenVPN 2.0 into Debian for future inclusion in > Sarge, I got this [1] bug report from one Debian user. It seems that 2.0 > doesn't get along well with udev, as opposed to 1.6. I don't use udev, > so I can't really tell, but has anything changed from 1.6 to 2.0 in the > way the device is handled? > > The suspicious message is: > > Oct 16 16:31:12 gimli wait_for_sysfs[5873]: error: wait_for_sysfs needs an update to handle the device '/class/net/tun0' properly, please report to <linux-hotplug-de...@lists.sourceforge.net> > > The bug submitter claims that OpenVPN 1.6 deals correctly with it. Maybe > it has something to do with device probing?
The TUN/TAP handling code in 2.0 is nearly identical to the 1.6 code. The only change I can think of is the setting of txqueuelen on the TUN/TAP driver. Incidentally, the error shown in the bug report looks like he is trying to make a tunnel between 1.6 and 2.0 using incompatible key-method parameters. He needs to set --key-method 2 on the 1.6 side. > Thanks, > > Alberto > > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276799 > > > P.S. James, did you find out anything about this [2]? Do you think it > could be due to hardware (RAM) problem? I'm thinking about tagging it > irreproducible. Yes, I would tend to mark it as irreproducible for now. I tried to contact him for more info, but haven't received any response. > [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=265632 James
