[oconf] BB troubles on configuration OpenVPN

Need help configuring your VPN? Just post here and you'll get that help.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
gianpierobottini
OpenVpn Newbie
Posts: 4
Joined: Fri Sep 22, 2017 8:54 am

[oconf] BB troubles on configuration OpenVPN

Post by gianpierobottini » Fri Sep 22, 2017 9:16 am

Hello everyone.
I have just configured openvpn and the connection is ok
(the windows client has the message connected with the new ip address)
BUT it seems to be no packet exchange between client and server (for example the ping doesnt work from server to client and from client to server)
The purpose of my vpn is to connect some windows clients to enterprise network.
I'm very newbie and probably my problem is trivial
Here are the two configuration files and the log files
Thanks for your help
Gian

this is my client.ovpn
client
dev tap
proto udp
remote XXX.XXX.XXX.XXX 1194 # - Your server IP and OpenVPN Port
resolv-retry infinite
nobind
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
persist-key
persist-tun
ca ca.crt
cert client.crt
key client.key
auth-user-pass
comp-lzo no
reneg-sec 0
verb 3

this is my 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 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 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 dh2048.pem 2048
#dh dh2048.pem
dh dh.pem
server-bridge 192.168.0.254 255.255.255.0 192.168.0.180 192.168.0.200
# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# 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 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"

# 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.
# commentato 11/9/2017 GPB
#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.
# Note that 2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC

# Enable compression on the VPN link and push the
# option to the client (2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"

# For compression compatible with older clients use comp-lzo
# 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 nobody

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

# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

# Notify the client that when the server restarts so it
# can automatically reconnect.
explicit-exit-notify 1

client log

