Thank you very much. That worked.

#sudo modprobe tun

#sudo ls -l /dev/net/tun
crw-rw-rw- 1 root root 10, 200 Sep 6 07:51 /dev/net/tun

#sudo openvpn --config myvpn.ovpn

I run the command manually....
sudo openvpn --config myvpn.ovpn

This ran and i got vpn IP address
However, i am not getting my command line back.

.......
Thu Sep 6 09:12:51 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
....
....
Thu Sep 6 09:12:53 2018 /usr/bin/ip route add 10.x.y.0/32 via 10.x.y.25
Thu Sep 6 09:12:53 2018 Initialization Sequence Completed

(Here the cursor just waits forever)
If i hit Ctrl-D, it kills the VPN conection

Question 1> When running this command manually, how do i get my command line back

Question 2> I tried to run this during boot up but i am not being successful as per the article below.
(https://wiki.archlinux.org/index.php/OpenVPN)

# sudo systemctl start openvpn-client@myvpn.service
(myvpn is the config file located at /etc/openvpn/client/myvpn.ovpn)

Failed to get D-Bus connection: Operation not permitted

Any thoughts?

Many thanks!
jim

caymann,

I think I have an easy answer to your first question. Just append "&" to the end of the command and it will launch in the background, leaving your shell script available:

"sudo openvpn --config myvpn.ovpn &"

I don't have a good answer on the auto launching. Hopefully someone else can help you with that. I've also just noticed that brfransen has pushed the updates from testing to the production repos. If you update, you will likely need to go back to the first openvpn package that I linked because the dependency packages will have changed.

Thanks for that.
I figured out how to use runit
So i am using runit and works fine during bootup
It is running as a service now

I created:
#sudo nano /etc/sv/openvpn/run

And added the following contents

!/bin/sh
echo "Starting ExpressVPN"
exec 2>&1
sudo modprobe tun
sudo /usr/bin/openvpn --config /etc/openvpn/client/vpn.conf


I made it executible
#chmod +x run

#sudo add_service.sh openvpn
#sudo sv stop openvpn
#sudo sv start openvpn
# sudo sv status openvpn
run: openvpn: (pid 863) 20257s
reboot

That's terrific. Sorry I wasn't able to get the compiled file to you quicker. I suggest requesting OpenVPN be added to the repos here:
http://linhes.org/projects/linhes/issues

Otherwise we are tampering with the system and you could have some issues as dependencies are updated, etc.

Was going to add the request to issues but don't see a way to do that.
Also will the package you created work with R8.6.1 ?

Thanks

tscholl, I really don't know. I installed everything per the post for 8.5.2 on my 8.6.0 system and I don't see any errors, but I do not have a way to test it. Here is the post with the link and install info if you want to try. I will try to add an issue as well.

http://forums.linhes.org/viewtopic.php? ... 22#p142222

Thanks for adding that as a feature. I finally figured out why I couldn't add it. I wasn't logged into LinHES Home.
Sigh..............

I finally had time to try and install the packages, both installed without any errors.

Then I ran the following:

My question is where do I get the information for the the config file? And where should it be located.

Any suggestions?
Thanks

I assume you would create the config file for your vpn. I have not investigated openvpn, though...

i am not running openvpn on linhes, however, i am running an openvpn server on a rpi. hopefully some of this info will be be of use.

upon installation, a startup script was created for me. the startup procedures between arch and rpi are different, but be that as it may, the startup script sets some things up for us. one of those items is the server config file

the startup script looks for server side .conf files in /etc/default/openvpn and /etc/openvpn/.*conf

the command line you are using to launch openvpn:



you indicate that the command returns "error opening config file". this could be as simple as not providing the correct path to the myvpn.opvn file you are trying to use. you may have to fully qualify the path to the myvpn.opvn file. however, when using the server side startup script the path and name of the conf file is setup for you (/etc/openvpn/server.conf).

my /etc/openvpn/server.conf file also adds "--daemon" to the startup, to push it into the background. you could add this to your command line or continue to use the standard unix "&" to push it in the background when running it via command line

the server.conf file is initially set up by the installation script, but can be hand edited if you need to change settings later. there are very many settings.

the daemon option, along with many other options can be found here:



this server.conf file sets up configurations for the server in addition to containing information used to generate client config (opvn) files

in order to create a client opvn file on a openvpn server running on my rpi, i reran the openvpn installation script and selected the option to add a new user.

the instructions i used are here:



these instructions have you run the openvpn-install.sh script. this script gave me several options, one of which was to create a new user, which will result in the creation of a new client config (opvn) file. however, a client opvn file was also created for me on the rpi upon initial install. as i am using an rpi, and do not have openvpn installed on linhes, i do not know where the openvpn-install.sh would be located on arch.

once you get the client.opvn file created, then you copy it to the client and cross your fingers and hope it works.

logs can be checked in the /etc/openvpn/openvpn-status.log file

hope this answers some of your questions

_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6

tscholl,

sorry, but i just reread the title of your post, where it clearly states that you want to connect to an openvpn server as a client, and you are not attempting to use your linhes as an openvpn server. my previous response incorrectly assumed you were trying to run an openvpn server on your linhes box

be that as it may, your basic question of where to get the client opvn config file is that you get it from the server that you are trying to connect to. the process to generate the client opvn file is mentioned in my previous post. you would then run



be sure to fully qualify the client file if it is not located in your current working directory

_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6

Thanks for the information provided, it did point me to running openvpn-install.sh
The bad news is that this file is not in any of the openvpn install directories.
Arggggg ... I'am still looking.

Ok I am making progress I was able to create a client.conf using

as a starting point and following this.

That was very helpful and it also helped to create the myvpn.ovpn.
Ran the following and got this result.

So I'm making progress. Not quite sure if I really need to do anything about using something other than the static key.

Also I'm really no sure that it is working. After I start openvpn and I go to whatsmyip.org it is still showing the same ip address as before.

Thanks welner for pointing me in the right direction.

based on the output, it appears that you are attempting to connect to a hosted server at midphase.com that is running an openvpn server, and your linhes box is the client.

if you want to redirect all traffic coming to/from the client and have "whatsmyipaddress" return the ip address of the server try this:

https://openvpn.net/community-resources/how-to/#routing-all-client-traffic-including-web-traffic-through-the-vpn

however, please note that the example shows this being set at the server level and being pushed out to the client. i don't know if you can force this setting at the client level without the server being set up for it (there is a warning in the section)

if you did connect using the current configuration, you should have access to boxes on the network the server is on and ifconfig -a will show a tun0 device

_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6

Sorry for the delay in getting back to you, I looked over your post and ran

ifconfig -a

It does not return anything for a tun0 device so I thinking I still have a configuration issue somewhere.