Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 2023-05-10 10:49:19.621717 *Tunnelblick: macOS 13.3.1 (22E261); Tunnelblick 3.8.8a (build 5776); prior version 3.8.8 (build 5775)
- 2023-05-10 10:49:19.934678 *Tunnelblick: Attempting connection with exo_n.mamaev_2023 using shadow copy; Set nameserver = 769; monitoring connection
- 2023-05-10 10:49:19.935576 *Tunnelblick: openvpnstart start exo_n.mamaev_2023.tblk 54000 769 0 1 0 34652464 -ptADGNWradsgnw 2.5.9-openssl-1.1.1t <password>
- 2023-05-10 10:49:20.323239 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
- 2023-05-10 10:49:20.323402 OpenVPN 2.5.9 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Feb 16 2023
- 2023-05-10 10:49:20.323416 library versions: OpenSSL 1.1.1t 7 Feb 2023, LZO 2.10
- 2023-05-10 10:49:20.324037 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:54000
- 2023-05-10 10:49:20.324048 Need hold release from management interface, waiting...
- 2023-05-10 10:49:20.560522 *Tunnelblick: openvpnstart log:
- OpenVPN started successfully.
- Command used to start OpenVPN (one argument per displayed line):
- /Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.5.9-openssl-1.1.1t/openvpn
- --daemon
- --log /Library/Application Support/Tunnelblick/Logs/-SUsers-Snmamaev-SLibrary-SApplication Support-STunnelblick-SConfigurations-Sexo_n.mamaev_2023.tblk-SContents-SResources-Sconfig.ovpn.769_0_1_0_34652464.54000.openvpn.log
- --cd /Library/Application Support/Tunnelblick/Users/nmamaev/exo_n.mamaev_2023.tblk/Contents/Resources
- --machine-readable-output
- --setenv IV_GUI_VER "net.tunnelblick.tunnelblick 5776 3.8.8a (build 5776)"
- --verb 3
- --config /Library/Application Support/Tunnelblick/Users/nmamaev/exo_n.mamaev_2023.tblk/Contents/Resources/config.ovpn
- --setenv TUNNELBLICK_CONFIG_FOLDER /Library/Application Support/Tunnelblick/Users/nmamaev/exo_n.mamaev_2023.tblk/Contents/Resources
- --verb 3
- --cd /Library/Application Support/Tunnelblick/Users/nmamaev/exo_n.mamaev_2023.tblk/Contents/Resources
- --management 127.0.0.1 54000 /Library/Application Support/Tunnelblick/Mips/exo_n.mamaev_2023.tblk.mip
- --management-query-passwords
- --management-hold
- --script-security 2
- --route-up /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -9 -d -f -m -w -ptADGNWradsgnw
- --down /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -9 -d -f -m -w -ptADGNWradsgnw
- 2023-05-10 10:49:20.583126 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:54000
- 2023-05-10 10:49:20.613361 MANAGEMENT: CMD 'pid'
- 2023-05-10 10:49:20.613440 MANAGEMENT: CMD 'auth-retry interact'
- 2023-05-10 10:49:20.613476 MANAGEMENT: CMD 'state on'
- 2023-05-10 10:49:20.613498 MANAGEMENT: CMD 'state'
- 2023-05-10 10:49:20.613541 MANAGEMENT: CMD 'bytecount 1'
- 2023-05-10 10:49:20.614005 *Tunnelblick: Established communication with OpenVPN
- 2023-05-10 10:49:20.615090 *Tunnelblick: >INFO:OpenVPN Management Interface Version 3 -- type 'help' for more info
- 2023-05-10 10:49:20.616047 MANAGEMENT: CMD 'hold release'
- 2023-05-10 10:49:42.673519 MANAGEMENT: CMD 'username "Auth" "n.mamaev"'
- 2023-05-10 10:49:42.673895 MANAGEMENT: CMD 'password [...]'
- 2023-05-10 10:49:42.674059 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
- 2023-05-10 10:49:42.675554 MANAGEMENT: >STATE:1683686982,RESOLVE,,,,,,
- 2023-05-10 10:49:42.699245 TCP/UDP: Preserving recently used remote address: [AF_INET]185.63.189.130:1195
- 2023-05-10 10:49:42.699365 Socket Buffers: R=[786896->786896] S=[9216->9216]
- 2023-05-10 10:49:42.699389 UDP link local: (not bound)
- 2023-05-10 10:49:42.699405 UDP link remote: [AF_INET]185.63.189.130:1195
- 2023-05-10 10:49:42.699432 MANAGEMENT: >STATE:1683686982,WAIT,,,,,,
- 2023-05-10 10:49:42.771363 MANAGEMENT: >STATE:1683686982,AUTH,,,,,,
- 2023-05-10 10:49:42.771499 TLS: Initial packet from [AF_INET]185.63.189.130:1195, sid=ab92f175 623aa9d3
- 2023-05-10 10:49:42.867502 VERIFY OK: depth=1, CN=Exo-soft VPN Server
- 2023-05-10 10:49:42.868334 VERIFY KU OK
- 2023-05-10 10:49:42.868385 Validating certificate extended key usage
- 2023-05-10 10:49:42.868408 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
- 2023-05-10 10:49:42.868423 VERIFY EKU OK
- 2023-05-10 10:49:42.868436 VERIFY OK: depth=0, CN=server
- 2023-05-10 10:49:42.984242 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
- 2023-05-10 10:49:42.984394 [server] Peer Connection Initiated with [AF_INET]185.63.189.130:1195
- 2023-05-10 10:49:44.315425 MANAGEMENT: >STATE:1683686984,GET_CONFIG,,,,,,
- 2023-05-10 10:49:44.315624 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
- 2023-05-10 10:49:44.386849 PUSH: Received control message: 'PUSH_REPLY,route 10.3.0.0 255.255.255.0,route 10.50.0.0 255.255.255.0,route 10.99.0.0 255.255.255.0,route 10.13.0.0 255.255.255.0,route 172.16.0.0 255.255.255.0,route 172.16.4.0 255.255.255.0,route 172.31.240.0 255.255.240.0,route 172.31.224.0 255.255.240.0,route 172.31.223.0 255.255.255.0,route 172.31.220.0 255.255.255.0,route 172.31.48.0 255.255.240.0,route 172.31.33.0 255.255.255.0,route 82.202.164.22 255.255.255.255,route 212.109.223.137 255.255.255.255,route 80.87.203.174 255.255.255.255,route 192.168.80.1,topology net30,ping 10,ping-restart 120,route 135.181.128.208 255.255.255.255,route 144.76.39.238 255.255.255.255,route 172.31.36.0 255.255.254.0,route 185.146.158.7 255.255.255.255,route 188.120.227.207 255.255.255.255,route 23.88.71.231 255.255.255.255,route 31.135.14.255 255.255.255.255,route 31.135.9.63 255.255.255.255,route 37.230.119.161 255.255.255.255,route 79.143.72.175 255.255.255.255,push-continuation 2'
- 2023-05-10 10:49:44.387337 PUSH: Received control message: 'PUSH_REPLY,route 82.202.160.81 255.255.255.255,route 82.202.163.44 255.255.255.255,ifconfig 10.60.4.173 10.60.4.174,peer-id 10,cipher AES-256-GCM,push-continuation 1'
- 2023-05-10 10:49:44.400367 OPTIONS IMPORT: timers and/or timeouts modified
- 2023-05-10 10:49:44.400447 OPTIONS IMPORT: --ifconfig/up options modified
- 2023-05-10 10:49:44.400478 OPTIONS IMPORT: route options modified
- 2023-05-10 10:49:44.400486 OPTIONS IMPORT: peer-id set
- 2023-05-10 10:49:44.400494 OPTIONS IMPORT: adjusting link_mtu to 1625
- 2023-05-10 10:49:44.400501 OPTIONS IMPORT: data channel crypto options modified
- 2023-05-10 10:49:44.400510 Data Channel: using negotiated cipher 'AES-256-GCM'
- 2023-05-10 10:49:44.414241 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
- 2023-05-10 10:49:44.415291 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
- 2023-05-10 10:49:44.422205 Opened utun device utun4
- 2023-05-10 10:49:44.422267 MANAGEMENT: >STATE:1683686984,ASSIGN_IP,,10.60.4.173,,,,
- 2023-05-10 10:49:44.422285 /sbin/ifconfig utun4 delete
- ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
- 2023-05-10 10:49:44.455635 NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
- 2023-05-10 10:49:44.455687 /sbin/ifconfig utun4 10.60.4.173 10.60.4.174 mtu 1500 netmask 255.255.255.255 up
- 2023-05-10 10:49:44.460826 MANAGEMENT: >STATE:1683686984,ADD_ROUTES,,,,,,
- 2023-05-10 10:49:44.460891 /sbin/route add -net 10.3.0.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 10.3.0.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.472286 /sbin/route add -net 10.50.0.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 10.50.0.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.477320 /sbin/route add -net 10.99.0.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 10.99.0.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.480661 /sbin/route add -net 10.13.0.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 10.13.0.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.483875 /sbin/route add -net 172.16.0.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 172.16.0.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.487084 /sbin/route add -net 172.16.4.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 172.16.4.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.489296 /sbin/route add -net 172.31.240.0 10.60.4.174 255.255.240.0
- route: writing to routing socket: File exists
- add net 172.31.240.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.492649 /sbin/route add -net 172.31.224.0 10.60.4.174 255.255.240.0
- route: writing to routing socket: File exists
- add net 172.31.224.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.495684 /sbin/route add -net 172.31.223.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 172.31.223.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.498627 /sbin/route add -net 172.31.220.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 172.31.220.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.501612 /sbin/route add -net 172.31.48.0 10.60.4.174 255.255.240.0
- route: writing to routing socket: File exists
- add net 172.31.48.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.503993 /sbin/route add -net 172.31.33.0 10.60.4.174 255.255.255.0
- route: writing to routing socket: File exists
- add net 172.31.33.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.506209 /sbin/route add -net 82.202.164.22 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 82.202.164.22: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.508670 /sbin/route add -net 212.109.223.137 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 212.109.223.137: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.510844 /sbin/route add -net 80.87.203.174 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 80.87.203.174: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.513156 /sbin/route add -net 192.168.80.1 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 192.168.80.1: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.515820 /sbin/route add -net 135.181.128.208 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 135.181.128.208: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.518331 /sbin/route add -net 144.76.39.238 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 144.76.39.238: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.520612 /sbin/route add -net 172.31.36.0 10.60.4.174 255.255.254.0
- route: writing to routing socket: File exists
- add net 172.31.36.0: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.522996 /sbin/route add -net 185.146.158.7 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 185.146.158.7: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.525202 /sbin/route add -net 188.120.227.207 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 188.120.227.207: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.527317 /sbin/route add -net 23.88.71.231 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 23.88.71.231: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.529322 /sbin/route add -net 31.135.14.255 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 31.135.14.255: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.531307 /sbin/route add -net 31.135.9.63 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 31.135.9.63: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.533305 /sbin/route add -net 37.230.119.161 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 37.230.119.161: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.535343 /sbin/route add -net 79.143.72.175 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 79.143.72.175: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.537277 /sbin/route add -net 82.202.160.81 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 82.202.160.81: gateway 10.60.4.174: File exists
- 2023-05-10 10:49:44.539613 /sbin/route add -net 82.202.163.44 10.60.4.174 255.255.255.255
- route: writing to routing socket: File exists
- add net 82.202.163.44: gateway 10.60.4.174: File exists
- 10:49:44 *Tunnelblick: **********************************************
- 10:49:44 *Tunnelblick: Start of output from client.up.tunnelblick.sh
- 10:49:46 *Tunnelblick: NOTE: No network configuration changes need to be made.
- 10:49:46 *Tunnelblick: WARNING: Will NOT monitor for other network configuration changes.
- 10:49:46 *Tunnelblick: WARNING: Will NOT disable IPv6 settings.
- 10:49:46 *Tunnelblick: DNS servers '192.168.0.1' will be used for DNS queries when the VPN is active
- 10:49:46 *Tunnelblick: NOTE: The DNS servers do not include any free public DNS servers known to Tunnelblick. This may cause DNS queries to fail or be intercepted or falsified even if they are directed through the VPN. Specify only known public DNS servers or DNS servers located on the VPN network to avoid such problems.
- 10:49:46 *Tunnelblick: Flushed the DNS cache via dscacheutil
- 10:49:46 *Tunnelblick: /usr/sbin/discoveryutil not present. Not flushing the DNS cache via discoveryutil
- 10:49:46 *Tunnelblick: Notified mDNSResponder that the DNS cache was flushed
- 10:49:46 *Tunnelblick: Not notifying mDNSResponderHelper that the DNS cache was flushed because it is not running
- 10:49:46 *Tunnelblick: End of output from client.up.tunnelblick.sh
- 10:49:46 *Tunnelblick: **********************************************
- 2023-05-10 10:49:46.718466 Initialization Sequence Completed
- 2023-05-10 10:49:46.718499 MANAGEMENT: >STATE:1683686986,CONNECTED,SUCCESS,10.60.4.173,185.63.189.130,1195,,
- 2023-05-10 10:49:47.830384 *Tunnelblick: Warning: Could not obtain a list of DNS addresses that are expected
- 2023-05-10 10:49:47.938719 *Tunnelblick: Routing info stdout:
- route to: 192.168.0.1
- destination: 192.168.0.1
- interface: en0
- flags: <UP,HOST,DONE,LLINFO,WASCLONED,IFSCOPE,IFREF,ROUTER>
- recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire
- 0 0 0 0 0 0 1500 1193
- stderr:
- 2023-05-10 10:49:47.945040 *Tunnelblick: Warning: DNS server address 192.168.0.1 is not a public IP address and is not being routed through the VPN.
- 2023-05-10 10:49:53.561397 *Tunnelblick: This computer's apparent public IP address (178.184.156.111) was unchanged after the connection was made
- 2023-05-10 10:49:19.963406 *Tunnelblick: openvpnstart starting OpenVPN
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement