This is not really a bug. You can work around the "tun" issue by loading the tun module (see earlier posts) but it will still fail trying to bind to port 500 (ports <1024 are protected so that only root may bind them). You really need to use sudo to run the command. Unfortunately, the kvpnc home web page instructions for doing so are incomplete.
I'm using Suse Linux and had the same problem. Note, the recommended method for modifying /etc/sudoers is to use the program visudo which requires vi. Here's how we fixed it: 1) When you use sudo, by default your environment variables changes. You need to have ACCESS or XAUTHORITY in the allowed list of variables. In the file /etc/sudoers You can either comment out the line: Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE" or you can modify it to read like this: Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE DISPLAY XAUTHORITY" 2) In /etc/sudoers there is a note which says "When configuring sudo, delete the two following lines:". I missed that when I first setup sudoers so other people may have too. The lines to delete (I just commented them out by prepending with a "#") are: #Defaults targetpw # ask for the password of the target user i.e. root #ALL ALL=(ALL) ALL # WARNING! Only use this together with 'Defaults targetpw'! 3) Suse has a graphical utility called Yast (some people hate it, I happen to like it) for system configuration which allows you to choose the user, runas, nopassword and command. It then modifies the /etc/sudoers file. Using yast, the change to sudoers looks like this: VPNUser ALL = (root) NOPASSWD: /opt/kde3/bin/kvpnc NOTE: I BELIEVE THE PATH TO KVPNC WILL BE DIFFERENT IN UBUNTU! 4) By default, X is not permitting other processes to contact it, you need to turn it off by running "xhost +". I created a desktop icon with the following command to do this then run sudo kvpnc. xhost + && sudo /opt/kde3/bin/kvpnc && xhost - AGAIN, THE PATH TO KVPNC IS DIFFERENT IN UBUNTU! As much as I'd like to, I can't take credit for finding this, it was my boss who figured it out. He also sent a message to the kvpnc people so they can update their documentation. A couple more notes: I tried setting kvpnc to use the Cisco client, it didn't work, I had to use vpnc. Kvpnc would not work unless I manually added a logon name in the config file (Preferences - Profile - Authenticate - User data). Without a pre-entered name, I kept getting "no logon name". The MOTD (message of the day) which pops up when a user connects to my VPN does not work with this client. I wouldn't care if this were for me but I'm creating an image which will be used by our end users and our MOTD includes legal mumbo jumbo. I worked around this by putting the legal notice on the desktop wallpaper. Sorry for the long winded posting, I think that's everything. Good luck! Scott -- Loading of module "tun" failed! https://bugs.launchpad.net/bugs/109420 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
