On Friday 19 December 2008 10:15:59 James Knott wrote:
Danesh Daroui wrote:
Thanks for the tip, but the problem is that when I installed "openVPN" via YaST, I can not run "openvpn" in shell. It shows that the package is installed but it can not be run. By the way, do you connect to your Linux VPN from XP, by establishing a VPN connection as it should be for other VPNs?
It can be started by (root) command or in Yast System Services. I use the command method. On my firewall, I use the following commands in /etc/init.d/boot.local: #start vpn tunnel modprobe tun /usr/local/bin/vpn_up &
That script points to /usr/local/bin/vpn_up: #! /bin/bash cd /etc/openvpn /usr/sbin/openvpn --config static-office.conf
Seems like an odd way of starting up an openvpn daemon. Typically, boot.local will be run before the network has been brought up (particularly if controlled by NetworkManager), so openvpn will fail. I guess your conf has enough retries that it eventually comes up though. There is normally a openvpn init script supplied with the package - why not use that? Going back to the OP, as has been mentioned the openvpn binary is in an sbin directory so is not in a normal user path, and is typically run under root privileges because it requires read/write access to a network device (in this case tun or tap). Even explicitly specifying the openvpn binary won't be enough to have your non-root user be able to manipulate an openvpn connection without rights being applied elsewhere. There is also a NetworkManager plugin for openvpn available which does allow a non-root user to configure and start up an openvpn connection from a desktop. Maybe that would be the best place to look? Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org