Fri Sep 22 10:59:16 2017 OpenVPN 2.4.3 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Jul 14 2017
Fri Sep 22 10:59:16 2017 Windows version 6.2 (Windows 8 or greater) 64bit
Fri Sep 22 10:59:16 2017 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.10
Enter Management Password:
Fri Sep 22 10:59:16 2017 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Fri Sep 22 10:59:16 2017 Need hold release from management interface, waiting...
Fri Sep 22 10:59:16 2017 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Fri Sep 22 10:59:16 2017 MANAGEMENT: CMD 'state on'
Fri Sep 22 10:59:16 2017 MANAGEMENT: CMD 'log all on'
Fri Sep 22 10:59:16 2017 MANAGEMENT: CMD 'echo all on'
Fri Sep 22 10:59:16 2017 MANAGEMENT: CMD 'hold off'
Fri Sep 22 10:59:16 2017 MANAGEMENT: CMD 'hold release'
Fri Sep 22 10:59:20 2017 MANAGEMENT: CMD 'username "Auth" "gbottini"'
Fri Sep 22 10:59:20 2017 MANAGEMENT: CMD 'password [...]'
Fri Sep 22 10:59:20 2017 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Fri Sep 22 10:59:20 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]2.238.73.46:1194
Fri Sep 22 10:59:20 2017 Socket Buffers: R=[65536->65536] S=[64512->64512]
Fri Sep 22 10:59:20 2017 UDP link local: (not bound)
Fri Sep 22 10:59:20 2017 UDP link remote: [AF_INET]2.238.73.46:1194
Fri Sep 22 10:59:20 2017 MANAGEMENT: >STATE:1506070760,WAIT,,,,,,
Fri Sep 22 10:59:20 2017 MANAGEMENT: >STATE:1506070760,AUTH,,,,,,
Fri Sep 22 10:59:20 2017 TLS: Initial packet from [AF_INET]2.238.73.46:1194, sid=90cf9d7d e48874ff
Fri Sep 22 10:59:20 2017 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Sep 22 10:59:21 2017 VERIFY OK: depth=1, CN=Easy-RSA CA
Fri Sep 22 10:59:21 2017 VERIFY OK: depth=0, CN=server
Fri Sep 22 10:59:21 2017 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1574', remote='link-mtu 1590'
Fri Sep 22 10:59:21 2017 WARNING: 'cipher' is used inconsistently, local='cipher BF-CBC', remote='cipher AES-256-CBC'
Fri Sep 22 10:59:21 2017 WARNING: 'keysize' is used inconsistently, local='keysize 128', remote='keysize 256'
Fri Sep 22 10:59:21 2017 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Fri Sep 22 10:59:21 2017 [server] Peer Connection Initiated with [AF_INET]2.238.73.46:1194
Fri Sep 22 10:59:22 2017 MANAGEMENT: >STATE:1506070762,GET_CONFIG,,,,,,
Fri Sep 22 10:59:22 2017 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Fri Sep 22 10:59:22 2017 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route-gateway 192.168.0.254,ping 10,ping-restart 120,ifconfig 192.168.0.180 255.255.255.0,peer-id 0,cipher AES-256-GCM'
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: timers and/or timeouts modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: --ifconfig/up options modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: route options modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: route-related options modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: peer-id set
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: adjusting link_mtu to 1657
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: data channel crypto options modified
Fri Sep 22 10:59:22 2017 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Sep 22 10:59:22 2017 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Sep 22 10:59:22 2017 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Sep 22 10:59:22 2017 interactive service msg_channel=540
Fri Sep 22 10:59:22 2017 ROUTE_GATEWAY 192.168.43.1/255.255.255.0 I=6 HWADDR=40:f0:2f:2c:d0:81
Fri Sep 22 10:59:22 2017 open_tun
Fri Sep 22 10:59:22 2017 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{3BA581A7-E53D-4328-92CF-ADDF1049A80C}.tap
Fri Sep 22 10:59:22 2017 TAP-Windows Driver Version 9.21
Fri Sep 22 10:59:22 2017 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.0.180/255.255.255.0 on interface {3BA581A7-E53D-4328-92CF-ADDF1049A80C} [DHCP-serv: 192.168.0.0, lease-time: 31536000]
Fri Sep 22 10:59:22 2017 Successful ARP Flush on interface [30] {3BA581A7-E53D-4328-92CF-ADDF1049A80C}
Fri Sep 22 10:59:22 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Sep 22 10:59:22 2017 MANAGEMENT: >STATE:1506070762,ASSIGN_IP,,192.168.0.180,,,,
Fri Sep 22 10:59:27 2017 TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up
Fri Sep 22 10:59:27 2017 C:\WINDOWS\system32\route.exe ADD 2.238.73.46 MASK 255.255.255.255 192.168.43.1
Fri Sep 22 10:59:27 2017 Route addition via service succeeded
Fri Sep 22 10:59:27 2017 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 192.168.0.254
Fri Sep 22 10:59:27 2017 Route addition via service succeeded
Fri Sep 22 10:59:27 2017 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 192.168.0.254
Fri Sep 22 10:59:27 2017 Route addition via service succeeded
Fri Sep 22 10:59:27 2017 Initialization Sequence Completed
Fri Sep 22 10:59:27 2017 MANAGEMENT: >STATE:1506070767,CONNECTED,SUCCESS,192.168.0.180,2.238.73.46,1194,,

