Go to Settings - Configure KVpnc... - Application - Debug. Enable 'Show debug console' and set Log level to 2. Its also recommended to check 'Keep connection files'.
Its a bug in 0.8.5.1 and its fixed in later releases. As workaround you can go to Settings - Configure KVpnc... - Profile - Certificate/Psk - Certificate path and set it to /etc/openvpn.
You'll find it at /root/.kde/share/apps/kvpnc/kvpnc.log. If you running (K)Ubuntu or have setup sudo use, root have to replaced with your username.
Its not implemented yet. Its on the list with planned features. It w'll need a lot of work, so its not estimated in near future.Help is everytime welcome.
Yes, you will need 0.8.8. Install l2tpd and a ipsec vpn server (strongSwan, Openswan, racoon). Then you can create a new profile within the wizard.
Yes, you will need 0.8.8. Smartcard support is given for OpenVPN and strongSwan. On the smartcard settings set special provider library if needed and click on Detect button right next the smartcard slot combobox. After successful detect select the right slot and click on Detect button right next the smartcard id combobox. Now you can select your ID.
Great! You can help by working on the project. Currenly open tasks:
handbook review/update
programming
translations
config data redesign
Just send a mail to the author or join the irc channel. Also you can donate money/hardware.
You can send a mail to the author or visit the IRC channel #kvpnc on irc.freenode.net for talking with the KVpnc team.
Yes it can do that. Just configure a new OpenVPN connection with the wizard and select 'Pre Shared Key' at Authentication settings.
There could some reasons for that problem. Be sure you have enabled UDP in NAT settings if you behind a NAT router (if unsure, ask your network administrator). A old bug in KVpnc had set a local port on advanced settings which is wrong. This only happens igf you have an old config from a previous version and have imported the pcf profile file. In this case simply uncheck the use of the local port in advanced settings at profile manager. The last problem is not a problem of KVpnc, its a bug in vpnc (read more innen). KVpnc >= 0.8.6 can handle this bug.Another reason is vpnc >= 0.4.x because it has changed some parameters. KVpnc >= 0.8.9 can handle this.