Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 8 of 8

Thread: Guide to make OpenVPN work on VIX2.4

  1. #1

    Title
    Forum Supporter
    Donated Member
    Join Date
    Jun 2011
    Posts
    500
    Thanks
    92
    Thanked 39 Times in 29 Posts

    Guide to make OpenVPN work on VIX2.4

    Ok mates It seems I've found the solution for the OpenVPN issue. Reading previous posts above I noticed that they were reffering to a multi user configuration.
    I mean one OpenVPN server and many different OpenVPN clients.

    My discoveries applies to a p2p OpenVPN connection. So further implementation may be necessary.

    ------------------------------------------
    OPENVPN SERVER CONFIGURATION
    ------------------------------------------
    Let's go:
    For what I've discovered it's essential to generate the *.key file right from the enigma2 receiver (In this case I own a Vu+DUO).
    To do this here are the steps:
    Make sure OpenVPN is installed (starting from Vix 2.4 you have to go to Network Configuration, choose OpenVPN and it'll ask to install) then
    1 - telnet to you receiver
    2 - type and send: cd /etc/init.d
    3 - issue the following: openvpn -- genkey --secret /var/etc/openvpn/keys/name.key
    at this point your .key file is generated

    Time to set up the server .conf file. (put it via FTP in /etc/openvpn/)
    Make sure that for a p2p OpenVpn connection you have only the *.key in the /keys subfolder, nothing else is needed.
    So edit the server.conf like this:

    dev tun0
    ifconfig 10.8.0.1 10.8.0.2
    port 1150
    keepalive 10 120
    verb 5
    secret /etc/openvpn/keys/name.key
    log /etc/openvpn/openvpn.log


    notes:
    A-the ip address can be assigned as you wish in a private range. Just note the colours of the two ips. They'll be switched in the client configuration.
    B-the port number has to be opened for port forwarding on you router.
    C-the log file is useful to understand if anything is not workin. Be careful it can get huge and fill up the flash memory. So after everyting is ok just delete it and disble the line in the config file (just put a # at the beginning of it)

    Is now time to make the openvpn start:
    make sure to be in the cd /etc/init.d directory:
    issue: /etc/init.d/openvpn start
    at this point your openVPN should be running, and in telnet if you issue ps command you'll get the process list and it should write near the end the following something like this line:
    1134 root 4180 S /usr/sbin/openvpn --daemon --writepid /var/run/openv

    Infact, if you go in the OpenVPN panel, this time you'll see the GREEN label saying: Running
    openscr.jpg

    ------------------------------------------
    OPENVPN CLIENT CONFIGURATION
    ------------------------------------------
    For the client side, make sure OpenVPN is installed, then you shoud ftp in it and place the client.conf file in /etc/openvpn/) and the .key file generated previously on the server in the /etc/openvpn/key folder.
    The client config file should be like this:
    dev tun0
    remote ip-address
    port 1150
    ifconfig 10.8.0.2 10.8.0.1
    resolv-retry infinite
    persist-tun
    persist-key
    verb 5
    secret /etc/openvpn/keys/name.key
    log /etc/openvpn/openvpn.log


    notes:
    D- ip-address is the actual ip address of the server box. If you don't have a static ip you should use a dyndns or similar service.
    E- as you can se the openvpn ips are inverted here.
    F- since this is a client conf the port number just tells the client on which port to contact the server. If the client is behind a firewall you don't need to forward this port.
    ---------------------------------------------
    ---------------------------------------------

    A suggestion/request for VIX developers:
    could be possible to add the feature to automatically generate the *.key as a script within the openvpn panel?
    Maybe just after the installation take place.
    Or better structure the panel to execute the script to generate a .key file or a basic .conf file.

  2. The Following 9 Users Say Thank You to MarsArtis For This Useful Post:

    awacs (19-03-15),ferrari312 (15-01-13),formianodicastellone (29-06-13),judge (31-05-12),Larry-G (31-05-12),Maxwell (31-05-12),punisher (31-05-12),sat gr (20-12-13),Sicilian (01-06-12)

  3. #2
    Larry-G's Avatar
    Title
    V.I.P
    Donated Member
    Join Date
    May 2010
    Posts
    32,542
    Thanks
    7,824
    Thanked 22,937 Times in 12,378 Posts
    made a sticky, thanks for the tutorial.
    My posts contain my own personal thoughts and opinions, they do not represent those of any organisation or group but my own.

    If you don't like what I post, Don't read it.

    SIMPLES.

  4. The Following 2 Users Say Thank You to Larry-G For This Useful Post:

    davis (11-10-14),Sicilian (01-06-12)

  5. #3

    Title
    Forum Supporter
    Donated Member
    Join Date
    Jun 2011
    Posts
    500
    Thanks
    92
    Thanked 39 Times in 29 Posts
    your welcome Phoenix.
    I hope I can help better for the development of the VIX image.

  6. #4

    Title
    Junior Member
    Join Date
    Jul 2012
    Posts
    1
    Thanks
    0
    Thanked 2 Times in 1 Post

    Witopia VPN

    Just a wee guide to setting this up using Witopia VPN - This requires having a paid subscription to Witopia Personal VPN Pro

    1. Login to your Witopia account - https://my.witopia.net/dashboard and click on "Download Client Software".

    2. Download the Zip file that appears in the pop-up window and unzip on your computer.

    3. Open up the unzipped folder and open the "SampleConfig.txt" file.

    4. Edit the line that reads - "remote [REPLACE WITH SERVER NAME] 1194" and add in a server of your preferred VPN location. These can be found here - https://www.witopia.net/?faq-item=op...eway-locations

    for example remote vpn.newyork.witopia.net 1194

    5. Rename the "SampleConfig.txt" to "Client.conf"

    6. FTP into your box and upload all the files in the folder to /etc/openvpn

    The folder /etc/openvpn should therefore have the following file:

    ***.crf (filename is individual to each user)
    ***.key (filename is individual to each user)
    Client.conf
    ca.crt


    If you want to enable logging, edit the Client.conf file and add the line
    log /etc/openvpn/openvpn.log

  7. The Following 2 Users Say Thank You to brobert99 For This Useful Post:

    marand (31-07-13),uhustic (24-12-16)

  8. #5

    Title
    Senior Member
    Join Date
    May 2013
    Posts
    256
    Thanks
    25
    Thanked 22 Times in 19 Posts
    is there anyway to allow openvpn to connect to vpn connection but also allow me to dial into the server on the box?

  9. The Following User Says Thank You to Coldfire For This Useful Post:

    awacs (19-03-15)

  10. #6

    Title
    Senior Member
    Join Date
    May 2013
    Posts
    256
    Thanks
    25
    Thanked 22 Times in 19 Posts
    anyone? please

  11. The Following User Says Thank You to Coldfire For This Useful Post:

    awacs (19-03-15)

  12. #7

    Title
    Senior Member
    Join Date
    Apr 2010
    Posts
    101
    Thanks
    8
    Thanked 28 Times in 19 Posts

    Re: Guide to make OpenVPN work on VIX2.4

    Are you trying to run openvpn as client and server concurrently?

    Not sure it's possible or, at least, practical. A bit of googling didn't bring up any success stories.

    I just run an openvpn virtual machine on my media server to gain access from outside.

    Sent from my GT-I9300 using Tapatalk 2

  13. #8

    Title
    Senior Member
    Join Date
    May 2013
    Posts
    256
    Thanks
    25
    Thanked 22 Times in 19 Posts
    only running it as a client

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.