|
From: Jan J. K. <ja...@ni...> - 2011-06-04 20:58:58
|
Hi, Joselito Tapangan wrote: > > On Fri, Jun 3, 2011 at 3:32 PM, David Sommerseth > <ope...@to... <mailto:ope...@to...>> > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 03/06/11 02:34, Joselito Tapangan wrote: > > Hi, > > > > When I run as root the command modinfo tun the display is this. > > / > > filename: > /lib/modules/2.6.18-194.32.1.el5/kernel/drivers/net/tun.ko > > alias: char-major-10-200 > > license: GPL > > author: (C) 1999-2004 Max Krasnyansky <ma...@qu... > <mailto:ma...@qu...> > > <mailto:ma...@qu... <mailto:ma...@qu...>>> > > description: Universal TUN/TAP device driver > > srcversion: 23EC8E176639DE5F2DA2D21 > > depends: > > vermagic: 2.6.18-194.32.1.el5 SMP mod_unload 686 REGPARM > 4KSTACKS gcc-4.1 > > module_sig: > > 883f3504d24ffbb59f555817d939ea9112a82c09f6a8588888271 > <tel:8588888271>f5528944640a3f7bdd769eaaa760a08a76254af60772266157edea59dfbde7f294c70 > > / > > When I run as root the modprobe tun. There is no error display > but also > > there is no output. It goes directly to the prompt. > > > > [please, don't top post] > > When modprobe do give any output, it means everything is okay. > The command > most likely worked fine. You can verify that by doing as JJK > suggested: > > lsmod | grep tun > > If you see a line with 'tun' listed, it means the tun module is > loaded and > ready to be used. > > > kind regards, > > David Sommerseth > > > > On Fri, Jun 3, 2011 at 4:42 AM, Jan Just Keijser > <ja...@ni... <mailto:ja...@ni...> > > <mailto:ja...@ni... <mailto:ja...@ni...>>> wrote: > > > > do (as root) > > modinfo tun > > modprobe tun > > > > if the second command returns an error , then there's > something wrong > > with your CentOS installation ; after the 'modprobe' do an > > lsmod | grep tun > > to see if the device is actually listed. > > > > HTH, > > > > JJK > > > > [...snip...] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk3ojh0ACgkQDC186MBRfro5TgCgig5fz6v2xFXJ68tS5dB3IHNw > lwAAnifkPMnbsfdijj+elw8bNq6Q26oo > =zv0W > -----END PGP SIGNATURE----- > > > As what have you said, If there is no error the tun module is probably > is running and ready to use. However the main problem of mine is the > OpenVPN itself when I tried to run It failed and when I try to see the > logs. > This is what I found in the error log; > / > "Tue May 31 09:58:43 2011 us=705749 Note: Cannot ioctl TUNSETIFF tun0: > Device or resource busy (errno=16) > Tue May 31 09:58:43 2011 us=705763 Note: Attempting fallback to kernel > 2.2 TUN/TAP interface > Tue May 31 09:58:43 2011 us=705787 Cannot open TUN/TAP dev /dev/tun0: > No such file or directory (errno=2) > Tue May 31 09:58:43 2011 us=705811 Exiting"/ > > What I need to know how to solve this problem Since we all know the > module of tun is running, Any other possible reason why I commit that > error? If there is so How can I do such solution? Your help is a great > appreciated. so the 'tun' module is loaded; which user is used to start openvpn? openvpn normally must be run as 'root' (or via 'sudo' ). also, try running, as root, openvpn --dev tun --proto udp and post the output here - on my CentOS box that gives Sat Jun 4 22:58:13 2011 TUN/TAP device tun0 opened HTH, JJK |