Ubuntu OpenVPN Server and Industrial VPN Router OpenVPN Client :
Dear Admin ,
I am trying to configure Server Client in OpenVPN where :
Server is UBUNTU Linux 14.04 and Client is a Hardware ( Industrial VPN Router eWON )
The client is showing the healthy VPN Connection but the Server is unable to ping the client . I am attaching the files ( server.ovpn & client.ovpn ) :
SERVER.CONF
#################################################
#Sample OpenVPN 2.0 config file for
#multi-client server.
#This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# "C:\Program Files\OpenVPN\config\foo.key" #
# #
# Comments are preceded with "#' or ";' #
#################################################
# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d
# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 443
# TCP or UDP server?
;proto udp
proto tcp
# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap
# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.crt
key server.key # This file should be kept secret
# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
dh dh2048.pem
# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0
# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt
# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses. You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge
# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"
# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).
# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.
# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2
# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script
# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
push "redirect-gateway def1 bypass-dhcp"
# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
push "dhcp-option DNS 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"
# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
client-to-client
# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
duplicate-cn
# The keepalive directive causes ping-like
# messags to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120
# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be "0'
# on the server and "1' on the clients.
;tls-auth ta.key 0 # This file is secret
# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC # Blowfish (default)
;cipher AES-128-CBC # AES
;cipher DES-EDE3-CBC # Triple-DES
# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo
# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100
# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nogroup
# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun
# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log
# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
;log openvpn.log
;log-append openvpn.log
# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3
# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20
CLIENT.OVPN
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################
# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client
# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap
# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
;proto udp
proto tcp
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote 125.19.78.182 443
;remote my-server-2 1194
# Choose a random host from the remote
# list for load-balancing. Otherwise
# try hosts in the order specified.
;remote-random
# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite
# Most clients don't need to bind to
# a specific local port number.
nobind
# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nogroup
# Try to preserve some state across restarts.
persist-key
persist-tun
# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]
# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings
# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
ca usr/ca.crt
cert usr/SSMANKU.crt
key usr/SSMANKU.key
# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". This is an
# important precaution to protect against
# a potential attack discussed here:
# http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
ns-cert-type server
# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1
# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo
# Set log file verbosity.
verb 3
# Silence repeating messages
;mute 20
ERROR IN THE CLIENT :
Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:5: topology (2.0.9)
Options error: unknown --redirect-gateway flag: bypass-dhcp
PUSH: Received control message: "PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 208.67.222.222,dhcp-option DNS 208.67.220.220,route 10.8.0.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.10 10.8.0.9'
Please Assist !
Thanks
-
Hi kyle,
My settings in var file are correct.I already uncommented that lines.
And I change the verb to 9 there.
Check server log file after changing verb 9 from verb 3. Is it correct ?
And then i connect my flexy to VPN Server but it still shows VPN Connection is not configured.
It gives me an error message in real time logging like:Options error: Unrecognized option or missing parameter(s) in /var/run/OpenVPN-qyhtri:1: client (2.0.9)
What can i do to resolve this?
Thank you in advance
Server.log (23 KB)
0 -
Hi Kyle, Please check the ewon configurations. Is it correct or not ?
It is still shows VPN Configuration is not connected.
Thank you in advance.
MOVED TO STAFF NOTE (229 KB)
0 -
Hi kyle
Is eFive connected with other openvpn compatible client?0 -
Your comcfg file does not point to your hms_client.ovpn file. You need to change this setting in comcfg:
VPNCfgFile:+/usr/hms_client.ovpn
It also appears there is a routing problem where the client cannot reach the server.
I'm not exactly sure what you are asking. The eFive is basically an OpenVPN server with our web interface on top of it. It is for use with the eWON clients such as Cosy and Flexy devices.
I haven't had a lot of time to go over this. At this current time we don't officially support using your own OpenVPN server.
Kyle
0 -
Hi kyle
I have config this setting VPNCfgFile:+/usr/hms_client.ovpn in my comcfg.txt
But also it shows vpn connection is not configured.
0 -
Hi kyle,
I have error like Options error: Unrecognized option or missing parameter(s) in /var/run/OpenVPN-qyhtri:1: client (2.0.9) after config VPNCfgFile:+/usr/hms_client.ovpn in comcfg.txt. How can i solve this ?
How can i solve that routing problem where the client can jot reach the server ?
Thank you in advance
0 -
Please send a new backup.
Please remove last 2 lines in your hms_client.ovpn file
You're on your own with this. Can you ping the Flexy from the OpenVPN server? If not, find out why.
0 -
I attached a new backup of flexy. Check it & revert back.
After removing two lines in my hms_client.ovpn file i also have same error like Options error: Unrecognized option or missing parameter(s) in /var/run/OpenVPN-qyhtri:1: client (2.0.9). I also check the ping from Openvpn server to flexy. It looks fine.
Which version of openvpn use for communication for the same?MOVED TO STAFF NOTE (336 KB)
0 -
Hey kyle,
We have one customer that have their own cloud (amazon AWS server )and wants to communicate with eWON rather than talk2M
Is it possible to connect flexy with third party amazon AWS server ?
They have an urgent requirement like this:can u help me as soon as possible?
And please give us the feasibility of the same.
0 -
Yes, you can run OpenVPN on public cloud. However, it is not officially supported by HMS. The OpenVPN instructions above were put together by the Americas region (who runs hms.how). If you have a project where you need urgent support, you need to contact and work with your local HMS support team. You can open a ticket with them by going to https://mysupport.hms.se . Since you are in India, I am unable to officially take your case, but I can provide some support through the forum. I would recommend starting fresh with the above instructions being especially careful to complete each step. Your settings look ok but something must be wrong with your keys. I am going to be working on cleaning up the instructions and making them easier to follow in the future.
0 -
Hi kyle,
I have tested hms_client.ovpn file (Ubuntu VPN Client) with Ubuntu VPN Server. It communicates fine and i got ping from Ubuntu VPN Client to Ubuntu VPN Server.
I have tested that same with Windows VPN Client & Windows VPN Server and i got the same result. It communicates fine.So, I Guess there is no issue with keys.
If I use the same Server & Client configuration files in flexy it gives me an error message like Options error: Unrecognized option or missing parameter(s) in /var/run/OpenVPN-qyhtri:1: client (2.0.9).
I am using openvpn version 2.4.0. Is flexy supports the openvpn version 2.4.0 ?
I have attached Server & Client log files and Screenshots of tun network appears after Successfully run the code.
Please share your views for the same.
Serverlog.txt (22.3 KB)
Clientlog.txt (1022 Bytes)
0 -
Hi kyle,
Gentle Reminder:
0 -
My set up was with firmware version 13.0. Can you try with that firmware?
0 -
I will try and revert you:
I am using 2.4.0 openvpn server:Is flexy compitable with openvpn version 2.4.0 ?
Because in one document of hms i read eWon is based on openvpn version 2.0. it may not work in higher version of openvpn.
0 -
Yes, it has been tested with 2.4. Make sure to make a backup of the eWON because when reverting it will clear the settings.
0 -
I have update the draft of the OpenVPN Server Configuration App Note to make it easier to follow and more general for different types of infrastructure. Please keep in mind that you should have prior experience with OpenVPN and Linux networking before attempting to implement this solution, and it is not officially supported by HMS at this time, just a general guide for those looking to implement their own OpenVPN infrastructure instead of using our Talk2M platform.
openVPN App Note Rev 2.pdf (287.5 KB)
0 -
Hi kyle,
Thank you for the support.
I have successfully connect eWon with third party server.
But I got stuck at one place. I can't access the other end of the LAN port of eWon.
Should we get the LAN and WAN routing capabilities with such type of third party cloud VPN service that we did with the native Talk2M server?
0 -
No, not by default. Talk2M uses it's own highly customized configuration. You will have to configure your server's routing and firewall settings for your own application. You can refer to the Digital Ocean guide's Step 6 for some information on that. I would like to eventually create a guide to illustrate some sample configurations but I don't have time atm. Keep in mind, by default the clients cannot communicate with each other. To enable you will need to un-comment "client-to-client" in the server.conf file. The server.conf file contains a lot of information as well, so read through that and here is another good source of information: https://wiki.archlinux.org/index.php/OpenVPN
This is the reason that I advise anyone considering building their own OpenVPN infrastructure to have prior OpenVPN and Linux networking experience, or be prepared to do a lot of homework.
0 -
Latest Version :
openVPN App Note Rev4.2.pdf (469.9 KB)
0
Please sign in to leave a comment.
Comments
49 comments