[Newbie Inside] Bridge mode

Need help configuring your VPN? Just post here and you'll get that help.
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

[Newbie Inside] Bridge mode

Post by MetalicMan » Tue May 15, 2018 9:04 am

Hi there!

I'm trying to configure my 1st open vpn server for accessing a NAS over internet.
So I think bridge mode will work better for my purpose.


Open VPN installed on a Windows10 machine.

Bridged with TAP1, static IP 192.168.1.61


server
#################################################
#################################################
# 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 TAP1

# 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 quimialvpn.crt
key quimialvpn.key # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

# 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 192.168.1.61 255.255.0.0 192.168.1.40 192.168.1.50

# 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.1.60 0.0.0.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# 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.
# Note that v2.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 (v2.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 3

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

client
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
dev tap
;dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
;proto tcp
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote *********** 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 ca.crt
cert vpn.crt
key vpn.key

# Verify server certificate by checking that the
# certicate has the correct key usage set.
# 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 keyUsage set to
# digitalSignature, keyEncipherment
# and the extendedKeyUsage to
# serverAuth
# EasyRSA can do this for you.
remote-cert-tls 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.
# Note that v2.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.
# 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



Can get connection but cannot ping, and do nothing...

Can someone help me?

Thanks in advance,
Last edited by MetalicMan on Tue May 15, 2018 11:06 am, edited 1 time in total.

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 4877
Joined: Fri Jun 03, 2016 1:17 pm

Re: [Newbie Inside] Bridge mode

Post by TinCanTech » Tue May 15, 2018 10:01 am

MetalicMan wrote:
Tue May 15, 2018 9:04 am
server-bridge 192.168.1.61 255.255.0.0 192.168.1.40 192.168.1.50
server-bridge
The second "server-bridge" over writes the settings of the first "server-bridge" statement ..

Also, server-bridge should point to the default gateway of your server LAN not the server IP.

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Tue May 15, 2018 10:58 am

Thanks for the help.
I'm trying that right now and post feedback

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Tue May 15, 2018 11:05 am

Still no luck cannot ping either :(

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 4877
Joined: Fri Jun 03, 2016 1:17 pm

Re: [Newbie Inside] Bridge mode

Post by TinCanTech » Tue May 15, 2018 11:15 am


MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Tue May 15, 2018 11:27 am

Ok, got it working!! Thank you very much
I can now ping and browse via IP. Is there any way to get dns to working?

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Tue May 15, 2018 3:33 pm

I got it working by manually config DNS on the client computers!

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Tue May 15, 2018 3:55 pm

New problem.. After 20minutes working, I lost the connection.

I got this log on server, and I think the culprint is
Tue May 15 16:50:05 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]

Could someone point in the right direction?

Code: Select all

