OS win 8.1
Anyone have a clew?
Best regards / Martin
log:
Fri Jan 24 19:11:18 2014 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013
Enter Management Password:
Fri Jan 24 19:11:18 2014 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Fri Jan 24 19:11:18 2014 Need hold release from management interface, waiting...
Fri Jan 24 19:11:19 2014 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Fri Jan 24 19:11:19 2014 MANAGEMENT: CMD 'state on'
Fri Jan 24 19:11:19 2014 MANAGEMENT: CMD 'log all on'
Fri Jan 24 19:11:19 2014 MANAGEMENT: CMD 'hold off'
Fri Jan 24 19:11:19 2014 MANAGEMENT: CMD 'hold release'
Fri Jan 24 19:11:19 2014 Socket Buffers: R=[65536->65536] S=[65536->65536]
Fri Jan 24 19:11:19 2014 UDPv4 link local: [undef]
Fri Jan 24 19:11:19 2014 UDPv4 link remote: [AF_INET]91.123.200.171:1194
Fri Jan 24 19:11:19 2014 MANAGEMENT: >STATE:1390587079,WAIT,,,
Fri Jan 24 19:11:19 2014 MANAGEMENT: >STATE:1390587079,AUTH,,,
Fri Jan 24 19:11:19 2014 TLS: Initial packet from [AF_INET]91.123.200.171:1194, sid=b2927f9d 58521fc8
Fri Jan 24 19:11:22 2014 VERIFY OK: depth=1, C=SE, ST=CA, L=SanFrancisco, O=Fort-Funston, CN=Fort-Funston CA, emailAddress=
Fri Jan 24 19:11:22 2014 VERIFY OK: nsCertType=SERVER
Fri Jan 24 19:11:22 2014 VERIFY OK: depth=0, C=SE, ST=CA, L=SanFrancisco, O=Fort-Funston, CN= , emailAddress=
Fri Jan 24 19:11:23 2014 WARNING: 'dev-type' is used inconsistently, local='dev-type tap', remote='dev-type tun'
Fri Jan 24 19:11:23 2014 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1574', remote='link-mtu 1542'
Fri Jan 24 19:11:23 2014 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1532', remote='tun-mtu 1500'
Fri Jan 24 19:11:23 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Jan 24 19:11:23 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Jan 24 19:11:23 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Jan 24 19:11:23 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Jan 24 19:11:23 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Fri Jan 24 19:11:23 2014 [ ] Peer Connection Initiated with [AF_INET]91.123.200.171:1194
Fri Jan 24 19:11:24 2014 MANAGEMENT: >STATE:1390587084,GET_CONFIG,,,
Fri Jan 24 19:11:25 2014 SENT CONTROL [ ]: 'PUSH_REQUEST' (status=1)
Fri Jan 24 19:11:25 2014 PUSH: Received control message: 'PUSH_REPLY,“dhcp-option DNS 10.8.0.1″,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5'
Fri Jan 24 19:11:25 2014 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:1: “dhcp-option (2.3.2)
Fri Jan 24 19:11:25 2014 OPTIONS IMPORT: timers and/or timeouts modified
Fri Jan 24 19:11:25 2014 OPTIONS IMPORT: --ifconfig/up options modified
Fri Jan 24 19:11:25 2014 OPTIONS IMPORT: route options modified
Fri Jan 24 19:11:25 2014 WARNING: Since you are using --dev tap, the second argument to --ifconfig must be a netmask, for example something like 255.255.255.0. (silence this warning with --ifconfig-nowarn)
Fri Jan 24 19:11:25 2014 OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
Fri Jan 24 19:11:25 2014 OpenVPN ROUTE: failed to parse/resolve route for host/network: 0.0.0.0
Fri Jan 24 19:11:25 2014 OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
Fri Jan 24 19:11:25 2014 OpenVPN ROUTE: failed to parse/resolve route for host/network: 10.8.0.1
Fri Jan 24 19:11:25 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Fri Jan 24 19:11:25 2014 MANAGEMENT: >STATE:1390587085,ASSIGN_IP,,10.8.0.6,
Fri Jan 24 19:11:25 2014 open_tun, tt->ipv6=0
Fri Jan 24 19:11:25 2014 TAP-WIN32 device [Anslutning till lokalt nätverk] opened: \\.\Global\{B6FE8BA2-ACAA-4B59-81D4-948F83DBA08D}.tap
Fri Jan 24 19:11:25 2014 TAP-Windows Driver Version 9.9
Fri Jan 24 19:11:25 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/10.8.0.5 on interface {B6FE8BA2-ACAA-4B59-81D4-948F83DBA08D} [DHCP-serv: 10.8.0.4, lease-time: 31536000]
Fri Jan 24 19:11:25 2014 Successful ARP Flush on interface [21] {B6FE8BA2-ACAA-4B59-81D4-948F83DBA08D}
Fri Jan 24 19:11:27 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:27 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:29 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:29 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:30 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:30 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:31 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:31 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:32 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:32 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:33 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:33 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:34 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:34 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:35 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:35 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:36 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:36 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:37 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:37 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:38 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:38 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:39 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:39 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:40 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:40 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:41 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:41 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:42 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:42 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:43 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:43 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:44 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:44 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:45 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:45 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:46 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:46 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:47 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:47 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:48 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:48 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:49 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:49 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:50 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:50 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:51 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:51 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:52 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:52 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:53 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:53 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:55 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:55 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:56 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
Fri Jan 24 19:11:56 2014 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 24 19:11:57 2014 TEST ROUTES: 0/0 succeeded len=0 ret=0 a=0 u/d=down
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.1.1 p=0 i=15 t=4 pr=3 a=1230 h=0 m=25/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=431038 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=431038 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=431038 h=0 m=306/0/0/0/0
192.168.1.0 255.255.255.0 192.168.1.11 p=0 i=15 t=3 pr=2 a=1230 h=0 m=281/0/0/0/0
192.168.1.11 255.255.255.255 192.168.1.11 p=0 i=15 t=3 pr=2 a=1230 h=0 m=281/0/0/0/0
192.168.1.255 255.255.255.255 192.168.1.11 p=0 i=15 t=3 pr=2 a=1230 h=0 m=281/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=431038 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 0.0.0.0 p=0 i=21 t=3 pr=2 a=431022 h=0 m=286/0/0/0/0
224.0.0.0 240.0.0.0 192.168.1.11 p=0 i=15 t=3 pr=2 a=1253 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=431038 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 0.0.0.0 p=0 i=21 t=3 pr=2 a=431022 h=0 m=286/0/0/0/0
255.255.255.255 255.255.255.255 192.168.1.11 p=0 i=15 t=3 pr=2 a=1253 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Windows Adapter V9
Index = 21
GUID = {B6FE8BA2-ACAA-4B59-81D4-948F83DBA08D}
IP = 169.254.243.203/255.255.0.0
MAC = 00:ff:b6:fe:8b:a2
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 0.0.0.0/255.255.255.255
DHCP LEASE OBTAINED = Fri Jan 24 19:11:57 2014
DHCP LEASE EXPIRES = Fri Jan 24 19:11:57 2014
DNS SERV =
Microsoft Hosted Network Virtual Adapter
Index = 19
GUID = {F0DD0932-937E-4FDC-9F36-962F4807D186}
IP = 0.0.0.0/0.0.0.0
MAC = 56:db:30:2d:1f:28
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jan 24 19:11:57 2014
DHCP LEASE EXPIRES = Fri Jan 24 19:11:57 2014
DNS SERV =
Microsoft Wi-Fi Direct Virtual Adapter
Index = 16
GUID = {C6ACDF57-4A88-478C-AD73-251F5C5477F7}
IP = 0.0.0.0/0.0.0.0
MAC = 16:db:30:2d:1f:28
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jan 24 19:11:57 2014
DHCP LEASE EXPIRES = Fri Jan 24 19:11:57 2014
DNS SERV =
Qualcomm Atheros AR956x Wireless Network Adapter
Index = 15
GUID = {7F5F3F3E-EDE6-4921-A91A-A1D1C5E9953A}
IP = 192.168.1.11/255.255.255.0
MAC = a4:db:30:2d:1f:28
GATEWAY = 192.168.1.1/255.255.255.255
DHCP SERV = 192.168.1.1/255.255.255.255
DHCP LEASE OBTAINED = Fri Jan 24 18:51:27 2014
DHCP LEASE EXPIRES = Fri Jan 31 18:51:27 2014
DNS SERV = 192.168.1.1/255.255.255.255
Bluetooth Device (Personal Area Network)
Index = 13
GUID = {C3E7FC30-A088-48F1-93DF-74DF9E2E212A}
IP = 0.0.0.0/0.0.0.0
MAC = a4:db:30:2d:57:68
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jan 24 19:11:57 2014
DHCP LEASE EXPIRES = Fri Jan 24 19:11:57 2014
DNS SERV =
Realtek PCIe GBE Family Controller
Index = 12
GUID = {42228631-F2AB-4C49-9C27-4BBC6269B03D}
IP = 0.0.0.0/0.0.0.0
MAC = 18:67:b0:be:e0:52
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jan 24 19:11:57 2014
DHCP LEASE EXPIRES = Fri Jan 24 19:11:57 2014
DNS SERV =
Fri Jan 24 19:11:57 2014 Initialization Sequence Completed With Errors ( see
http://openvpn.net/faq.html#dhcpclientserv )
Fri Jan 24 19:11:57 2014 MANAGEMENT: >STATE:1390587117,CONNECTED,ERROR,10.8.0.6,91.123.200.171
.ovpn:
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################
# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client
# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
dev tap
;dev tun
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap
# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
;proto tcp
proto udp
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote 91.123.200.171 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 nogroup
# Try to preserve some state across restarts.
persist-key
persist-tun
# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]
# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings
# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
ca ca.crt
cert client1.crt
key client1.key
# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". This is an
# important precaution to protect against
# a potential attack discussed here:
#
http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
ns-cert-type server
# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1
# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo
# Set log file verbosity.
verb 3
# Silence repeating messages
;mute 20
#mssfix
route-method exe
#route-method IPAPI
route-delay 2
route 0.0.0.0 0.0.0.0