OpenVPN not connectingConnection to openVPN Access ServerOpenvpn server on ubuntu and clients on WindowsUse...

Am I not good enough for you?

Touchscreen-controlled dentist office snowman collector game

When two POV characters meet

How do anti-virus programs start at Windows boot?

Sword in the Stone story where the sword was held in place by electromagnets

"However" used in a conditional clause?

Want to switch to tankless, but can I use my existing wiring?

What is the definition of "Natural Selection"?

What exactly is the purpose of connection links straped between the rocket and the launch pad

Word for a person who has no opinion about whether god exists

Unreachable code, but reachable with exception

Silly Sally's Movie

What wound would be of little consequence to a biped but terrible for a quadruped?

Why must traveling waves have the same amplitude to form a standing wave?

Make a transparent 448*448 image

what does the apostrophe mean in this notation?

Replacing Windows 7 security updates with anti-virus?

Confusion with the nameplate of an induction motor

Potentiometer like component

Time dilation for a moving electronic clock

Humans have energy, but not water. What happens?

Is all copper pipe pretty much the same?

What happens with multiple copies of Humility and Glorious Anthem on the battlefield?

Is it illegal in Germany to take sick leave if you caused your own illness with food?



OpenVPN not connecting


Connection to openVPN Access ServerOpenvpn server on ubuntu and clients on WindowsUse Steam's In-Home Streaming across VPN (OpenVPN)?Difference between OpenVPN Access Server and just OpenVPNHow To setup Asterisk VoIP server over OpenVPN in Tor hidden serviceIn OpenVPN 2.4, how do I support multiple ciphers?OpenVPN Attempting to establish TCP connection failed: Connection refusedCannot Access Remote Network IP & Host from Openvpn serverMy openvpn clients connects to server with .ovpn+ca.crt files onlyOpenVPN connects but can not connect to local network resources or browse internet













1















There have been a number of post similar to this, but none seem to satisfy my need. Plus I am a Ubuntu newbie. I followed this tutorial to completely set up OpenVPN on Ubuntu 12.04 server. Here is my server.conf file



#################################################
# 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 192.168.13.8

# 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 1194

# TCP or UDP server?
proto tcp
;proto udp

# "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 tap0
up "/etc/openvpn/up.sh br0"
down "/etc/openvpn/down.sh br0"
;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 "/etc/openvpn/ca.crt"
cert "/etc/openvpn/server.crt"
key "/etc/openvpn/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 dh1024.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 192.168.13.101 255.255.255.0 192.168.13.105 192.168.13.200

# 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.13.1 255.255.255.0"
push "dhcp-option DNS 192.168.13.201"
push "dhcp-option DOMAIN blahblah.dyndns-wiki.com"
;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
# messages 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 FilesOpenVPNlog" 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


I am using Windows 7 as the Client and set that up accordingly using the OpenVPN GUI. That conf file is as follows:



##############################################
# 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 tap0
up "/etc/openvpn/up.sh br0"
down "/etc/openvpn/down.sh br0"
;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 tcp
;proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
blahblah.dyndns-wiki.com 1194
;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 nobody

# 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 "C:\Program FilesOpenVPNconfig\ca.crt"
cert "C:\Program FilesOpenVPNconfig\ChadMWade-THINK.crt"
key "C:\Program FilesOpenVPNconfig\ChadMWade-THINK.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


Not sure whats left to do.










share|improve this question














bumped to the homepage by Community 7 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    1















    There have been a number of post similar to this, but none seem to satisfy my need. Plus I am a Ubuntu newbie. I followed this tutorial to completely set up OpenVPN on Ubuntu 12.04 server. Here is my server.conf file



    #################################################
    # 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 192.168.13.8

    # 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 1194

    # TCP or UDP server?
    proto tcp
    ;proto udp

    # "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 tap0
    up "/etc/openvpn/up.sh br0"
    down "/etc/openvpn/down.sh br0"
    ;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 "/etc/openvpn/ca.crt"
    cert "/etc/openvpn/server.crt"
    key "/etc/openvpn/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 dh1024.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 192.168.13.101 255.255.255.0 192.168.13.105 192.168.13.200

    # 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.13.1 255.255.255.0"
    push "dhcp-option DNS 192.168.13.201"
    push "dhcp-option DOMAIN blahblah.dyndns-wiki.com"
    ;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
    # messages 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 FilesOpenVPNlog" 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


    I am using Windows 7 as the Client and set that up accordingly using the OpenVPN GUI. That conf file is as follows:



    ##############################################
    # 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 tap0
    up "/etc/openvpn/up.sh br0"
    down "/etc/openvpn/down.sh br0"
    ;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 tcp
    ;proto udp

    # The hostname/IP and port of the server.
    # You can have multiple remote entries
    # to load balance between the servers.
    blahblah.dyndns-wiki.com 1194
    ;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 nobody

    # 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 "C:\Program FilesOpenVPNconfig\ca.crt"
    cert "C:\Program FilesOpenVPNconfig\ChadMWade-THINK.crt"
    key "C:\Program FilesOpenVPNconfig\ChadMWade-THINK.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


    Not sure whats left to do.










    share|improve this question














    bumped to the homepage by Community 7 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      1












      1








      1








      There have been a number of post similar to this, but none seem to satisfy my need. Plus I am a Ubuntu newbie. I followed this tutorial to completely set up OpenVPN on Ubuntu 12.04 server. Here is my server.conf file



      #################################################
      # 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 192.168.13.8

      # 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 1194

      # TCP or UDP server?
      proto tcp
      ;proto udp

      # "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 tap0
      up "/etc/openvpn/up.sh br0"
      down "/etc/openvpn/down.sh br0"
      ;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 "/etc/openvpn/ca.crt"
      cert "/etc/openvpn/server.crt"
      key "/etc/openvpn/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 dh1024.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 192.168.13.101 255.255.255.0 192.168.13.105 192.168.13.200

      # 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.13.1 255.255.255.0"
      push "dhcp-option DNS 192.168.13.201"
      push "dhcp-option DOMAIN blahblah.dyndns-wiki.com"
      ;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
      # messages 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 FilesOpenVPNlog" 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


      I am using Windows 7 as the Client and set that up accordingly using the OpenVPN GUI. That conf file is as follows:



      ##############################################
      # 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 tap0
      up "/etc/openvpn/up.sh br0"
      down "/etc/openvpn/down.sh br0"
      ;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 tcp
      ;proto udp

      # The hostname/IP and port of the server.
      # You can have multiple remote entries
      # to load balance between the servers.
      blahblah.dyndns-wiki.com 1194
      ;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 nobody

      # 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 "C:\Program FilesOpenVPNconfig\ca.crt"
      cert "C:\Program FilesOpenVPNconfig\ChadMWade-THINK.crt"
      key "C:\Program FilesOpenVPNconfig\ChadMWade-THINK.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


      Not sure whats left to do.










      share|improve this question














      There have been a number of post similar to this, but none seem to satisfy my need. Plus I am a Ubuntu newbie. I followed this tutorial to completely set up OpenVPN on Ubuntu 12.04 server. Here is my server.conf file



      #################################################
      # 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 192.168.13.8

      # 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 1194

      # TCP or UDP server?
      proto tcp
      ;proto udp

      # "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 tap0
      up "/etc/openvpn/up.sh br0"
      down "/etc/openvpn/down.sh br0"
      ;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 "/etc/openvpn/ca.crt"
      cert "/etc/openvpn/server.crt"
      key "/etc/openvpn/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 dh1024.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 192.168.13.101 255.255.255.0 192.168.13.105 192.168.13.200

      # 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.13.1 255.255.255.0"
      push "dhcp-option DNS 192.168.13.201"
      push "dhcp-option DOMAIN blahblah.dyndns-wiki.com"
      ;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
      # messages 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 FilesOpenVPNlog" 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


      I am using Windows 7 as the Client and set that up accordingly using the OpenVPN GUI. That conf file is as follows:



      ##############################################
      # 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 tap0
      up "/etc/openvpn/up.sh br0"
      down "/etc/openvpn/down.sh br0"
      ;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 tcp
      ;proto udp

      # The hostname/IP and port of the server.
      # You can have multiple remote entries
      # to load balance between the servers.
      blahblah.dyndns-wiki.com 1194
      ;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 nobody

      # 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 "C:\Program FilesOpenVPNconfig\ca.crt"
      cert "C:\Program FilesOpenVPNconfig\ChadMWade-THINK.crt"
      key "C:\Program FilesOpenVPNconfig\ChadMWade-THINK.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


      Not sure whats left to do.







      openvpn






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 7 '13 at 3:55









      LandArchLandArch

      180139




      180139





      bumped to the homepage by Community 7 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 7 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          You need to add the word "remote" before the servername in your Windows client config file.



          You have this line:
          blahblah.dyndns-wiki.com 1194



          It should be like this:
          remote blahblah.dyndns-wiki.com 1194






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f372326%2fopenvpn-not-connecting%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            You need to add the word "remote" before the servername in your Windows client config file.



            You have this line:
            blahblah.dyndns-wiki.com 1194



            It should be like this:
            remote blahblah.dyndns-wiki.com 1194






            share|improve this answer




























              0














              You need to add the word "remote" before the servername in your Windows client config file.



              You have this line:
              blahblah.dyndns-wiki.com 1194



              It should be like this:
              remote blahblah.dyndns-wiki.com 1194






              share|improve this answer


























                0












                0








                0







                You need to add the word "remote" before the servername in your Windows client config file.



                You have this line:
                blahblah.dyndns-wiki.com 1194



                It should be like this:
                remote blahblah.dyndns-wiki.com 1194






                share|improve this answer













                You need to add the word "remote" before the servername in your Windows client config file.



                You have this line:
                blahblah.dyndns-wiki.com 1194



                It should be like this:
                remote blahblah.dyndns-wiki.com 1194







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 28 '15 at 13:45









                Terence SmithTerence Smith

                1




                1






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f372326%2fopenvpn-not-connecting%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

                    Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

                    Simple Scan not detecting my scanner (Brother DCP-7055W)Brother MFC-L2700DW printer can print, can't...