Tue May 15 15:49:39 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Tue May 15 15:49:39 2018 Windows version 6.2 (Windows 8 or greater) 64bit
Tue May 15 15:49:39 2018 library versions: OpenSSL 1.1.0h  27 Mar 2018, LZO 2.10
Enter Management Password:
Tue May 15 15:49:39 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Tue May 15 15:49:39 2018 Need hold release from management interface, waiting...
Tue May 15 15:49:39 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Tue May 15 15:49:39 2018 MANAGEMENT: CMD 'state on'
Tue May 15 15:49:39 2018 MANAGEMENT: CMD 'log all on'
Tue May 15 15:49:40 2018 MANAGEMENT: CMD 'echo all on'
Tue May 15 15:49:40 2018 MANAGEMENT: CMD 'bytecount 5'
Tue May 15 15:49:40 2018 MANAGEMENT: CMD 'hold off'
Tue May 15 15:49:40 2018 MANAGEMENT: CMD 'hold release'
Tue May 15 15:49:40 2018 NOTE: when bridging your LAN adapter with the TAP adapter, note that the new bridge adapter will often take on its own IP address that is different from what the LAN adapter was previously set to
Tue May 15 15:49:40 2018 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x.  Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Tue May 15 15:49:40 2018 Diffie-Hellman initialized with 2048 bit key
Tue May 15 15:49:40 2018 interactive service msg_channel=0
Tue May 15 15:49:40 2018 open_tun
Tue May 15 15:49:40 2018 TAP-WIN32 device [TAP1] opened: \\.\Global\{76375FAE-076E-4483-AB20-E149416F36FC}.tap
Tue May 15 15:49:40 2018 TAP-Windows Driver Version 9.21 
Tue May 15 15:49:40 2018 Sleeping for 10 seconds...
Tue May 15 15:49:50 2018 NOTE: FlushIpNetTable failed on interface [9] {76375FAE-076E-4483-AB20-E149416F36FC} (status=1168) : Elemento não encontrado.  
Tue May 15 15:49:50 2018 Could not determine IPv4/IPv6 protocol. Using AF_INET6
Tue May 15 15:49:50 2018 Socket Buffers: R=[65536->65536] S=[65536->65536]
Tue May 15 15:49:50 2018 setsockopt(IPV6_V6ONLY=0)
Tue May 15 15:49:50 2018 UDPv6 link local (bound): [AF_INET6][undef]:1194
Tue May 15 15:49:50 2018 UDPv6 link remote: [AF_UNSPEC]
Tue May 15 15:49:50 2018 MULTI: multi_init called, r=256 v=256
Tue May 15 15:49:50 2018 IFCONFIG POOL: base=192.168.25.40 size=11, ipv6=0
Tue May 15 15:49:50 2018 Initialization Sequence Completed
Tue May 15 15:49:50 2018 MANAGEMENT: >STATE:1526395790,CONNECTED,SUCCESS,,,,,
Tue May 15 15:49:51 2018 94.61.114.36 TLS: Initial packet from [AF_INET6]::ffff:94.61.114.36:6859, sid=72741bd9 795704f2
Tue May 15 15:49:51 2018 94.61.114.36 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Tue May 15 15:49:51 2018 94.61.114.36 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_VER=2.4.6
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_PLAT=win
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_PROTO=2
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_NCP=2
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_LZ4=1
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_LZ4v2=1
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_LZO=1
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_COMP_STUB=1
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_COMP_STUBv2=1
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_TCPNL=1
Tue May 15 15:49:51 2018 94.61.114.36 peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue May 15 15:49:51 2018 94.61.114.36 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Tue May 15 15:49:51 2018 94.61.114.36 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.61.114.36:6859
Tue May 15 15:49:51 2018 vpn/94.61.114.36 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Tue May 15 15:49:52 2018 vpn/94.61.114.36 PUSH: Received control message: 'PUSH_REQUEST'
Tue May 15 15:49:52 2018 vpn/94.61.114.36 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Tue May 15 15:49:52 2018 vpn/94.61.114.36 Data Channel: using negotiated cipher 'AES-256-GCM'
Tue May 15 15:49:52 2018 vpn/94.61.114.36 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 15:49:52 2018 vpn/94.61.114.36 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 15:49:52 2018 vpn/94.61.114.36 MULTI: Learn: 00:ff:d4:79:29:50 -> vpn/94.61.114.36
Tue May 15 15:49:56 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:64933, sid=bc626606 0eb31bf9
Tue May 15 15:49:56 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Tue May 15 15:49:56 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_VER=2.4.6
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_PLAT=win
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_PROTO=2
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_NCP=2
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_LZ4=1
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_LZ4v2=1
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_LZO=1
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_TCPNL=1
Tue May 15 15:49:56 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue May 15 15:49:56 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Tue May 15 15:49:56 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:64933
Tue May 15 15:49:56 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.41, IPv6=(Not enabled)
Tue May 15 15:49:57 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Tue May 15 15:49:57 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.41 255.255.255.0,peer-id 1,cipher AES-256-GCM' (status=1)
Tue May 15 15:49:57 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Tue May 15 15:49:57 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 15:49:57 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 15:49:58 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Tue May 15 16:22:23 2018 89.155.20.132 TLS: Initial packet from [AF_INET6]::ffff:89.155.20.132:59558, sid=fe28e085 d3b7084b
Tue May 15 16:22:23 2018 89.155.20.132 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Tue May 15 16:22:23 2018 89.155.20.132 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_VER=2.4.6
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_PLAT=win
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_PROTO=2
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_NCP=2
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_LZ4=1
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_LZ4v2=1
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_LZO=1
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_COMP_STUB=1
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_COMP_STUBv2=1
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_TCPNL=1
Tue May 15 16:22:23 2018 89.155.20.132 peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue May 15 16:22:23 2018 89.155.20.132 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Tue May 15 16:22:23 2018 89.155.20.132 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:89.155.20.132:59558
Tue May 15 16:22:23 2018 vpn/89.155.20.132 MULTI_sva: pool returned IPv4=192.168.25.42, IPv6=(Not enabled)
Tue May 15 16:22:24 2018 vpn/89.155.20.132 PUSH: Received control message: 'PUSH_REQUEST'
Tue May 15 16:22:24 2018 vpn/89.155.20.132 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.42 255.255.255.0,peer-id 2,cipher AES-256-GCM' (status=1)
Tue May 15 16:22:24 2018 vpn/89.155.20.132 Data Channel: using negotiated cipher 'AES-256-GCM'
Tue May 15 16:22:24 2018 vpn/89.155.20.132 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:22:24 2018 vpn/89.155.20.132 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:22:24 2018 vpn/89.155.20.132 MULTI: Learn: 00:ff:80:c0:f1:b1 -> vpn/89.155.20.132
Tue May 15 16:23:49 2018 89.155.20.132 TLS: Initial packet from [AF_INET6]::ffff:89.155.20.132:62579, sid=3f979443 02bfc547
Tue May 15 16:23:49 2018 89.155.20.132 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Tue May 15 16:23:49 2018 89.155.20.132 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_VER=2.4.6
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_PLAT=win
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_PROTO=2
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_NCP=2
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_LZ4=1
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_LZ4v2=1
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_LZO=1
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_COMP_STUB=1
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_COMP_STUBv2=1
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_TCPNL=1
Tue May 15 16:23:49 2018 89.155.20.132 peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue May 15 16:23:49 2018 89.155.20.132 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Tue May 15 16:23:49 2018 89.155.20.132 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:89.155.20.132:62579
Tue May 15 16:23:49 2018 vpn/89.155.20.132 MULTI_sva: pool returned IPv4=192.168.25.43, IPv6=(Not enabled)
Tue May 15 16:23:50 2018 vpn/89.155.20.132 PUSH: Received control message: 'PUSH_REQUEST'
Tue May 15 16:23:50 2018 vpn/89.155.20.132 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.43 255.255.255.0,peer-id 3,cipher AES-256-GCM' (status=1)
Tue May 15 16:23:50 2018 vpn/89.155.20.132 Data Channel: using negotiated cipher 'AES-256-GCM'
Tue May 15 16:23:50 2018 vpn/89.155.20.132 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:23:50 2018 vpn/89.155.20.132 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:23:51 2018 vpn/89.155.20.132 MULTI: Learn: 00:ff:80:c0:f1:b1 -> vpn/89.155.20.132
Tue May 15 16:27:39 2018 vpn/89.155.20.132 [vpn] Inactivity timeout (--ping-restart), restarting
Tue May 15 16:27:39 2018 vpn/89.155.20.132 SIGUSR1[soft,ping-restart] received, client-instance restarting
Tue May 15 16:32:54 2018 89.155.20.132 TLS: Initial packet from [AF_INET6]::ffff:89.155.20.132:57140, sid=f55d314a 7ff46abb
Tue May 15 16:32:54 2018 89.155.20.132 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Tue May 15 16:32:54 2018 89.155.20.132 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_VER=2.4.6
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_PLAT=win
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_PROTO=2
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_NCP=2
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_LZ4=1
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_LZ4v2=1
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_LZO=1
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_COMP_STUB=1
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_COMP_STUBv2=1
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_TCPNL=1
Tue May 15 16:32:54 2018 89.155.20.132 peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue May 15 16:32:54 2018 89.155.20.132 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Tue May 15 16:32:54 2018 89.155.20.132 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:89.155.20.132:57140
Tue May 15 16:32:54 2018 vpn/89.155.20.132 MULTI_sva: pool returned IPv4=192.168.25.42, IPv6=(Not enabled)
Tue May 15 16:32:56 2018 vpn/89.155.20.132 PUSH: Received control message: 'PUSH_REQUEST'
Tue May 15 16:32:56 2018 vpn/89.155.20.132 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.42 255.255.255.0,peer-id 2,cipher AES-256-GCM' (status=1)
Tue May 15 16:32:56 2018 vpn/89.155.20.132 Data Channel: using negotiated cipher 'AES-256-GCM'
Tue May 15 16:32:56 2018 vpn/89.155.20.132 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:32:56 2018 vpn/89.155.20.132 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:32:56 2018 vpn/89.155.20.132 MULTI: Learn: 00:ff:80:c0:f1:b1 -> vpn/89.155.20.132
Tue May 15 16:34:58 2018 vpn/89.155.20.132 [vpn] Inactivity timeout (--ping-restart), restarting
Tue May 15 16:34:58 2018 vpn/89.155.20.132 SIGUSR1[soft,ping-restart] received, client-instance restarting
Tue May 15 16:44:27 2018 vpn/89.155.20.132 [vpn] Inactivity timeout (--ping-restart), restarting
Tue May 15 16:44:27 2018 vpn/89.155.20.132 SIGUSR1[soft,ping-restart] received, client-instance restarting
Tue May 15 16:46:04 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Tue May 15 16:46:04 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Tue May 15 16:49:51 2018 vpn/94.61.114.36 TLS: soft reset sec=0 bytes=5122666/-1 pkts=16103/0
Tue May 15 16:50:04 2018 vpn/94.61.114.36 [vpn] Inactivity timeout (--ping-restart), restarting
Tue May 15 16:50:04 2018 vpn/94.61.114.36 SIGUSR1[soft,ping-restart] received, client-instance restarting
Tue May 15 16:50:05 2018 89.155.20.132 TLS: Initial packet from [AF_INET6]::ffff:89.155.20.132:60355, sid=fb98acb2 d5c596de
Tue May 15 16:50:05 2018 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:89.155.20.132:60355 [0]
Tue May 15 16:50:05 2018 94.61.114.36 TLS Error: Unroutable control packet received from [AF_INET6]::ffff:94.61.114.36:6859 (si=3 op=P_CONTROL_SOFT_RESET_V1)
Tue May 15 16:50:05 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:05 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:05 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:05 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:06 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:06 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:06 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS: new session incoming connection from [AF_INET6]::ffff:94.61.114.36:6859
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: reading acknowledgement record from packet
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:07 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:08 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:08 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:08 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:09 2018 94.61.114.36 TLS Error: local/remote TLS keys are out of sync: [AF_INET6]::ffff:94.61.114.36:6859 [0]
Tue May 15 16:50:10 2018 94.61.114.36 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Tue May 15 16:50:10 2018 94.61.114.36 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_VER=2.4.6
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_PLAT=win
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_PROTO=2
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_LZ4=1
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_LZ4v2=1
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_LZO=1
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_COMP_STUB=1
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_COMP_STUBv2=1
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_TCPNL=1
Tue May 15 16:50:10 2018 94.61.114.36 peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue May 15 16:50:10 2018 94.61.114.36 Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue May 15 16:50:10 2018 94.61.114.36 Outgoing Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue May 15 16:50:10 2018 94.61.114.36 Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue May 15 16:50:10 2018 94.61.114.36 Incoming Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue May 15 16:50:10 2018 94.61.114.36 TLS: move_session: dest=TM_ACTIVE src=TM_UNTRUSTED reinit_src=1
Tue May 15 16:50:10 2018 94.61.114.36 TLS: tls_multi_process: untrusted session promoted to semi-trusted
Tue May 15 16:50:10 2018 94.61.114.36 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Tue May 15 16:50:10 2018 94.61.114.36 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.61.114.36:6859
Tue May 15 16:50:10 2018 vpn/94.61.114.36 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Tue May 15 16:50:17 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:49459, sid=94e3f4ed 05603142
Tue May 15 16:50:17 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Tue May 15 16:50:17 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_VER=2.4.6
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_PLAT=win
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_PROTO=2
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_NCP=2
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_LZ4=1
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_LZ4v2=1
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_LZO=1
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_TCPNL=1
Tue May 15 16:50:17 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue May 15 16:50:17 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Tue May 15 16:50:17 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:49459
Tue May 15 16:50:17 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.41, IPv6=(Not enabled)
Tue May 15 16:50:18 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Tue May 15 16:50:18 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.41 255.255.255.0,peer-id 1,cipher AES-256-GCM' (status=1)
Tue May 15 16:50:18 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Tue May 15 16:50:18 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:50:18 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:50:20 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Tue May 15 16:51:22 2018 89.155.20.132 TLS: Initial packet from [AF_INET6]::ffff:89.155.20.132:60516, sid=97f48cb3 af891eeb
Tue May 15 16:51:23 2018 89.155.20.132 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Tue May 15 16:51:23 2018 89.155.20.132 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_VER=2.4.6
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_PLAT=win
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_PROTO=2
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_NCP=2
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_LZ4=1
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_LZ4v2=1
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_LZO=1
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_COMP_STUB=1
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_COMP_STUBv2=1
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_TCPNL=1
Tue May 15 16:51:23 2018 89.155.20.132 peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue May 15 16:51:23 2018 89.155.20.132 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Tue May 15 16:51:23 2018 89.155.20.132 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:89.155.20.132:60516
Tue May 15 16:51:23 2018 vpn/89.155.20.132 MULTI_sva: pool returned IPv4=192.168.25.42, IPv6=(Not enabled)
Tue May 15 16:51:25 2018 vpn/89.155.20.132 PUSH: Received control message: 'PUSH_REQUEST'
Tue May 15 16:51:25 2018 vpn/89.155.20.132 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.42 255.255.255.0,peer-id 2,cipher AES-256-GCM' (status=1)
Tue May 15 16:51:25 2018 vpn/89.155.20.132 Data Channel: using negotiated cipher 'AES-256-GCM'
Tue May 15 16:51:25 2018 vpn/89.155.20.132 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:51:25 2018 vpn/89.155.20.132 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue May 15 16:51:37 2018 vpn/89.155.20.132 MULTI: Learn: 00:ff:80:c0:f1:b1 -> vpn/89.155.20.132

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Tue May 15, 2018 8:17 pm

I'm trying this out to solve the TLS question above

https://forum.pfsense.org/index.php?topic=127391.0

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 4877
Joined: Fri Jun 03, 2016 1:17 pm

Re: [Newbie Inside] Bridge mode

Post by TinCanTech » Wed May 16, 2018 11:22 am

MetalicMan wrote:
Tue May 15, 2018 8:17 pm
I'm trying this out to solve the TLS question above

https://forum.pfsense.org/index.php?topic=127391.0
The suggested work around from pfsense is a Very Bad Idea -- Do NOT use it !

They advise you increase your TLS renegotiation to 10x the recommended period.

Your log shows you had a downtime of a couple of seconds while your client reconnected at the specified --reneg-sec timeout of 3600 (1 hour) .. That is how openvpn is supposed to work.
Last edited by TinCanTech on Wed May 16, 2018 10:26 pm, edited 2 times in total.

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Wed May 16, 2018 9:26 pm

Dispite the workaround, today had the same issue after a couple of hours.
The connections seems ok on the server, computers are green, but its not responding to requests. I try to restart the service from GUI but no success, I have to restart the computer..

Can you figure out whats causing this so I can remove the workaround and get the correct settings?

Here's the log until I restart the computer

Code: Select all

Wed May 16 12:44:59 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 12:57:03 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 12:57:03 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 12:57:03 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:54267
Wed May 16 12:57:03 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 12:57:04 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 12:57:04 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 12:57:04 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 12:57:04 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 12:57:04 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 12:57:07 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 13:01:07 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 13:01:07 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 13:03:05 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:55398, sid=7dc69c45 9d5f8a86
Wed May 16 13:03:05 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 13:03:05 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 13:03:05 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 13:03:05 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 13:03:05 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:55398
Wed May 16 13:03:05 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 13:03:06 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 13:03:06 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 13:03:06 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 13:03:06 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 13:03:06 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 13:03:21 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 13:07:21 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 13:07:21 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 13:09:19 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:52992, sid=0a8ea0fb 5afdd233
Wed May 16 13:09:19 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 13:09:19 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 13:09:19 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 13:09:19 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 13:09:19 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:52992
Wed May 16 13:09:19 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 13:09:20 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 13:09:20 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 13:09:20 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 13:09:20 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 13:09:20 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 13:09:21 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 13:13:21 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 13:13:21 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 13:15:19 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:60679, sid=207cbe62 9e11dba3
Wed May 16 13:15:19 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 13:15:19 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 13:15:19 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 13:15:19 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 13:15:19 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:60679
Wed May 16 13:15:19 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 13:15:20 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 13:15:20 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 13:15:20 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 13:15:20 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 13:15:20 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 13:15:21 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 13:19:21 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 13:19:21 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 13:21:21 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:53192, sid=a5410b69 fa1a38ed
Wed May 16 13:21:21 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 13:21:21 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 13:21:21 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 13:21:21 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 13:21:21 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:53192
Wed May 16 13:21:21 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 13:21:22 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 13:21:22 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 13:21:22 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 13:21:22 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 13:21:22 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 13:21:26 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 13:25:26 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 13:25:26 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 14:56:13 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:63897, sid=af562922 adf76a8d
Wed May 16 14:56:13 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 14:56:13 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 14:56:13 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 14:56:13 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 14:56:13 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:63897
Wed May 16 14:56:13 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 14:56:14 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 14:56:14 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 14:56:14 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 14:56:14 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 14:56:14 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 14:56:14 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 15:00:14 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 15:00:14 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 15:02:12 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:51283, sid=d7714693 fd782dc4
Wed May 16 15:02:12 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 15:02:12 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 15:02:12 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 15:02:12 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 15:02:12 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:51283
Wed May 16 15:02:12 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 15:02:13 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 15:02:13 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 15:02:13 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 15:02:13 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:02:13 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:02:23 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 15:06:23 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 15:06:23 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 15:08:21 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:64792, sid=c9d5857f 2226aaaf
Wed May 16 15:08:21 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 15:08:21 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 15:08:21 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 15:08:21 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 15:08:21 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:64792
Wed May 16 15:08:21 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 15:08:22 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 15:08:22 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 15:08:22 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 15:08:22 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:08:22 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:08:24 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 15:12:24 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 15:12:24 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 15:28:53 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:49856, sid=72d0a093 3ddf8c1e
Wed May 16 15:28:53 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 15:28:53 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 15:28:53 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 15:28:53 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 15:28:53 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:49856
Wed May 16 15:28:53 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 15:28:54 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 15:28:54 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 15:28:54 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 15:28:54 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:28:54 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:28:54 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 15:32:54 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 15:32:54 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 15:34:52 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:49784, sid=104ff354 d94f7bec
Wed May 16 15:34:52 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 15:34:52 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 15:34:52 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 15:34:52 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 15:34:52 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:49784
Wed May 16 15:34:52 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 15:34:53 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 15:34:53 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 15:34:53 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 15:34:53 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:34:53 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:35:00 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 15:39:00 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 15:39:00 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 15:40:59 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:61346, sid=1415fb04 a9e432cc
Wed May 16 15:40:59 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 15:40:59 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 15:40:59 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 15:40:59 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 15:40:59 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:61346
Wed May 16 15:40:59 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 15:41:01 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 15:41:01 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 15:41:01 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 15:41:01 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:41:01 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:41:04 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 15:45:04 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 15:45:04 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 15:47:04 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:15573, sid=85b77b5c ddf43148
Wed May 16 15:47:04 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 15:47:04 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 15:47:04 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 15:47:04 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 15:47:04 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:15573
Wed May 16 15:47:04 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 15:47:05 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 15:47:05 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 15:47:05 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 15:47:05 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:47:05 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:47:06 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 15:51:07 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 15:51:07 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 15:53:04 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:62550, sid=d5a73462 520f6bc6
Wed May 16 15:53:04 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 15:53:04 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 15:53:04 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 15:53:04 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 15:53:04 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:62550
Wed May 16 15:53:04 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 15:53:05 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 15:53:05 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 15:53:05 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 15:53:05 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:53:05 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:53:20 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 15:57:20 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 15:57:20 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 15:57:56 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:58798, sid=85c222e9 84b14442
Wed May 16 15:57:56 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 15:57:56 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 15:57:56 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 15:57:56 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 15:57:56 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:58798
Wed May 16 15:57:56 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 15:57:57 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 15:57:57 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 15:57:57 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 15:57:57 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:57:57 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 15:57:58 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 16:01:58 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 16:01:58 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 16:03:55 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:53643, sid=3e9f5398 04b9d80d
Wed May 16 16:03:55 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 16:03:55 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 16:03:55 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 16:03:55 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 16:03:55 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:53643
Wed May 16 16:03:55 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 16:03:56 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 16:03:56 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 16:03:56 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 16:03:56 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 16:03:56 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 16:04:02 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 16:08:02 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 16:08:02 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 16:09:59 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:56245, sid=c8631c2f 3c540b1e
Wed May 16 16:09:59 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 16:09:59 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 16:09:59 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 16:09:59 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 16:09:59 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:56245
Wed May 16 16:09:59 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 16:10:01 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 16:10:01 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Wed May 16 16:10:01 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 16:10:01 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 16:10:01 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 16:10:05 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 16:14:05 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 16:14:05 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 16:15:54 2018 87.103.96.70 TLS: Initial packet from [AF_INET6]::ffff:87.103.96.70:50095, sid=411cf819 0f63dac0
Wed May 16 16:15:55 2018 87.103.96.70 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 16:15:55 2018 87.103.96.70 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_VER=2.4.6
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_PLAT=win
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_PROTO=2
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_NCP=2
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_LZ4=1
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_LZ4v2=1
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_LZO=1
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_COMP_STUB=1
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_COMP_STUBv2=1
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_TCPNL=1
Wed May 16 16:15:55 2018 87.103.96.70 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 16:15:55 2018 87.103.96.70 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 16:15:55 2018 87.103.96.70 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:87.103.96.70:50095
Wed May 16 16:15:55 2018 vpn/87.103.96.70 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Wed May 16 16:16:04 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:56279, sid=a00c4af9 08f28649
Wed May 16 16:16:04 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Wed May 16 16:16:04 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_VER=2.4.6
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_PLAT=win
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_PROTO=2
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_NCP=2
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_LZ4=1
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_LZ4v2=1
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_LZO=1
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_TCPNL=1
Wed May 16 16:16:04 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 16 16:16:04 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed May 16 16:16:04 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:56279
Wed May 16 16:16:04 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.41, IPv6=(Not enabled)
Wed May 16 16:16:05 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Wed May 16 16:16:05 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.41 255.255.255.0,peer-id 1,cipher AES-256-GCM' (status=1)
Wed May 16 16:16:05 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 16 16:16:05 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 16:16:05 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 16 16:16:06 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Wed May 16 16:19:55 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Wed May 16 16:19:55 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Wed May 16 16:21:37 2018 MANAGEMENT: CMD 'signal SIGHUP'
Wed May 16 16:21:37 2018 SENT CONTROL [vpn]: 'RESTART' (status=1)
Wed May 16 16:21:39 2018 Closing TUN/TAP interface









Server Config:
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
reneg-sec 36000

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

# 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 quimialvpn.crt
key quimialvpn.key # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

# 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
duplicate-cn

# 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.25.62 255.255.255.0 192.168.25.40 192.168.25.50

# 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.1.60 0.0.0.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# 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.
# Note that v2.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 (v2.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 3

# 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 config
client.conf
##############################################
# 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
reneg-sec 0

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
dev tap
;dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
;proto tcp
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote ******.ddns.net 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 ca.crt
cert vpn.crt
key vpn.key

# Verify server certificate by checking that the
# certicate has the correct key usage set.
# 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 keyUsage set to
# digitalSignature, keyEncipherment
# and the extendedKeyUsage to
# serverAuth
# EasyRSA can do this for you.
remote-cert-tls 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.
# Note that v2.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.
# 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

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Thu May 17, 2018 6:13 pm

Crashed 2 times today, only rebooting the computer has solved the problem

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Thu May 17, 2018 7:30 pm

I can connect, but I cannot ping or see the network


Latest Log where that happens, you can see my connection @ 20:16 but I cannot browse or ping.
Have to restart the computer and reconnect the client

Code: Select all

Thu May 17 16:08:40 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
192.168.25.40 255.255.255.0,peer-id 2,cipher AES-256-GCM' (status=1)
Thu May 17 17:45:42 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 17:45:42 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 17:45:42 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 17:45:42 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Thu May 17 17:46:40 2018 94.63.179.107 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu May 17 17:46:40 2018 94.63.179.107 TLS Error: TLS handshake failed
Thu May 17 17:46:40 2018 94.63.179.107 SIGUSR1[soft,tls-error] received, client-instance restarting
Thu May 17 17:46:40 2018 94.63.179.107 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu May 17 17:46:40 2018 94.63.179.107 TLS Error: TLS handshake failed
Thu May 17 17:46:40 2018 94.63.179.107 SIGUSR1[soft,tls-error] received, client-instance restarting
Thu May 17 17:50:39 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 17:50:39 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 17:50:39 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:64899, sid=432eea7f e80ac519
Thu May 17 17:50:39 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:64611, sid=503c001b aa58d1d1
Thu May 17 17:50:39 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:53076, sid=967373c7 a983dba6
Thu May 17 17:50:39 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:60710, sid=2d444eb0 126d777d
Thu May 17 17:50:39 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:61160, sid=755d936e 942a25bd
Thu May 17 17:50:39 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 17:50:39 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_VER=2.4.6
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_PLAT=win
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_PROTO=2
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_NCP=2
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_LZ4=1
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_LZ4v2=1
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_LZO=1
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_TCPNL=1
Thu May 17 17:50:39 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 17:50:39 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 17:50:39 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:61160
Thu May 17 17:50:39 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 17:50:40 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 17:50:40 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 4,cipher AES-256-GCM' (status=1)
Thu May 17 17:50:40 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 17:50:40 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 17:50:40 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 17:50:40 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Thu May 17 17:51:39 2018 94.63.179.107 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu May 17 17:51:39 2018 94.63.179.107 TLS Error: TLS handshake failed
Thu May 17 17:51:39 2018 94.63.179.107 SIGUSR1[soft,tls-error] received, client-instance restarting
Thu May 17 17:51:39 2018 94.63.179.107 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu May 17 17:51:39 2018 94.63.179.107 TLS Error: TLS handshake failed
Thu May 17 17:51:39 2018 94.63.179.107 SIGUSR1[soft,tls-error] received, client-instance restarting
Thu May 17 17:51:39 2018 94.63.179.107 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu May 17 17:51:39 2018 94.63.179.107 TLS Error: TLS handshake failed
Thu May 17 17:51:39 2018 94.63.179.107 SIGUSR1[soft,tls-error] received, client-instance restarting
Thu May 17 17:51:39 2018 94.63.179.107 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu May 17 17:51:39 2018 94.63.179.107 TLS Error: TLS handshake failed
Thu May 17 17:51:39 2018 94.63.179.107 SIGUSR1[soft,tls-error] received, client-instance restarting
Thu May 17 17:55:38 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 17:55:38 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 17:57:38 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:56479, sid=b9fa7a29 28c9e7db
Thu May 17 17:57:38 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 17:57:38 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_VER=2.4.6
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_PLAT=win
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_PROTO=2
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_NCP=2
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_LZ4=1
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_LZ4v2=1
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_LZO=1
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_TCPNL=1
Thu May 17 17:57:38 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 17:57:38 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 17:57:38 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:56479
Thu May 17 17:57:38 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 17:57:39 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 17:57:39 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 17:57:39 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 17:57:39 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 17:57:39 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 17:57:49 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Thu May 17 18:01:49 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 18:01:49 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 18:03:47 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:61806, sid=3a977c91 08c92547
Thu May 17 18:03:47 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 18:03:47 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_VER=2.4.6
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_PLAT=win
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_PROTO=2
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_NCP=2
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_LZ4=1
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_LZ4v2=1
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_LZO=1
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_TCPNL=1
Thu May 17 18:03:47 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 18:03:47 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 18:03:47 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:61806
Thu May 17 18:03:47 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 18:03:48 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 18:03:48 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 18:03:48 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 18:03:48 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:03:48 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:03:54 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Thu May 17 18:07:54 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 18:07:54 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 18:09:50 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:57209, sid=699377c4 e108eab2
Thu May 17 18:09:50 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 18:09:50 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_VER=2.4.6
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_PLAT=win
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_PROTO=2
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_NCP=2
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_LZ4=1
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_LZ4v2=1
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_LZO=1
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_TCPNL=1
Thu May 17 18:09:50 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 18:09:50 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 18:09:50 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:57209
Thu May 17 18:09:50 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 18:09:51 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 18:09:51 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 18:09:51 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 18:09:51 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:09:51 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:09:54 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Thu May 17 18:13:54 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 18:13:54 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 18:15:52 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:58592, sid=f5a5a5cd 657b87e0
Thu May 17 18:15:52 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 18:15:52 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_VER=2.4.6
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_PLAT=win
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_PROTO=2
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_NCP=2
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_LZ4=1
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_LZ4v2=1
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_LZO=1
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_TCPNL=1
Thu May 17 18:15:52 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 18:15:52 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 18:15:52 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:58592
Thu May 17 18:15:52 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 18:15:53 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 18:15:53 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 18:15:53 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 18:15:53 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:15:53 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:15:54 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Thu May 17 18:19:55 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 18:19:55 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 18:21:50 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:56318, sid=bee26dbe 0b42ef8f
Thu May 17 18:21:50 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 18:21:50 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_VER=2.4.6
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_PLAT=win
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_PROTO=2
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_NCP=2
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_LZ4=1
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_LZ4v2=1
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_LZO=1
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_TCPNL=1
Thu May 17 18:21:50 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 18:21:50 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 18:21:50 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:56318
Thu May 17 18:21:50 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 18:21:51 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 18:21:51 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 18:21:51 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 18:21:51 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:21:51 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:21:53 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Thu May 17 18:25:53 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 18:25:53 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 18:27:50 2018 94.63.179.107 TLS: Initial packet from [AF_INET6]::ffff:94.63.179.107:52471, sid=bde84317 de03087f
Thu May 17 18:27:50 2018 94.63.179.107 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 18:27:50 2018 94.63.179.107 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_VER=2.4.6
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_PLAT=win
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_PROTO=2
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_NCP=2
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_LZ4=1
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_LZ4v2=1
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_LZO=1
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_COMP_STUB=1
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_COMP_STUBv2=1
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_TCPNL=1
Thu May 17 18:27:50 2018 94.63.179.107 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 18:27:50 2018 94.63.179.107 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 18:27:50 2018 94.63.179.107 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:94.63.179.107:52471
Thu May 17 18:27:50 2018 vpn/94.63.179.107 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 18:27:51 2018 vpn/94.63.179.107 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 18:27:51 2018 vpn/94.63.179.107 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 18:27:51 2018 vpn/94.63.179.107 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 18:27:51 2018 vpn/94.63.179.107 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:27:51 2018 vpn/94.63.179.107 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 18:27:54 2018 vpn/94.63.179.107 MULTI: Learn: 00:ff:4f:97:64:ad -> vpn/94.63.179.107
Thu May 17 18:31:54 2018 vpn/94.63.179.107 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 18:31:54 2018 vpn/94.63.179.107 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:03:48 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:64109, sid=79fdf6e8 a8cbd67c
Thu May 17 19:03:48 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:03:48 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:03:48 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:03:48 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:03:48 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:64109
Thu May 17 19:03:48 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:03:49 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:03:49 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:03:49 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:03:49 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:03:49 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:03:49 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:07:50 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:07:50 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:09:47 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:56272, sid=b6faed63 d77c045f
Thu May 17 19:09:47 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:09:47 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:09:47 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:09:47 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:09:47 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:56272
Thu May 17 19:09:47 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:09:48 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:09:48 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:09:48 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:09:48 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:09:48 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:09:55 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:13:55 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:13:55 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:15:54 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:56972, sid=b8b0d23d 847c3cef
Thu May 17 19:15:54 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:15:54 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:15:54 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:15:54 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:15:54 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:56972
Thu May 17 19:15:54 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:15:55 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:15:55 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:15:55 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:15:55 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:15:55 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:16:06 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:20:06 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:20:06 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:22:04 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:63802, sid=9cdc1f73 67461581
Thu May 17 19:22:04 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:22:04 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:22:04 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:22:04 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:22:04 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:63802
Thu May 17 19:22:04 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:22:05 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:22:05 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:22:05 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:22:05 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:22:05 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:22:06 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:26:06 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:26:06 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:28:05 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:60281, sid=eca392de 1e90b8d8
Thu May 17 19:28:05 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:28:05 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:28:05 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:28:05 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:28:05 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:60281
Thu May 17 19:28:05 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:28:06 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:28:06 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:28:06 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:28:06 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:28:06 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:28:07 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:32:07 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:32:07 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:34:02 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:52158, sid=9638c577 b09f9616
Thu May 17 19:34:02 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:34:02 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:34:02 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:34:02 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:34:02 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:52158
Thu May 17 19:34:02 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:34:03 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:34:03 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:34:03 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:34:03 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:34:03 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:34:06 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:38:06 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:38:06 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:40:04 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:49950, sid=d37ae57a 3d303637
Thu May 17 19:40:04 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:40:04 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:40:04 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:40:04 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:40:04 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:49950
Thu May 17 19:40:04 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:40:05 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:40:05 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:40:05 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:40:05 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:40:05 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:40:06 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:44:06 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:44:06 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:46:03 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:54483, sid=5b1f9673 c1ac8bf5
Thu May 17 19:46:03 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:46:03 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:46:03 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:46:03 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:46:03 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:54483
Thu May 17 19:46:03 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:46:05 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:46:05 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:46:05 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:46:05 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:46:05 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:46:06 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:50:06 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:50:06 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:52:05 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:59803, sid=36f37bc9 b196f5c9
Thu May 17 19:52:05 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:52:05 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:52:05 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:52:05 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:52:05 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:59803
Thu May 17 19:52:05 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:52:07 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:52:07 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:52:07 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:52:07 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:52:07 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:52:08 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 19:56:09 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 19:56:09 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 19:58:03 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:62034, sid=757c8aa8 72a4326a
Thu May 17 19:58:03 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 19:58:03 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 19:58:03 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 19:58:03 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 19:58:03 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:62034
Thu May 17 19:58:03 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 19:58:04 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 19:58:04 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 19:58:04 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 19:58:04 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:58:04 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 19:58:06 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 20:02:06 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 20:02:06 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 20:04:06 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:27375, sid=6219ac16 d017203b
Thu May 17 20:04:06 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 20:04:06 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 20:04:06 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 20:04:06 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 20:04:06 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:27375
Thu May 17 20:04:06 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 20:04:07 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 20:04:07 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 20:04:07 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 20:04:07 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 20:04:07 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 20:04:08 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 20:08:09 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 20:08:09 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 20:10:06 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:59385, sid=07b0e06d fd115c5b
Thu May 17 20:10:06 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 20:10:06 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 20:10:06 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 20:10:06 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 20:10:06 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:59385
Thu May 17 20:10:06 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 20:10:08 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 20:10:08 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 20:10:08 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 20:10:08 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 20:10:08 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 20:10:09 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 20:14:09 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 20:14:09 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting
Thu May 17 20:16:07 2018 148.63.253.18 TLS: Initial packet from [AF_INET6]::ffff:148.63.253.18:58966, sid=ad654b99 33254054
Thu May 17 20:16:07 2018 148.63.253.18 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Thu May 17 20:16:07 2018 148.63.253.18 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=vpn, name=vpn, emailAddress=geral@quimial.pt
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_VER=2.4.6
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_PLAT=win
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_PROTO=2
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_NCP=2
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_LZ4=1
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_LZ4v2=1
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_LZO=1
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_COMP_STUB=1
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_COMP_STUBv2=1
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_TCPNL=1
Thu May 17 20:16:07 2018 148.63.253.18 peer info: IV_GUI_VER=OpenVPN_GUI_11
Thu May 17 20:16:07 2018 148.63.253.18 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 17 20:16:07 2018 148.63.253.18 [vpn] Peer Connection Initiated with [AF_INET6]::ffff:148.63.253.18:58966
Thu May 17 20:16:07 2018 vpn/148.63.253.18 MULTI_sva: pool returned IPv4=192.168.25.40, IPv6=(Not enabled)
Thu May 17 20:16:09 2018 vpn/148.63.253.18 PUSH: Received control message: 'PUSH_REQUEST'
Thu May 17 20:16:09 2018 vpn/148.63.253.18 SENT CONTROL [vpn]: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Thu May 17 20:16:09 2018 vpn/148.63.253.18 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 17 20:16:09 2018 vpn/148.63.253.18 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 20:16:09 2018 vpn/148.63.253.18 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 17 20:16:16 2018 vpn/148.63.253.18 MULTI: Learn: 00:ff:c2:f9:f7:45 -> vpn/148.63.253.18
Thu May 17 20:20:17 2018 vpn/148.63.253.18 [vpn] Inactivity timeout (--ping-restart), restarting
Thu May 17 20:20:17 2018 vpn/148.63.253.18 SIGUSR1[soft,ping-restart] received, client-instance restarting

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Sat May 19, 2018 9:22 am

Problem still persists :(

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 4877
Joined: Fri Jun 03, 2016 1:17 pm

Re: [Newbie Inside] Bridge mode

Post by TinCanTech » Sat May 19, 2018 11:11 am

You still have not posted a client log file ..

Try adding --duplicate-cn to your server config.

Also, you may have created your bridge incorrectly, please try using --dev tun (not tap)

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Mon May 21, 2018 7:36 am

Thanks for the reply!

I'll get that for you.
My client log shows nothing unusual, it connects, I got IP, It minimizes, and stays green, but I cannot connect or ping to anything.

A log from this morning when this situation was happening

Code: Select all

Mon May 21 08:32:08 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Mon May 21 08:32:08 2018 Windows version 6.2 (Windows 8 or greater) 64bit
Mon May 21 08:32:08 2018 library versions: OpenSSL 1.1.0h  27 Mar 2018, LZO 2.10
Mon May 21 08:32:08 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Mon May 21 08:32:08 2018 Need hold release from management interface, waiting...
Mon May 21 08:32:08 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Mon May 21 08:32:09 2018 MANAGEMENT: CMD 'state on'
Mon May 21 08:32:09 2018 MANAGEMENT: CMD 'log all on'
Mon May 21 08:32:09 2018 MANAGEMENT: CMD 'echo all on'
Mon May 21 08:32:09 2018 MANAGEMENT: CMD 'bytecount 5'
Mon May 21 08:32:09 2018 MANAGEMENT: CMD 'hold off'
Mon May 21 08:32:09 2018 MANAGEMENT: CMD 'hold release'
Mon May 21 08:32:09 2018 MANAGEMENT: >STATE:1526887929,RESOLVE,,,,,,
Mon May 21 08:32:09 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]2.83.58.179:1194
Mon May 21 08:32:09 2018 Socket Buffers: R=[65536->65536] S=[65536->65536]
Mon May 21 08:32:09 2018 UDP link local: (not bound)
Mon May 21 08:32:09 2018 UDP link remote: [AF_INET]2.83.58.179:1194
Mon May 21 08:32:09 2018 MANAGEMENT: >STATE:1526887929,WAIT,,,,,,
Mon May 21 08:32:09 2018 MANAGEMENT: >STATE:1526887929,AUTH,,,,,,
Mon May 21 08:32:09 2018 TLS: Initial packet from [AF_INET]2.83.58.179:1194, sid=553b3a0c ce0d9bc0
Mon May 21 08:32:09 2018 VERIFY OK: depth=1, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=QUIMIAL_SEDE, name=QUIMIAL_SEDE, emailAddress=geral@quimial.pt
Mon May 21 08:32:09 2018 VERIFY KU OK
Mon May 21 08:32:09 2018 Validating certificate extended key usage
Mon May 21 08:32:09 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Mon May 21 08:32:09 2018 VERIFY EKU OK
Mon May 21 08:32:09 2018 VERIFY OK: depth=0, C=PT, ST=PORTO, L=PovoaVarzim, O=Quimial, OU=Quimial, CN=quimialvpn, name=quimialvpn, emailAddress=geral@quimial.pt
Mon May 21 08:32:09 2018 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Mon May 21 08:32:09 2018 [quimialvpn] Peer Connection Initiated with [AF_INET]2.83.58.179:1194
Mon May 21 08:32:10 2018 MANAGEMENT: >STATE:1526887930,GET_CONFIG,,,,,,
Mon May 21 08:32:10 2018 SENT CONTROL [quimialvpn]: 'PUSH_REQUEST' (status=1)
Mon May 21 08:32:10 2018 PUSH: Received control message: 'PUSH_REPLY,route-gateway 192.168.25.62,ping 10,ping-restart 120,ifconfig 192.168.25.40 255.255.255.0,peer-id 0,cipher AES-256-GCM'
Mon May 21 08:32:10 2018 OPTIONS IMPORT: timers and/or timeouts modified
Mon May 21 08:32:10 2018 OPTIONS IMPORT: --ifconfig/up options modified
Mon May 21 08:32:10 2018 OPTIONS IMPORT: route-related options modified
Mon May 21 08:32:10 2018 OPTIONS IMPORT: peer-id set
Mon May 21 08:32:10 2018 OPTIONS IMPORT: adjusting link_mtu to 1656
Mon May 21 08:32:10 2018 OPTIONS IMPORT: data channel crypto options modified
Mon May 21 08:32:10 2018 Data Channel: using negotiated cipher 'AES-256-GCM'
Mon May 21 08:32:10 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon May 21 08:32:10 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon May 21 08:32:10 2018 interactive service msg_channel=648
Mon May 21 08:32:10 2018 open_tun
Mon May 21 08:32:10 2018 TAP-WIN32 device [Ethernet 3] opened: \\.\Global\{C2F9F745-9237-4008-A2D2-A70FAF5AC7D0}.tap
Mon May 21 08:32:10 2018 TAP-Windows Driver Version 9.21 
Mon May 21 08:32:10 2018 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.25.40/255.255.255.0 on interface {C2F9F745-9237-4008-A2D2-A70FAF5AC7D0} [DHCP-serv: 192.168.25.0, lease-time: 31536000]
Mon May 21 08:32:10 2018 Successful ARP Flush on interface [5] {C2F9F745-9237-4008-A2D2-A70FAF5AC7D0}
Mon May 21 08:32:10 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Mon May 21 08:32:10 2018 MANAGEMENT: >STATE:1526887930,ASSIGN_IP,,192.168.25.40,,,,
Mon May 21 08:32:15 2018 TEST ROUTES: 0/0 succeeded len=0 ret=1 a=0 u/d=up
Mon May 21 08:32:15 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon May 21 08:32:15 2018 Initialization Sequence Completed
Mon May 21 08:32:15 2018 MANAGEMENT: >STATE:1526887935,CONNECTED,SUCCESS,192.168.25.40,2.83.58.179,1194,,

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 4877
Joined: Fri Jun 03, 2016 1:17 pm

Re: [Newbie Inside] Bridge mode

Post by TinCanTech » Mon May 21, 2018 9:58 am

Your log shows nothing but a normal successful connection.

The problem you experience is renegotiation of data channel keys, this is how openvpn works.
The best thing you can do at this time is to change your --keepalive values to speed up the timeout.

Try: keepalive 10 30 (in your server config)

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Mon May 21, 2018 10:18 pm

Thanks once again for taking the time to keep up with this matter!

New test before aplying the keepalive: Server was on for 4 hours, I've connected, I got positive connection, but could not ping from this "hot start"

I've already had duplicate cn on the server config.
I've now added the keepalive

Current server config:
server
#################################################
# 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
reneg-sec 36000
keepalive 10 30

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

# 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 quimialvpn.crt
key quimialvpn.key # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

# 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
duplicate-cn

# 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.25.62 255.255.255.0 192.168.25.40 192.168.25.50

# 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.1.60 0.0.0.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# 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.
# Note that v2.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 (v2.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 3

# 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



Thanks once again!

MetalicMan
OpenVPN User
Posts: 22
Joined: Tue May 15, 2018 8:16 am

Re: [Newbie Inside] Bridge mode

Post by MetalicMan » Tue May 22, 2018 8:58 am

This morning problem happens again. Got a fresh connection but cannot ping or browse... Only restarting the computer...

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 4877
Joined: Fri Jun 03, 2016 1:17 pm

Re: [Newbie Inside] Bridge mode

Post by TinCanTech » Tue May 22, 2018 9:27 am

Try adding --ncp-disable to your server.

You also need to provide clear and concise details of the problem when it occurs:
  • Server log showing what the server is doing when the problem occurs
  • Client log when the problem occurs
Also, wait a couple of minutes to see if the connection can be re-established.
MetalicMan wrote:
Tue May 22, 2018 8:58 am
Only restarting the computer...
Which computer ? be clear ..

Post Reply