server log (/var/log/messages)
Sep 22 10:59:21 DA openvpn[10746]: MULTI: multi_create_instance called
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 Re-using SSL/TLS context
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 LZO compression initializing
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 Control Channel MTU parms [ L:1654 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 Data Channel MTU parms [ L:1654 D:1450 EF:122 EB:411 ET:32 EL:3 ]
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 Local Options String (VER=V4): 'V4,dev-type tap,link-mtu 1590,tun-mtu 1532,proto UDPv4,comp-lzo,cipher AES-256-CBC,auth SHA1,keysize 256,key-method 2,tls-server'
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 Expected Remote Options String (VER=V4): 'V4,dev-type tap,link-mtu 1590,tun-mtu 1532,proto UDPv4,comp-lzo,cipher AES-256-CBC,auth SHA1,keysize 256,key-method 2,tls-client'
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 TLS: Initial packet from [AF_INET]91.253.242.246:33282, sid=f5d57d45 b25ead03
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 VERIFY OK: depth=1, CN=Easy-RSA CA
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 VERIFY OK: depth=0, CN=client
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_VER=2.4.3
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_PLAT=win
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_PROTO=2
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_NCP=2
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_LZ4=1
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_LZ4v2=1
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_LZO=1
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_COMP_STUB=1
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_COMP_STUBv2=1
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_TCPNL=1
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 peer info: IV_GUI_VER=OpenVPN_GUI_11
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1590', remote='link-mtu 1574'
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher BF-CBC'
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128'
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Sep 22 10:59:21 DA openvpn[10746]: 91.253.242.246:33282 [client] Peer Connection Initiated with [AF_INET]91.253.242.246:33282
Sep 22 10:59:21 DA openvpn[10746]: client/91.253.242.246:33282 MULTI_sva: pool returned IPv4=192.168.0.180, IPv6=(Not enabled)
Sep 22 10:59:22 DA openvpn[10746]: client/91.253.242.246:33282 PUSH: Received control message: 'PUSH_REQUEST'
Sep 22 10:59:22 DA openvpn[10746]: client/91.253.242.246:33282 SENT CONTROL [client]: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route-gateway 192.168.0.254,ping 10,ping-restart 120,ifconfig 192.168.0.180 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Sep 22 10:59:22 DA openvpn[10746]: client/91.253.242.246:33282 Data Channel: using negotiated cipher 'AES-256-GCM'
Sep 22 10:59:22 DA openvpn[10746]: client/91.253.242.246:33282 Data Channel MTU parms [ L:1582 D:1450 EF:50 EB:411 ET:32 EL:3 ]
Sep 22 10:59:22 DA openvpn[10746]: client/91.253.242.246:33282 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Sep 22 10:59:22 DA openvpn[10746]: client/91.253.242.246:33282 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Sep 22 10:59:22 DA openvpn[10746]: client/91.253.242.246:33282 MULTI: Learn: 00:ff:3b:a5:81:a7 -> client/91.253.242.246:33282

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: [oconf] BB troubles on configuration OpenVPN

Post by TinCanTech » Fri Sep 22, 2017 11:18 am

Server config:

Code: Select all

port 1194
proto udp

dev tap

ca ca.crt
cert server.crt
key server.key  # This file should be kept secret

dh dh.pem
server-bridge 192.168.0.254 255.255.255.0 192.168.0.180 192.168.0.200

ifconfig-pool-persist ipp.txt


push "redirect-gateway def1 bypass-dhcp"

push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"

keepalive 10 120

cipher AES-256-CBC

comp-lzo

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

persist-key
persist-tun

status openvpn-status.log

verb 4

explicit-exit-notify 1
Client log:
gianpierobottini wrote:
Fri Sep 22, 2017 9:16 am
Fri Sep 22 10:59:21 2017 [server] Peer Connection Initiated with [AF_INET]2.238.73.46:1194
Fri Sep 22 10:59:22 2017 MANAGEMENT: >STATE:1506070762,GET_CONFIG,,,,,,
Fri Sep 22 10:59:22 2017 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Fri Sep 22 10:59:22 2017 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route-gateway 192.168.0.254,ping 10,ping-restart 120,ifconfig 192.168.0.180 255.255.255.0,peer-id 0,cipher AES-256-GCM'
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: timers and/or timeouts modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: --ifconfig/up options modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: route options modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: route-related options modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: peer-id set
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: adjusting link_mtu to 1657
Fri Sep 22 10:59:22 2017 OPTIONS IMPORT: data channel crypto options modified
Fri Sep 22 10:59:22 2017 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Sep 22 10:59:22 2017 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Sep 22 10:59:22 2017 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Sep 22 10:59:22 2017 interactive service msg_channel=540
Fri Sep 22 10:59:22 2017 ROUTE_GATEWAY 192.168.43.1/255.255.255.0 I=6 HWADDR=40:f0:2f:2c:d0:81
Fri Sep 22 10:59:22 2017 open_tun
Fri Sep 22 10:59:22 2017 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{3BA581A7-E53D-4328-92CF-ADDF1049A80C}.tap
Fri Sep 22 10:59:22 2017 TAP-Windows Driver Version 9.21
Fri Sep 22 10:59:22 2017 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.0.180/255.255.255.0 on interface {3BA581A7-E53D-4328-92CF-ADDF1049A80C} [DHCP-serv: 192.168.0.0, lease-time: 31536000]
Fri Sep 22 10:59:22 2017 Successful ARP Flush on interface [30] {3BA581A7-E53D-4328-92CF-ADDF1049A80C}
Fri Sep 22 10:59:22 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Sep 22 10:59:22 2017 MANAGEMENT: >STATE:1506070762,ASSIGN_IP,,192.168.0.180,,,,
Fri Sep 22 10:59:27 2017 TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up
Fri Sep 22 10:59:27 2017 C:\WINDOWS\system32\route.exe ADD 2.238.73.46 MASK 255.255.255.255 192.168.43.1
Fri Sep 22 10:59:27 2017 Route addition via service succeeded
Fri Sep 22 10:59:27 2017 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 192.168.0.254
Fri Sep 22 10:59:27 2017 Route addition via service succeeded
Fri Sep 22 10:59:27 2017 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 192.168.0.254
Fri Sep 22 10:59:27 2017 Route addition via service succeeded
Fri Sep 22 10:59:27 2017 Initialization Sequence Completed
Fri Sep 22 10:59:27 2017 MANAGEMENT: >STATE:1506070767,CONNECTED,SUCCESS,192.168.0.180,2.238.73.46,1194,,
gianpierobottini wrote:
Fri Sep 22, 2017 9:16 am
it seems to be no packet exchange between client and server (for example the ping doesnt work from server to client and from client to server)
Check your server & client windows firewalls to allow VPN packets ..

gianpierobottini
OpenVpn Newbie
Posts: 4
Joined: Fri Sep 22, 2017 8:54 am

Re: [oconf] BB troubles on configuration OpenVPN

Post by gianpierobottini » Fri Sep 22, 2017 12:40 pm

it does not seem like a firewall problem...I have stopped iptables on server and windows client on client....

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: [oconf] BB troubles on configuration OpenVPN

Post by TinCanTech » Fri Sep 22, 2017 1:25 pm

It looks exactly like a firewall problem .. not that it necessarily is ..

Post:

Code: Select all

# brctl show
# ifconfig
remove publicly identifiable data.

gianpierobottini
OpenVpn Newbie
Posts: 4
Joined: Fri Sep 22, 2017 8:54 am

Re: [oconf] BB troubles on configuration OpenVPN

Post by gianpierobottini » Mon Sep 25, 2017 10:23 am

ifconfig

~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:D0:C9:A3:F2:B6
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:c9ff:fea3:f2b6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1369 errors:0 dropped:0 overruns:0 frame:0
TX packets:409 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:239705 (234.0 KiB) TX bytes:54933 (53.6 KiB)

eth1 Link encap:Ethernet HWaddr 00:D0:C9:A3:F2:B7
inet addr:192.168.0.104 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:c9ff:fea3:f2b7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:251 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21410 (20.9 KiB) TX bytes:688 (688.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2716 (2.6 KiB) TX bytes:2716 (2.6 KiB)

virbr0 Link encap:Ethernet HWaddr 52:54:00:F1:04:19
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[root@DA ~]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.525400f10419 yes virbr0-nic

[root@DA ~]# service iptables status
iptables: Firewall is not running.


gianpierobottini
OpenVpn Newbie
Posts: 4
Joined: Fri Sep 22, 2017 8:54 am

Re: [oconf] BB troubles on configuration OpenVPN

Post by gianpierobottini » Mon Sep 25, 2017 1:23 pm

ok routing for the moment can be enough..probably it's easier ... now i try ...thanks a lot .

Post Reply