API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Apr 9th, 2019
114
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 35.18 KB | None | 0 0
raw download clone embed print report
  1. kdes70@kdes70-K56CB:/etc/openvpn$ sudo openvpn client.conf
  2. [sudo] пароль для kdes70:
  3. Tue Apr 9 17:00:08 2019 WARNING: file 'dmitriy.krivosein.key' is group or others accessible
  4. Tue Apr 9 17:00:08 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 3 2018
  5. Tue Apr 9 17:00:08 2019 library versions: OpenSSL 1.1.1 11 Sep 2018, LZO 2.10
  6. Tue Apr 9 17:00:08 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
  7. Tue Apr 9 17:00:08 2019 WARNING: normally if you use --mssfix and/or --fragment, you should also set --tun-mtu 1500 (currently it is 1450)
  8. Tue Apr 9 17:00:08 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]178.162.196.13:9999
  9. Tue Apr 9 17:00:08 2019 Socket Buffers: R=[87380->87380] S=[16384->16384]
  10. Tue Apr 9 17:00:08 2019 Attempting to establish TCP connection with [AF_INET]178.162.196.13:9999 [nonblock]
  11. Tue Apr 9 17:00:09 2019 TCP connection established with [AF_INET]178.162.196.13:9999
  12. Tue Apr 9 17:00:09 2019 TCP_CLIENT link local: (not bound)
  13. Tue Apr 9 17:00:09 2019 TCP_CLIENT link remote: [AF_INET]178.162.196.13:9999
  14. Tue Apr 9 17:00:09 2019 TLS: Initial packet from [AF_INET]178.162.196.13:9999, sid=9a9851b5 cb88b1b6
  15. Tue Apr 9 17:00:10 2019 VERIFY OK: depth=1, C=RU, ST=MSK, L=Moscow, O=Turbobit, CN=Turbobit CA, emailAddress=techs@remsys.net
  16. Tue Apr 9 17:00:10 2019 VERIFY OK: depth=0, C=RU, ST=MSK, L=Moscow, O=Turbobit, CN=vpn.turbobit.ru, emailAddress=techs@remsys.net
  17. Tue Apr 9 17:00:11 2019 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1494', remote='link-mtu 1544'
  18. Tue Apr 9 17:00:11 2019 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1450', remote='tun-mtu 1500'
  19. Tue Apr 9 17:00:11 2019 Control Channel: TLSv1, cipher SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
  20. Tue Apr 9 17:00:11 2019 [vpn.turbobit.ru] Peer Connection Initiated with [AF_INET]178.162.196.13:9999
  21. Tue Apr 9 17:00:12 2019 SENT CONTROL [vpn.turbobit.ru]: 'PUSH_REQUEST' (status=1)
  22. Tue Apr 9 17:00:13 2019 PUSH: Received control message: 'PUSH_REPLY,route 192.168.10.0 255.255.255.0,route 188.72.202.185 255.255.255.255 vpn_gateway,route 85.17.76.16 255.255.255.248 vpn_gateway,route 94.75.232.0 255.255.255.0 vpn_gateway,route 85.17.74.0 255.255.255.0 vpn_gateway,route 95.211.105.209 255.255.255.255 vpn_gateway,route 95.211.80.9 255.255.255.255 vpn_gateway,route 178.236.176.189 255.255.255.255 vpn_gateway,route 95.211.188.0 255.255.255.0 vpn_gateway,route 94.198.241.0 255.255.255.0 vpn_gateway,route 188.72.243.0 255.255.255.0 vpn_gateway,route 178.162.196.1 255.255.255.255 vpn_gateway,route 178.162.196.2 255.255.255.255 vpn_gateway,route 178.162.196.3 255.255.255.255 vpn_gateway,route 178.162.196.4 255.255.255.255 vpn_gateway,route 178.162.196.5 255.255.255.255 vpn_gateway,route 178.162.196.6 255.255.255.255 vpn_gateway,route 178.162.196.7 255.255.255.255 vpn_gateway,route 178.162.196.8 255.255.255.255 vpn_gateway,route 178.162.196.9 255.255.255.255 vpn_gateway,push-continuation 2'
  23. Tue Apr 9 17:00:14 2019 PUSH: Received control message: 'PUSH_REPLY,route 178.162.196.10 255.255.255.255 vpn_gateway,route 178.162.196.11 255.255.255.255 vpn_gateway,route 178.162.196.12 255.255.255.255 vpn_gateway,route 178.162.196.14 255.255.255.255 vpn_gateway,route 178.162.196.15 255.255.255.255 vpn_gateway,route 178.162.196.16 255.255.255.255 vpn_gateway,route 178.162.196.17 255.255.255.255 vpn_gateway,route 178.162.196.18 255.255.255.255 vpn_gateway,route 178.162.196.19 255.255.255.255 vpn_gateway,route 178.162.196.20 255.255.255.255 vpn_gateway,route 178.162.196.21 255.255.255.255 vpn_gateway,route 178.162.192.0 255.255.255.0 vpn_gateway,route 94.198.240.40 255.255.255.255 vpn_gateway,route 88.198.17.134 255.255.255.255 vpn_gateway,route 95.211.212.64 255.255.255.224 vpn_gateway,route 95.211.212.192 255.255.255.224 vpn_gateway,route 95.211.184.64 255.255.255.192 vpn_gateway,route 95.211.172.0 255.255.255.192 vpn_gateway,route 62.212.72.164 255.255.255.255 vpn_gateway,push-continuation 2'
  24. Tue Apr 9 17:00:15 2019 PUSH: Received control message: 'PUSH_REPLY,route 88.85.84.0 255.255.255.0 vpn_gateway,route 95.85.1.173 255.255.255.255 vpn_gateway,route 188.164.255.0 255.255.255.0 vpn_gateway,route 62.109.13.137 255.255.255.255 vpn_gateway,route 62.210.87.180 255.255.255.255 vpn_gateway,route 137.74.205.8 255.255.255.255 vpn_gateway,route 46.165.233.241 255.255.255.255 vpn_gateway,route 188.120.250.21 255.255.255.255 vpn_gateway,route 37.139.13.118 255.255.255.255 vpn_gateway,route 62.210.89.0 255.255.255.0 vpn_gateway,route 163.172.8.0 255.255.255.0 vpn_gateway,route 163.172.9.0 255.255.255.0 vpn_gateway,route 195.154.151.0 255.255.255.0 vpn_gateway,route 62.210.103.0 255.255.255.0 vpn_gateway,route 51.255.88.173 255.255.255.255 vpn_gateway,route 163.172.225.186 255.255.255.255 vpn_gateway,route 163.172.53.193 255.255.255.255 vpn_gateway,route 5.135.130.7 255.255.255.255 vpn_gateway,route 188.214.30.163 255.255.255.255 vpn_gateway,route 163.172.109.130 255.255.255.255 vpn_gateway,push-continuation 2'
  25. Tue Apr 9 17:00:15 2019 PUSH: Received control message: 'PUSH_REPLY,route 212.83.151.173 255.255.255.255 vpn_gateway,route 62.109.19.47 255.255.255.255 vpn_gateway,route 195.154.28.130 255.255.255.0 vpn_gateway,route 195.154.26.85 255.255.255.0 vpn_gateway,route 37.252.14.18 255.255.255.255 vpn_gateway ,route 5.45.65.111 255.255.255.255 vpn_gateway ,route 37.1.222.226 255.255.255.255 vpn_gateway ,route 10.10.1.0 255.255.255.0,topology net30,ping 20,ping-restart 65,ifconfig 10.10.1.102 10.10.1.101,push-continuation 1'
  26. Tue Apr 9 17:00:15 2019 OPTIONS IMPORT: timers and/or timeouts modified
  27. Tue Apr 9 17:00:15 2019 OPTIONS IMPORT: --ifconfig/up options modified
  28. Tue Apr 9 17:00:15 2019 OPTIONS IMPORT: route options modified
  29. Tue Apr 9 17:00:15 2019 Outgoing Data Channel: Cipher 'BF-CBC' initialized with 128 bit key
  30. Tue Apr 9 17:00:15 2019 WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
  31. Tue Apr 9 17:00:15 2019 Outgoing Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
  32. Tue Apr 9 17:00:15 2019 Incoming Data Channel: Cipher 'BF-CBC' initialized with 128 bit key
  33. Tue Apr 9 17:00:15 2019 WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
  34. Tue Apr 9 17:00:15 2019 Incoming Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
  35. Tue Apr 9 17:00:15 2019 WARNING: cipher with small block size in use, reducing reneg-bytes to 64MB to mitigate SWEET32 attacks.
  36. Tue Apr 9 17:00:15 2019 ROUTE_GATEWAY 192.168.0.1/255.255.255.0 IFACE=wlp3s0 HWADDR=24:fd:52:cc:e2:d2
  37. Tue Apr 9 17:00:15 2019 TUN/TAP device tun1 opened
  38. Tue Apr 9 17:00:15 2019 TUN/TAP TX queue length set to 100
  39. Tue Apr 9 17:00:15 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
  40. Tue Apr 9 17:00:15 2019 /sbin/ip link set dev tun1 up mtu 1450
  41. Tue Apr 9 17:00:15 2019 /sbin/ip addr add dev tun1 local 10.10.1.102 peer 10.10.1.101
  42. Tue Apr 9 17:00:15 2019 /sbin/ip route add 192.168.10.0/24 via 10.10.1.101
  43. RTNETLINK answers: File exists
  44. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  45. Tue Apr 9 17:00:15 2019 /sbin/ip route add 188.72.202.185/32 via 10.10.1.101
  46. RTNETLINK answers: File exists
  47. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  48. Tue Apr 9 17:00:15 2019 /sbin/ip route add 85.17.76.16/29 via 10.10.1.101
  49. RTNETLINK answers: File exists
  50. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  51. Tue Apr 9 17:00:15 2019 /sbin/ip route add 94.75.232.0/24 via 10.10.1.101
  52. RTNETLINK answers: File exists
  53. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  54. Tue Apr 9 17:00:15 2019 /sbin/ip route add 85.17.74.0/24 via 10.10.1.101
  55. RTNETLINK answers: File exists
  56. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  57. Tue Apr 9 17:00:15 2019 /sbin/ip route add 95.211.105.209/32 via 10.10.1.101
  58. RTNETLINK answers: File exists
  59. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  60. Tue Apr 9 17:00:15 2019 /sbin/ip route add 95.211.80.9/32 via 10.10.1.101
  61. RTNETLINK answers: File exists
  62. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  63. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.236.176.189/32 via 10.10.1.101
  64. RTNETLINK answers: File exists
  65. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  66. Tue Apr 9 17:00:15 2019 /sbin/ip route add 95.211.188.0/24 via 10.10.1.101
  67. RTNETLINK answers: File exists
  68. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  69. Tue Apr 9 17:00:15 2019 /sbin/ip route add 94.198.241.0/24 via 10.10.1.101
  70. RTNETLINK answers: File exists
  71. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  72. Tue Apr 9 17:00:15 2019 /sbin/ip route add 188.72.243.0/24 via 10.10.1.101
  73. RTNETLINK answers: File exists
  74. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  75. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.1/32 via 10.10.1.101
  76. RTNETLINK answers: File exists
  77. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  78. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.2/32 via 10.10.1.101
  79. RTNETLINK answers: File exists
  80. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  81. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.3/32 via 10.10.1.101
  82. RTNETLINK answers: File exists
  83. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  84. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.4/32 via 10.10.1.101
  85. RTNETLINK answers: File exists
  86. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  87. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.5/32 via 10.10.1.101
  88. RTNETLINK answers: File exists
  89. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  90. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.6/32 via 10.10.1.101
  91. RTNETLINK answers: File exists
  92. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  93. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.7/32 via 10.10.1.101
  94. RTNETLINK answers: File exists
  95. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  96. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.8/32 via 10.10.1.101
  97. RTNETLINK answers: File exists
  98. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  99. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.9/32 via 10.10.1.101
  100. RTNETLINK answers: File exists
  101. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  102. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.10/32 via 10.10.1.101
  103. RTNETLINK answers: File exists
  104. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  105. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.11/32 via 10.10.1.101
  106. RTNETLINK answers: File exists
  107. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  108. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.12/32 via 10.10.1.101
  109. RTNETLINK answers: File exists
  110. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  111. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.14/32 via 10.10.1.101
  112. RTNETLINK answers: File exists
  113. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  114. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.15/32 via 10.10.1.101
  115. RTNETLINK answers: File exists
  116. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  117. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.16/32 via 10.10.1.101
  118. RTNETLINK answers: File exists
  119. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  120. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.17/32 via 10.10.1.101
  121. RTNETLINK answers: File exists
  122. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  123. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.18/32 via 10.10.1.101
  124. RTNETLINK answers: File exists
  125. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  126. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.19/32 via 10.10.1.101
  127. RTNETLINK answers: File exists
  128. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  129. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.20/32 via 10.10.1.101
  130. RTNETLINK answers: File exists
  131. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  132. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.196.21/32 via 10.10.1.101
  133. RTNETLINK answers: File exists
  134. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  135. Tue Apr 9 17:00:15 2019 /sbin/ip route add 178.162.192.0/24 via 10.10.1.101
  136. RTNETLINK answers: File exists
  137. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  138. Tue Apr 9 17:00:15 2019 /sbin/ip route add 94.198.240.40/32 via 10.10.1.101
  139. RTNETLINK answers: File exists
  140. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  141. Tue Apr 9 17:00:15 2019 /sbin/ip route add 88.198.17.134/32 via 10.10.1.101
  142. RTNETLINK answers: File exists
  143. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  144. Tue Apr 9 17:00:15 2019 /sbin/ip route add 95.211.212.64/27 via 10.10.1.101
  145. RTNETLINK answers: File exists
  146. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  147. Tue Apr 9 17:00:15 2019 /sbin/ip route add 95.211.212.192/27 via 10.10.1.101
  148. RTNETLINK answers: File exists
  149. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  150. Tue Apr 9 17:00:15 2019 /sbin/ip route add 95.211.184.64/26 via 10.10.1.101
  151. RTNETLINK answers: File exists
  152. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  153. Tue Apr 9 17:00:15 2019 /sbin/ip route add 95.211.172.0/26 via 10.10.1.101
  154. RTNETLINK answers: File exists
  155. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  156. Tue Apr 9 17:00:15 2019 /sbin/ip route add 62.212.72.164/32 via 10.10.1.101
  157. RTNETLINK answers: File exists
  158. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  159. Tue Apr 9 17:00:15 2019 /sbin/ip route add 88.85.84.0/24 via 10.10.1.101
  160. RTNETLINK answers: File exists
  161. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  162. Tue Apr 9 17:00:15 2019 /sbin/ip route add 95.85.1.173/32 via 10.10.1.101
  163. RTNETLINK answers: File exists
  164. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  165. Tue Apr 9 17:00:15 2019 /sbin/ip route add 188.164.255.0/24 via 10.10.1.101
  166. RTNETLINK answers: File exists
  167. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  168. Tue Apr 9 17:00:15 2019 /sbin/ip route add 62.109.13.137/32 via 10.10.1.101
  169. RTNETLINK answers: File exists
  170. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  171. Tue Apr 9 17:00:15 2019 /sbin/ip route add 62.210.87.180/32 via 10.10.1.101
  172. RTNETLINK answers: File exists
  173. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  174. Tue Apr 9 17:00:15 2019 /sbin/ip route add 137.74.205.8/32 via 10.10.1.101
  175. RTNETLINK answers: File exists
  176. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  177. Tue Apr 9 17:00:15 2019 /sbin/ip route add 46.165.233.241/32 via 10.10.1.101
  178. RTNETLINK answers: File exists
  179. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  180. Tue Apr 9 17:00:15 2019 /sbin/ip route add 188.120.250.21/32 via 10.10.1.101
  181. RTNETLINK answers: File exists
  182. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  183. Tue Apr 9 17:00:15 2019 /sbin/ip route add 37.139.13.118/32 via 10.10.1.101
  184. RTNETLINK answers: File exists
  185. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  186. Tue Apr 9 17:00:15 2019 /sbin/ip route add 62.210.89.0/24 via 10.10.1.101
  187. RTNETLINK answers: File exists
  188. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  189. Tue Apr 9 17:00:15 2019 /sbin/ip route add 163.172.8.0/24 via 10.10.1.101
  190. RTNETLINK answers: File exists
  191. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  192. Tue Apr 9 17:00:15 2019 /sbin/ip route add 163.172.9.0/24 via 10.10.1.101
  193. RTNETLINK answers: File exists
  194. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  195. Tue Apr 9 17:00:15 2019 /sbin/ip route add 195.154.151.0/24 via 10.10.1.101
  196. RTNETLINK answers: File exists
  197. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  198. Tue Apr 9 17:00:15 2019 /sbin/ip route add 62.210.103.0/24 via 10.10.1.101
  199. RTNETLINK answers: File exists
  200. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  201. Tue Apr 9 17:00:15 2019 /sbin/ip route add 51.255.88.173/32 via 10.10.1.101
  202. RTNETLINK answers: File exists
  203. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  204. Tue Apr 9 17:00:15 2019 /sbin/ip route add 163.172.225.186/32 via 10.10.1.101
  205. RTNETLINK answers: File exists
  206. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  207. Tue Apr 9 17:00:15 2019 /sbin/ip route add 163.172.53.193/32 via 10.10.1.101
  208. RTNETLINK answers: File exists
  209. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  210. Tue Apr 9 17:00:15 2019 /sbin/ip route add 5.135.130.7/32 via 10.10.1.101
  211. RTNETLINK answers: File exists
  212. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  213. Tue Apr 9 17:00:15 2019 /sbin/ip route add 188.214.30.163/32 via 10.10.1.101
  214. RTNETLINK answers: File exists
  215. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  216. Tue Apr 9 17:00:15 2019 /sbin/ip route add 163.172.109.130/32 via 10.10.1.101
  217. RTNETLINK answers: File exists
  218. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  219. Tue Apr 9 17:00:15 2019 /sbin/ip route add 212.83.151.173/32 via 10.10.1.101
  220. RTNETLINK answers: File exists
  221. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  222. Tue Apr 9 17:00:15 2019 /sbin/ip route add 62.109.19.47/32 via 10.10.1.101
  223. RTNETLINK answers: File exists
  224. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  225. Tue Apr 9 17:00:15 2019 /sbin/ip route add 195.154.28.130/24 via 10.10.1.101
  226. Error: Invalid prefix for given prefix length.
  227. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  228. Tue Apr 9 17:00:15 2019 /sbin/ip route add 195.154.26.85/24 via 10.10.1.101
  229. Error: Invalid prefix for given prefix length.
  230. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  231. Tue Apr 9 17:00:15 2019 /sbin/ip route add 37.252.14.18/32 via 10.10.1.101
  232. RTNETLINK answers: File exists
  233. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  234. Tue Apr 9 17:00:15 2019 /sbin/ip route add 5.45.65.111/32 via 10.10.1.101
  235. RTNETLINK answers: File exists
  236. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  237. Tue Apr 9 17:00:15 2019 /sbin/ip route add 37.1.222.226/32 via 10.10.1.101
  238. RTNETLINK answers: File exists
  239. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  240. Tue Apr 9 17:00:15 2019 /sbin/ip route add 10.10.1.0/24 via 10.10.1.101
  241. RTNETLINK answers: File exists
  242. Tue Apr 9 17:00:15 2019 ERROR: Linux route add command failed: external program exited with error status: 2
  243. Tue Apr 9 17:00:15 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
  244. Tue Apr 9 17:00:15 2019 Initialization Sequence Completed
  245. Tue Apr 9 17:00:20 2019 Connection reset, restarting [0]
  246. Tue Apr 9 17:00:20 2019 SIGUSR1[soft,connection-reset] received, process restarting
  247. Tue Apr 9 17:00:20 2019 Restart pause, 5 second(s)
  248. Tue Apr 9 17:00:25 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
  249. Tue Apr 9 17:00:25 2019 WARNING: normally if you use --mssfix and/or --fragment, you should also set --tun-mtu 1500 (currently it is 1450)
  250. Tue Apr 9 17:00:25 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]178.162.196.13:9999
  251. Tue Apr 9 17:00:25 2019 Socket Buffers: R=[87380->87380] S=[16384->16384]
  252. Tue Apr 9 17:00:25 2019 Attempting to establish TCP connection with [AF_INET]178.162.196.13:9999 [nonblock]
  253. Tue Apr 9 17:00:26 2019 TCP connection established with [AF_INET]178.162.196.13:9999
  254. Tue Apr 9 17:00:26 2019 TCP_CLIENT link local: (not bound)
  255. Tue Apr 9 17:00:26 2019 TCP_CLIENT link remote: [AF_INET]178.162.196.13:9999
  256. Tue Apr 9 17:00:26 2019 TLS: Initial packet from [AF_INET]178.162.196.13:9999, sid=cd61f08a 397d8ff0
  257. Tue Apr 9 17:00:27 2019 VERIFY OK: depth=1, C=RU, ST=MSK, L=Moscow, O=Turbobit, CN=Turbobit CA, emailAddress=techs@remsys.net
  258. Tue Apr 9 17:00:27 2019 VERIFY OK: depth=0, C=RU, ST=MSK, L=Moscow, O=Turbobit, CN=vpn.turbobit.ru, emailAddress=techs@remsys.net
  259. Tue Apr 9 17:00:28 2019 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1494', remote='link-mtu 1544'
  260. Tue Apr 9 17:00:28 2019 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1450', remote='tun-mtu 1500'
  261. Tue Apr 9 17:00:28 2019 Control Channel: TLSv1, cipher SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
  262. Tue Apr 9 17:00:28 2019 [vpn.turbobit.ru] Peer Connection Initiated with [AF_INET]178.162.196.13:9999
  263. Tue Apr 9 17:00:29 2019 SENT CONTROL [vpn.turbobit.ru]: 'PUSH_REQUEST' (status=1)
  264. Tue Apr 9 17:00:30 2019 PUSH: Received control message: 'PUSH_REPLY,route 192.168.10.0 255.255.255.0,route 188.72.202.185 255.255.255.255 vpn_gateway,route 85.17.76.16 255.255.255.248 vpn_gateway,route 94.75.232.0 255.255.255.0 vpn_gateway,route 85.17.74.0 255.255.255.0 vpn_gateway,route 95.211.105.209 255.255.255.255 vpn_gateway,route 95.211.80.9 255.255.255.255 vpn_gateway,route 178.236.176.189 255.255.255.255 vpn_gateway,route 95.211.188.0 255.255.255.0 vpn_gateway,route 94.198.241.0 255.255.255.0 vpn_gateway,route 188.72.243.0 255.255.255.0 vpn_gateway,route 178.162.196.1 255.255.255.255 vpn_gateway,route 178.162.196.2 255.255.255.255 vpn_gateway,route 178.162.196.3 255.255.255.255 vpn_gateway,route 178.162.196.4 255.255.255.255 vpn_gateway,route 178.162.196.5 255.255.255.255 vpn_gateway,route 178.162.196.6 255.255.255.255 vpn_gateway,route 178.162.196.7 255.255.255.255 vpn_gateway,route 178.162.196.8 255.255.255.255 vpn_gateway,route 178.162.196.9 255.255.255.255 vpn_gateway,push-continuation 2'
  265. Tue Apr 9 17:00:31 2019 PUSH: Received control message: 'PUSH_REPLY,route 178.162.196.10 255.255.255.255 vpn_gateway,route 178.162.196.11 255.255.255.255 vpn_gateway,route 178.162.196.12 255.255.255.255 vpn_gateway,route 178.162.196.14 255.255.255.255 vpn_gateway,route 178.162.196.15 255.255.255.255 vpn_gateway,route 178.162.196.16 255.255.255.255 vpn_gateway,route 178.162.196.17 255.255.255.255 vpn_gateway,route 178.162.196.18 255.255.255.255 vpn_gateway,route 178.162.196.19 255.255.255.255 vpn_gateway,route 178.162.196.20 255.255.255.255 vpn_gateway,route 178.162.196.21 255.255.255.255 vpn_gateway,route 178.162.192.0 255.255.255.0 vpn_gateway,route 94.198.240.40 255.255.255.255 vpn_gateway,route 88.198.17.134 255.255.255.255 vpn_gateway,route 95.211.212.64 255.255.255.224 vpn_gateway,route 95.211.212.192 255.255.255.224 vpn_gateway,route 95.211.184.64 255.255.255.192 vpn_gateway,route 95.211.172.0 255.255.255.192 vpn_gateway,route 62.212.72.164 255.255.255.255 vpn_gateway,push-continuation 2'
  266. Tue Apr 9 17:00:31 2019 PUSH: Received control message: 'PUSH_REPLY,route 88.85.84.0 255.255.255.0 vpn_gateway,route 95.85.1.173 255.255.255.255 vpn_gateway,route 188.164.255.0 255.255.255.0 vpn_gateway,route 62.109.13.137 255.255.255.255 vpn_gateway,route 62.210.87.180 255.255.255.255 vpn_gateway,route 137.74.205.8 255.255.255.255 vpn_gateway,route 46.165.233.241 255.255.255.255 vpn_gateway,route 188.120.250.21 255.255.255.255 vpn_gateway,route 37.139.13.118 255.255.255.255 vpn_gateway,route 62.210.89.0 255.255.255.0 vpn_gateway,route 163.172.8.0 255.255.255.0 vpn_gateway,route 163.172.9.0 255.255.255.0 vpn_gateway,route 195.154.151.0 255.255.255.0 vpn_gateway,route 62.210.103.0 255.255.255.0 vpn_gateway,route 51.255.88.173 255.255.255.255 vpn_gateway,route 163.172.225.186 255.255.255.255 vpn_gateway,route 163.172.53.193 255.255.255.255 vpn_gateway,route 5.135.130.7 255.255.255.255 vpn_gateway,route 188.214.30.163 255.255.255.255 vpn_gateway,route 163.172.109.130 255.255.255.255 vpn_gateway,push-continuation 2'
  267. Tue Apr 9 17:00:32 2019 PUSH: Received control message: 'PUSH_REPLY,route 212.83.151.173 255.255.255.255 vpn_gateway,route 62.109.19.47 255.255.255.255 vpn_gateway,route 195.154.28.130 255.255.255.0 vpn_gateway,route 195.154.26.85 255.255.255.0 vpn_gateway,route 37.252.14.18 255.255.255.255 vpn_gateway ,route 5.45.65.111 255.255.255.255 vpn_gateway ,route 37.1.222.226 255.255.255.255 vpn_gateway ,route 10.10.1.0 255.255.255.0,topology net30,ping 20,ping-restart 65,ifconfig 10.10.1.102 10.10.1.101,push-continuation 1'
  268. Tue Apr 9 17:00:32 2019 OPTIONS IMPORT: timers and/or timeouts modified
  269. Tue Apr 9 17:00:32 2019 OPTIONS IMPORT: --ifconfig/up options modified
  270. Tue Apr 9 17:00:32 2019 OPTIONS IMPORT: route options modified
  271. Tue Apr 9 17:00:32 2019 Outgoing Data Channel: Cipher 'BF-CBC' initialized with 128 bit key
  272. Tue Apr 9 17:00:32 2019 WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
  273. Tue Apr 9 17:00:32 2019 Outgoing Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
  274. Tue Apr 9 17:00:32 2019 Incoming Data Channel: Cipher 'BF-CBC' initialized with 128 bit key
  275. Tue Apr 9 17:00:32 2019 WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
  276. Tue Apr 9 17:00:32 2019 Incoming Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
  277. Tue Apr 9 17:00:32 2019 WARNING: cipher with small block size in use, reducing reneg-bytes to 64MB to mitigate SWEET32 attacks.
  278. Tue Apr 9 17:00:32 2019 Preserving previous TUN/TAP instance: tun1
  279. Tue Apr 9 17:00:32 2019 Initialization Sequence Completed
  280. Tue Apr 9 17:00:37 2019 Connection reset, restarting [0]
  281. Tue Apr 9 17:00:37 2019 SIGUSR1[soft,connection-reset] received, process restarting
  282. Tue Apr 9 17:00:37 2019 Restart pause, 5 second(s)
  283. Tue Apr 9 17:00:42 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
  284. Tue Apr 9 17:00:42 2019 WARNING: normally if you use --mssfix and/or --fragment, you should also set --tun-mtu 1500 (currently it is 1450)
  285. Tue Apr 9 17:00:42 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]178.162.196.13:9999
  286. Tue Apr 9 17:00:42 2019 Socket Buffers: R=[87380->87380] S=[16384->16384]
  287. Tue Apr 9 17:00:42 2019 Attempting to establish TCP connection with [AF_INET]178.162.196.13:9999 [nonblock]
  288. Tue Apr 9 17:00:43 2019 TCP connection established with [AF_INET]178.162.196.13:9999
  289. Tue Apr 9 17:00:43 2019 TCP_CLIENT link local: (not bound)
  290. Tue Apr 9 17:00:43 2019 TCP_CLIENT link remote: [AF_INET]178.162.196.13:9999
  291. Tue Apr 9 17:00:43 2019 TLS: Initial packet from [AF_INET]178.162.196.13:9999, sid=1ba7b339 94b30bb0
  292. Tue Apr 9 17:00:44 2019 VERIFY OK: depth=1, C=RU, ST=MSK, L=Moscow, O=Turbobit, CN=Turbobit CA, emailAddress=techs@remsys.net
  293. Tue Apr 9 17:00:44 2019 VERIFY OK: depth=0, C=RU, ST=MSK, L=Moscow, O=Turbobit, CN=vpn.turbobit.ru, emailAddress=techs@remsys.net
  294. Tue Apr 9 17:00:45 2019 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1494', remote='link-mtu 1544'
  295. Tue Apr 9 17:00:45 2019 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1450', remote='tun-mtu 1500'
  296. Tue Apr 9 17:00:45 2019 Control Channel: TLSv1, cipher SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
  297. Tue Apr 9 17:00:45 2019 [vpn.turbobit.ru] Peer Connection Initiated with [AF_INET]178.162.196.13:9999
  298. Tue Apr 9 17:00:46 2019 SENT CONTROL [vpn.turbobit.ru]: 'PUSH_REQUEST' (status=1)
  299. Tue Apr 9 17:00:46 2019 PUSH: Received control message: 'PUSH_REPLY,route 192.168.10.0 255.255.255.0,route 188.72.202.185 255.255.255.255 vpn_gateway,route 85.17.76.16 255.255.255.248 vpn_gateway,route 94.75.232.0 255.255.255.0 vpn_gateway,route 85.17.74.0 255.255.255.0 vpn_gateway,route 95.211.105.209 255.255.255.255 vpn_gateway,route 95.211.80.9 255.255.255.255 vpn_gateway,route 178.236.176.189 255.255.255.255 vpn_gateway,route 95.211.188.0 255.255.255.0 vpn_gateway,route 94.198.241.0 255.255.255.0 vpn_gateway,route 188.72.243.0 255.255.255.0 vpn_gateway,route 178.162.196.1 255.255.255.255 vpn_gateway,route 178.162.196.2 255.255.255.255 vpn_gateway,route 178.162.196.3 255.255.255.255 vpn_gateway,route 178.162.196.4 255.255.255.255 vpn_gateway,route 178.162.196.5 255.255.255.255 vpn_gateway,route 178.162.196.6 255.255.255.255 vpn_gateway,route 178.162.196.7 255.255.255.255 vpn_gateway,route 178.162.196.8 255.255.255.255 vpn_gateway,route 178.162.196.9 255.255.255.255 vpn_gateway,push-continuation 2'
  300. Tue Apr 9 17:00:47 2019 PUSH: Received control message: 'PUSH_REPLY,route 178.162.196.10 255.255.255.255 vpn_gateway,route 178.162.196.11 255.255.255.255 vpn_gateway,route 178.162.196.12 255.255.255.255 vpn_gateway,route 178.162.196.14 255.255.255.255 vpn_gateway,route 178.162.196.15 255.255.255.255 vpn_gateway,route 178.162.196.16 255.255.255.255 vpn_gateway,route 178.162.196.17 255.255.255.255 vpn_gateway,route 178.162.196.18 255.255.255.255 vpn_gateway,route 178.162.196.19 255.255.255.255 vpn_gateway,route 178.162.196.20 255.255.255.255 vpn_gateway,route 178.162.196.21 255.255.255.255 vpn_gateway,route 178.162.192.0 255.255.255.0 vpn_gateway,route 94.198.240.40 255.255.255.255 vpn_gateway,route 88.198.17.134 255.255.255.255 vpn_gateway,route 95.211.212.64 255.255.255.224 vpn_gateway,route 95.211.212.192 255.255.255.224 vpn_gateway,route 95.211.184.64 255.255.255.192 vpn_gateway,route 95.211.172.0 255.255.255.192 vpn_gateway,route 62.212.72.164 255.255.255.255 vpn_gateway,push-continuation 2'
  301. Tue Apr 9 17:00:48 2019 PUSH: Received control message: 'PUSH_REPLY,route 88.85.84.0 255.255.255.0 vpn_gateway,route 95.85.1.173 255.255.255.255 vpn_gateway,route 188.164.255.0 255.255.255.0 vpn_gateway,route 62.109.13.137 255.255.255.255 vpn_gateway,route 62.210.87.180 255.255.255.255 vpn_gateway,route 137.74.205.8 255.255.255.255 vpn_gateway,route 46.165.233.241 255.255.255.255 vpn_gateway,route 188.120.250.21 255.255.255.255 vpn_gateway,route 37.139.13.118 255.255.255.255 vpn_gateway,route 62.210.89.0 255.255.255.0 vpn_gateway,route 163.172.8.0 255.255.255.0 vpn_gateway,route 163.172.9.0 255.255.255.0 vpn_gateway,route 195.154.151.0 255.255.255.0 vpn_gateway,route 62.210.103.0 255.255.255.0 vpn_gateway,route 51.255.88.173 255.255.255.255 vpn_gateway,route 163.172.225.186 255.255.255.255 vpn_gateway,route 163.172.53.193 255.255.255.255 vpn_gateway,route 5.135.130.7 255.255.255.255 vpn_gateway,route 188.214.30.163 255.255.255.255 vpn_gateway,route 163.172.109.130 255.255.255.255 vpn_gateway,push-continuation 2'
  302. Tue Apr 9 17:00:48 2019 PUSH: Received control message: 'PUSH_REPLY,route 212.83.151.173 255.255.255.255 vpn_gateway,route 62.109.19.47 255.255.255.255 vpn_gateway,route 195.154.28.130 255.255.255.0 vpn_gateway,route 195.154.26.85 255.255.255.0 vpn_gateway,route 37.252.14.18 255.255.255.255 vpn_gateway ,route 5.45.65.111 255.255.255.255 vpn_gateway ,route 37.1.222.226 255.255.255.255 vpn_gateway ,route 10.10.1.0 255.255.255.0,topology net30,ping 20,ping-restart 65,ifconfig 10.10.1.102 10.10.1.101,push-continuation 1'
  303. Tue Apr 9 17:00:48 2019 OPTIONS IMPORT: timers and/or timeouts modified
  304. Tue Apr 9 17:00:48 2019 OPTIONS IMPORT: --ifconfig/up options modified
  305. Tue Apr 9 17:00:48 2019 OPTIONS IMPORT: route options modified
  306. Tue Apr 9 17:00:48 2019 Outgoing Data Channel: Cipher 'BF-CBC' initialized with 128 bit key
  307. Tue Apr 9 17:00:48 2019 WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
  308. Tue Apr 9 17:00:48 2019 Outgoing Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
  309. Tue Apr 9 17:00:48 2019 Incoming Data Channel: Cipher 'BF-CBC' initialized with 128 bit key
  310. Tue Apr 9 17:00:48 2019 WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
  311. Tue Apr 9 17:00:48 2019 Incoming Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
  312. Tue Apr 9 17:00:48 2019 WARNING: cipher with small block size in use, reducing reneg-bytes to 64MB to mitigate SWEET32 attacks.
  313. Tue Apr 9 17:00:48 2019 Preserving previous TUN/TAP instance: tun1
  314. Tue Apr 9 17:00:48 2019 Initialization Sequence Completed
  315. ^CTue Apr 9 17:00:50 2019 event_wait : Interrupted system call (code=4)
  316. Tue Apr 9 17:00:50 2019 Closing TUN/TAP interface
  317. Tue Apr 9 17:00:50 2019 /sbin/ip addr del dev tun1 local 10.10.1.102 peer 10.10.1.101
  318. Tue Apr 9 17:00:50 2019 SIGINT[hard,] received, process exiting
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!