Knowledgebase: Konfiguracja VPN
OpenVPN - Gdzie znajdę logi połączenia?
Posted by Robert O on 12 sierpnia 2016 10:32 AM

Dziennik logów dostępny jest bezpośrednio w kliencie OpenVPN i nadpisywane przy każdorazowym połączeniu do serwera VPN.

Uruchom OpenVPN klienta, z listy wybierz serwer VPN i spróbuj się połączyć.
Następnie, z listy wybierz ponownie ten sam serwer i następnie "Pokaż Log"

W odpowiedzi otrzymamy:

Fri Apr 18 10:45:35 2014 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013
Enter Management Password:
Fri Apr 18 10:45:35 2014 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25354
Fri Apr 18 10:45:35 2014 Need hold release from management interface, waiting...
Fri Apr 18 10:45:35 2014 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25354
Fri Apr 18 10:45:35 2014 MANAGEMENT: CMD 'state on'
Fri Apr 18 10:45:35 2014 MANAGEMENT: CMD 'log all on'
Fri Apr 18 10:45:35 2014 MANAGEMENT: CMD 'hold off'
Fri Apr 18 10:45:35 2014 MANAGEMENT: CMD 'hold release'
Fri Apr 18 10:45:41 2014 MANAGEMENT: CMD 'username "Auth" "vpnonline"'
Fri Apr 18 10:45:41 2014 MANAGEMENT: CMD 'password [...]'
Fri Apr 18 10:45:41 2014 WARNING: No server certificate verification method has been enabled.
Fri Apr 18 10:45:42 2014 Socket Buffers: R=[8192->8192] S=[8192->8192]
Fri Apr 18 10:45:42 2014 MANAGEMENT: >STATE:1397810742,RESOLVE,,,
Fri Apr 18 10:45:42 2014 Attempting to establish TCP connection with [AF_INET]nazwa_serwera_vpn
Fri Apr 18 10:45:42 2014 MANAGEMENT: >STATE:1397810742,TCP_CONNECT,,,
Fri Apr 18 10:45:42 2014 TCP connection established with [AF_INET]nazwa_serwera_vpn
Fri Apr 18 10:45:42 2014 TCPv4_CLIENT link local: [undef]
Fri Apr 18 10:45:42 2014 TCPv4_CLIENT link remote: [AF_INET]nazwa_serwera_vpn
Fri Apr 18 10:45:42 2014 MANAGEMENT: >STATE:1397810742,WAIT,,,
Fri Apr 18 10:45:42 2014 MANAGEMENT: >STATE:1397810742,AUTH,,,
Fri Apr 18 10:45:42 2014 TLS: Initial packet from [AF_INET]nazwa_serwera_vpn, sid=ef521bd9 e24435f5
Fri Apr 18 10:45:42 2014 VERIFY OK: depth=2, C=BE, O=GlobalSign nv-sa, OU=Root CA, CN=GlobalSign Root CA
Fri Apr 18 10:45:42 2014 VERIFY OK: depth=1, O=AlphaSSL, CN=AlphaSSL CA - G2
Fri Apr 18 10:45:42 2014 VERIFY OK: depth=0, OU=Domain Control Validated, CN=*.vpnonline.eu
Fri Apr 18 10:45:43 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Apr 18 10:45:43 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Apr 18 10:45:43 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Apr 18 10:45:43 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Apr 18 10:45:43 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 4096 bit RSA
Fri Apr 18 10:45:43 2014 [*.vpnonline.eu] Peer Connection Initiated with [AF_INET]nazwa_serwera_vpn
Fri Apr 18 10:45:44 2014 MANAGEMENT: >STATE:1397810744,GET_CONFIG,,,
Fri Apr 18 10:45:45 2014 SENT CONTROL [*.vpnonline.eu]: 'PUSH_REQUEST' (status=1)
Fri Apr 18 10:45:50 2014 SENT CONTROL [*.vpnonline.eu]: 'PUSH_REQUEST' (status=1)
Fri Apr 18 10:45:55 2014 SENT CONTROL [*.vpnonline.eu]: 'PUSH_REQUEST' (status=1)
Fri Apr 18 10:45:55 2014 PUSH: Received control message:
'PUSH_REPLY,dhcp-option DNS 208.67.220.220,dhcp-option DNS 208.67.222.222,inactive 86400,ping 20,ping-restart 60,
route-gateway 10.100.200.254,ifconfig 10.100.200.49 255.255.255.0'
Fri Apr 18 10:45:55 2014 OPTIONS IMPORT: timers and/or timeouts modified
Fri Apr 18 10:45:55 2014 OPTIONS IMPORT: --ifconfig/up options modified
Fri Apr 18 10:45:55 2014 OPTIONS IMPORT: route-related options modified
Fri Apr 18 10:45:55 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Apr 18 10:45:55 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Fri Apr 18 10:45:55 2014 MANAGEMENT: >STATE:1397810755,ASSIGN_IP,,10.100.200.49,
Fri Apr 18 10:45:55 2014 open_tun, tt->ipv6=0
Fri Apr 18 10:45:55 2014 TAP-WIN32 device [Połączenie lokalne 2] opened: \\.\Global\{288E1A20-D4D4-41BF-8F19-4A41B463A100}.tap
Fri Apr 18 10:45:55 2014 TAP-Windows Driver Version 9.9
Fri Apr 18 10:45:55 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.100.200.49/255.255.255.0
on interface {288E1A20-D4D4-41BF-8F19-4A41B463A100} [DHCP-serv: 10.100.200.0, lease-time: 31536000]
Fri Apr 18 10:45:55 2014 Successful ARP Flush on interface [16] {288E1A20-D4D4-41BF-8F19-4A41B463A100}
Fri Apr 18 10:45:57 2014 TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up
Fri Apr 18 10:45:57 2014 C:\WINDOWS\system32\route.exe ADD 212.77.100.101 MASK 255.255.255.255 10.10.0.2
Fri Apr 18 10:45:57 2014 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Fri Apr 18 10:45:57 2014 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.100.200.254
Fri Apr 18 10:45:57 2014 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Fri Apr 18 10:45:57 2014 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.100.200.254
Fri Apr 18 10:45:57 2014 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Fri Apr 18 10:45:57 2014 Initialization Sequence Completed
Fri Apr 18 10:45:57 2014 MANAGEMENT: >STATE:1397810757,CONNECTED,SUCCESS,10.100.200.49,212.77.100.101

W OpenVPN kliencie mamy możliwość zmiany szczegółowości rejestru zdarzeń przez zmienną w konfiguracji .ovpn

verb (domyślnie verb 3)

Ustawienie szczegółowości rejestru zdarzeń:

0 – tylko błędy krytyczne,
4 – ogólne zastosowanie
5 oraz 6 – debugowanie problemów z połączeniem
9 – zapis wszystkich zdarzeń

Ustalenie ile tych samych powtórzonych zdarzeń ma się pojawić w logu:

mute 5

(0 vote(s))
Helpful
Not helpful