port 1194
proto udp
dev tun
ca "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\server.crt"
key "C:\\Program Files\\OpenVPN\\config\\server.key" # This file should be kept secret
dh "C:\\Program Files\\OpenVPN\\config\\dh.pem"
topology subnet
server 10.8.0.0 255.255.255.0
push "route 192.168.1.0 255.255.255.0"
route 192.168.100.0 255.255.255.0
client-config-dir "C:\\Program Files\\OpenVPN\\config\\ccd"
client-to-client
keepalive 10 120
tls-auth "C:\\Program Files\\OpenVPN\\config\\tls-auth.key" 0 # This file is secret
cipher AES-256-CBC
max-clients 1000
user nobody
group nogroup
persist-key
persist-tun
status openvpn-status.log
verb 3
explicit-exit-notify 1
ссd клиент
ifconfig-push 10.8.0.2 255.255.255.0
route 192.168.100.0 255.255.255.0
лог сервера
Wed May 4 15:47:59 2022 NOTE: --user option is not implemented on Windows
Wed May 4 15:47:59 2022 NOTE: --group option is not implemented on Windows
Wed May 4 15:47:59 2022 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.
Wed May 4 15:47:59 2022 --pull-filter ignored for --mode server
Wed May 4 15:47:59 2022 OpenVPN 2.5.6 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Mar 16 2022
Wed May 4 15:47:59 2022 Windows version 10.0 (Windows 10 or greater) 64bit
Wed May 4 15:47:59 2022 library versions: OpenSSL 1.1.1n 15 Mar 2022, LZO 2.10
Wed May 4 15:47:59 2022 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed May 4 15:47:59 2022 Need hold release from management interface, waiting...
Wed May 4 15:47:59 2022 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'state on'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'log all on'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'echo all on'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'bytecount 5'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'hold off'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'hold release'
Wed May 4 15:47:59 2022 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.
Wed May 4 15:47:59 2022 Diffie-Hellman initialized with 2048 bit key
Wed May 4 15:47:59 2022 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 4 15:47:59 2022 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 4 15:47:59 2022 interactive service msg_channel=916
Wed May 4 15:47:59 2022 open_tun
Wed May 4 15:47:59 2022 tap-windows6 device [OpenVPN TAP-Windows6] opened
Wed May 4 15:47:59 2022 TAP-Windows Driver Version 9.24
Wed May 4 15:47:59 2022 Set TAP-Windows TUN subnet mode network/local/netmask = 10.8.0.0/10.8.0.1/255.255.255.0 [SUCCEEDED]
Wed May 4 15:47:59 2022 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.1/255.255.255.0 on interface {81D8ACB4-A086-410F-881A-FB6D22592CEB} [DHCP-serv: 10.8.0.0, lease-time: 31536000]
Wed May 4 15:47:59 2022 Sleeping for 10 seconds...
Wed May 4 15:48:09 2022 Successful ARP Flush on interface [12] {81D8ACB4-A086-410F-881A-FB6D22592CEB}
Wed May 4 15:48:09 2022 MANAGEMENT: >STATE:1651657689,ASSIGN_IP,,10.8.0.1,,,,
Wed May 4 15:48:09 2022 IPv4 MTU set to 1500 on interface 12 using service
Wed May 4 15:48:09 2022 MANAGEMENT: >STATE:1651657689,ADD_ROUTES,,,,,,
Wed May 4 15:48:09 2022 C:\Windows\system32\route.exe ADD 192.168.100.0 MASK 255.255.255.0 10.8.0.2
Wed May 4 15:48:09 2022 Route addition via service succeeded
Wed May 4 15:48:09 2022 Could not determine IPv4/IPv6 protocol. Using AF_INET6
Wed May 4 15:48:09 2022 Socket Buffers: R=[131072->131072] S=[131072->131072]
Wed May 4 15:48:09 2022 setsockopt(IPV6_V6ONLY=0)
Wed May 4 15:48:09 2022 UDPv6 link local (bound): [AF_INET6][undef]:1194
Wed May 4 15:48:09 2022 UDPv6 link remote: [AF_UNSPEC]
Wed May 4 15:48:09 2022 MULTI: multi_init called, r=256 v=256
Wed May 4 15:48:09 2022 IFCONFIG POOL IPv4: base=10.8.0.2 size=253
Wed May 4 15:48:09 2022 Initialization Sequence Completed
Wed May 4 15:48:09 2022 MANAGEMENT: >STATE:1651657689,CONNECTED,SUCCESS,10.8.0.1,,,,
Wed May 4 15:48:14 2022 37.150.43.150:54614 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 4 15:48:14 2022 37.150.43.150:54614 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 4 15:48:14 2022 37.150.43.150:54614 TLS: Initial packet from [AF_INET6]::ffff:37.150.43.150:54614, sid=0e240efd 403283f9
Wed May 4 15:48:14 2022 37.150.43.150:54614 VERIFY OK: depth=1, CN=server
Wed May 4 15:48:14 2022 37.150.43.150:54614 VERIFY OK: depth=0, CN=Home
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_VER=2.5.6
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_PLAT=win
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_PROTO=6
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_NCP=2
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_CIPHERS=AES-256-GCM:AES-128-GCM
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_LZ4=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_LZ4v2=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_LZO=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_COMP_STUB=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_COMP_STUBv2=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_TCPNL=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_SSO=openurl,crtext
Wed May 4 15:48:14 2022 37.150.43.150:54614 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1549'
Wed May 4 15:48:14 2022 37.150.43.150:54614 WARNING: 'auth' is used inconsistently, local='auth SHA1', remote='auth [null-digest]'
Wed May 4 15:48:14 2022 37.150.43.150:54614 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
Wed May 4 15:48:14 2022 37.150.43.150:54614 [Home] Peer Connection Initiated with [AF_INET6]::ffff:37.150.43.150:54614
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 MULTI_sva: pool returned IPv4=10.8.0.2, IPv6=(Not enabled)
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 OPTIONS IMPORT: reading client specific options from: C:\Program Files\OpenVPN\config\ccd\Home
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 Options error: option 'route' cannot be used in this context (C:\Program Files\OpenVPN\config\ccd\Home)
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 MULTI: Learn: 10.8.0.2 -> Home/37.150.43.150:54614
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 MULTI: primary virtual IP for Home/37.150.43.150:54614: 10.8.0.2
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 SENT CONTROL [Home]: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
res2001, Планировал на openwrt роутер завязать конкретный файл клиент.ovpn . Подогнать камеры под сеть овпн и на реге тоже поменять. и шлюз на камерах писать впна?
Там только камеры и регистратор, можно баловаться с настройками обоих
2) ( 2 впн клиент) Камеры у нас сейчас за 2ым впн клиентом. Так как там пк, то решение я уже нашел. просто ПО прокинул на сервер уже с готовыми настроенными камерами
3) (3 впн клиент) Сейчас остро интересуют камеры за видеорегистратором за отсутствием пк в сети при помощи прошитого роутера через openwrt (роутер еще не поставил, заранее думаю)
res2001, А если просто камеры загнать в подсеть впн? 10.8.1.1 микротик, 10.8.1.2-254 камеры ?
1) сам впн сервер по локальному адресу тоже не пингует, хотя маршруты есть
2) Сразу отключаю, с правилами на данном этапе не замарачиваюсь
Я не понял как прописать локалку камер что видно было , сервер сразу дает ошибку на адрес 172.22.24.0 255.255.248.0
res2001, C камерами решил момент, через ПО для камер.
Думаю еще над таким вопросом . А если у меня будет не видеосервер(ПК) , а просто регистратор ... тогда возможен роутер микротик понадобится .ХМ
Сеть за клиентом пока можно отпустить. Интересует почему первый впн клиент не пингует локалку за впн сервером
res2001, Да, фаервол отключить забыл.. заработался уже .
Маршрут на сервере так и не добавился .
на втором впн клиенте ccd не добавлял iroute . попробовал там добавить айпи камер 172.22.24.0 255.255.248.0 в итоге получил ошибку на адрес и оставил на завтра
Главное что до меня наконец то дошло : что не нужно писать в доп айпи под сети устройств(камер) и прочего . Если все правильно прописано в овпн все и так работает
res2001, Тут я с Вами полностью согласен. Сижу допиливаю сервак на обьекте (2клиент впн с камерами) . Быстренько состряпал и он пингует впн сервак, впн клиента, впн сервак по локал адресу. За то его не пингует не сервер не клиент впн по впн адресу.. бред какой то
2 впн клиент
C:\Users\Администратор>ping 10.8.0.1
Обмен пакетами с 10.8.0.1 по с 32 байтами данных:
Ответ от 10.8.0.1: число байт=32 время=31мс TTL=128
Ответ от 10.8.0.1: число байт=32 время=30мс TTL=128
Ответ от 10.8.0.1: число байт=32 время=31мс TTL=128
Ответ от 10.8.0.1: число байт=32 время=31мс TTL=128
Обмен пакетами с 10.8.0.2 по с 32 байтами данных:
Ответ от 10.8.0.2: число байт=32 время=63мс TTL=128
Ответ от 10.8.0.2: число байт=32 время=64мс TTL=128
Ответ от 10.8.0.2: число байт=32 время=63мс TTL=128
Ответ от 10.8.0.2: число байт=32 время=63мс TTL=128
Обмен пакетами с 192.168.1.245 по с 32 байтами данных:
Ответ от 192.168.1.245: число байт=32 время=31мс TTL=127
Ответ от 192.168.1.245: число байт=32 время=31мс TTL=127
Ответ от 192.168.1.245: число байт=32 время=31мс TTL=127
Ответ от 192.168.1.245: число байт=32 время=31мс TTL=127
res2001,
Вот такая ошибка появилась в логе сервера:
Wed Apr 27 21:08:29 2022 Home/37.150.43.150:55686 Options error: option 'route' cannot be used in this context (C:\Program Files\OpenVPN\config\ccd\Home)
port 1194
proto udp
dev tun
ca "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\server.crt"
key "C:\\Program Files\\OpenVPN\\config\\server.key" # This file should be kept secret
dh "C:\\Program Files\\OpenVPN\\config\\dh.pem"
topology subnet
server 10.8.0.0 255.255.255.0
;ifconfig-pool-persist ipp.txt
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
push "route 192.168.1.0 255.255.255.0"
# 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 "C:\\Program Files\\OpenVPN\\config\\ccd"
# 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
client-to-client
keepalive 10 120
tls-auth "C:\\Program Files\\OpenVPN\\config\\tls-auth.key" 0 # This file is secret
cipher AES-256-CBC
max-clients 1000
user nobody
group nogroup
persist-key
persist-tun
status openvpn-status.log
verb 3
explicit-exit-notify 1
я вручную создавал папку ccd и файл клиента, потому что при подключении не появился. скинул с хештегами что бы было понятно
Сменил адрес в ifconfig-push не поменялся ip . Перезагрузил и сервер и клиент
res2001, Я по прежнему не добился того что бы "впн клиент" пинговал "локалку впн сервера" и "впн сервер" что бы пинговал "локальный адрес клиента". (напомню что впн клиент дом.комп подопытный)
Перечитав все описанное выше обратил внимание что : на сервере не появляются маршруты до локальной сети(за впн клиентом) .
Они у нас в ссd/client:
ifconfig-push 10.8.0.2 255.255.255.0 ( впн клиент)
port 1194
proto udp
dev tun
ca "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\server.crt"
key "C:\\Program Files\\OpenVPN\\config\\server.key" # This file should be kept secret
dh "C:\\Program Files\\OpenVPN\\config\\dh.pem"
topology subnet
server 10.8.0.0 255.255.255.0
push "route 192.168.1.0 255.255.255.0"
route 192.168.100.0 255.255.255.0
client-config-dir "C:\\Program Files\\OpenVPN\\config\\ccd"
client-to-client
keepalive 10 120
tls-auth "C:\\Program Files\\OpenVPN\\config\\tls-auth.key" 0 # This file is secret
cipher AES-256-CBC
max-clients 1000
user nobody
group nogroup
persist-key
persist-tun
status openvpn-status.log
verb 3
explicit-exit-notify 1
ifconfig-push 10.8.0.2 255.255.255.0
route 192.168.100.0 255.255.255.0
Wed May 4 15:47:59 2022 NOTE: --user option is not implemented on Windows
Wed May 4 15:47:59 2022 NOTE: --group option is not implemented on Windows
Wed May 4 15:47:59 2022 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.
Wed May 4 15:47:59 2022 --pull-filter ignored for --mode server
Wed May 4 15:47:59 2022 OpenVPN 2.5.6 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Mar 16 2022
Wed May 4 15:47:59 2022 Windows version 10.0 (Windows 10 or greater) 64bit
Wed May 4 15:47:59 2022 library versions: OpenSSL 1.1.1n 15 Mar 2022, LZO 2.10
Wed May 4 15:47:59 2022 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed May 4 15:47:59 2022 Need hold release from management interface, waiting...
Wed May 4 15:47:59 2022 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'state on'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'log all on'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'echo all on'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'bytecount 5'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'hold off'
Wed May 4 15:47:59 2022 MANAGEMENT: CMD 'hold release'
Wed May 4 15:47:59 2022 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.
Wed May 4 15:47:59 2022 Diffie-Hellman initialized with 2048 bit key
Wed May 4 15:47:59 2022 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 4 15:47:59 2022 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 4 15:47:59 2022 interactive service msg_channel=916
Wed May 4 15:47:59 2022 open_tun
Wed May 4 15:47:59 2022 tap-windows6 device [OpenVPN TAP-Windows6] opened
Wed May 4 15:47:59 2022 TAP-Windows Driver Version 9.24
Wed May 4 15:47:59 2022 Set TAP-Windows TUN subnet mode network/local/netmask = 10.8.0.0/10.8.0.1/255.255.255.0 [SUCCEEDED]
Wed May 4 15:47:59 2022 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.1/255.255.255.0 on interface {81D8ACB4-A086-410F-881A-FB6D22592CEB} [DHCP-serv: 10.8.0.0, lease-time: 31536000]
Wed May 4 15:47:59 2022 Sleeping for 10 seconds...
Wed May 4 15:48:09 2022 Successful ARP Flush on interface [12] {81D8ACB4-A086-410F-881A-FB6D22592CEB}
Wed May 4 15:48:09 2022 MANAGEMENT: >STATE:1651657689,ASSIGN_IP,,10.8.0.1,,,,
Wed May 4 15:48:09 2022 IPv4 MTU set to 1500 on interface 12 using service
Wed May 4 15:48:09 2022 MANAGEMENT: >STATE:1651657689,ADD_ROUTES,,,,,,
Wed May 4 15:48:09 2022 C:\Windows\system32\route.exe ADD 192.168.100.0 MASK 255.255.255.0 10.8.0.2
Wed May 4 15:48:09 2022 Route addition via service succeeded
Wed May 4 15:48:09 2022 Could not determine IPv4/IPv6 protocol. Using AF_INET6
Wed May 4 15:48:09 2022 Socket Buffers: R=[131072->131072] S=[131072->131072]
Wed May 4 15:48:09 2022 setsockopt(IPV6_V6ONLY=0)
Wed May 4 15:48:09 2022 UDPv6 link local (bound): [AF_INET6][undef]:1194
Wed May 4 15:48:09 2022 UDPv6 link remote: [AF_UNSPEC]
Wed May 4 15:48:09 2022 MULTI: multi_init called, r=256 v=256
Wed May 4 15:48:09 2022 IFCONFIG POOL IPv4: base=10.8.0.2 size=253
Wed May 4 15:48:09 2022 Initialization Sequence Completed
Wed May 4 15:48:09 2022 MANAGEMENT: >STATE:1651657689,CONNECTED,SUCCESS,10.8.0.1,,,,
Wed May 4 15:48:14 2022 37.150.43.150:54614 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 4 15:48:14 2022 37.150.43.150:54614 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 4 15:48:14 2022 37.150.43.150:54614 TLS: Initial packet from [AF_INET6]::ffff:37.150.43.150:54614, sid=0e240efd 403283f9
Wed May 4 15:48:14 2022 37.150.43.150:54614 VERIFY OK: depth=1, CN=server
Wed May 4 15:48:14 2022 37.150.43.150:54614 VERIFY OK: depth=0, CN=Home
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_VER=2.5.6
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_PLAT=win
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_PROTO=6
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_NCP=2
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_CIPHERS=AES-256-GCM:AES-128-GCM
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_LZ4=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_LZ4v2=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_LZO=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_COMP_STUB=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_COMP_STUBv2=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_TCPNL=1
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_GUI_VER=OpenVPN_GUI_11
Wed May 4 15:48:14 2022 37.150.43.150:54614 peer info: IV_SSO=openurl,crtext
Wed May 4 15:48:14 2022 37.150.43.150:54614 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1549'
Wed May 4 15:48:14 2022 37.150.43.150:54614 WARNING: 'auth' is used inconsistently, local='auth SHA1', remote='auth [null-digest]'
Wed May 4 15:48:14 2022 37.150.43.150:54614 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
Wed May 4 15:48:14 2022 37.150.43.150:54614 [Home] Peer Connection Initiated with [AF_INET6]::ffff:37.150.43.150:54614
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 MULTI_sva: pool returned IPv4=10.8.0.2, IPv6=(Not enabled)
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 OPTIONS IMPORT: reading client specific options from: C:\Program Files\OpenVPN\config\ccd\Home
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 Options error: option 'route' cannot be used in this context (C:\Program Files\OpenVPN\config\ccd\Home)
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 MULTI: Learn: 10.8.0.2 -> Home/37.150.43.150:54614
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 MULTI: primary virtual IP for Home/37.150.43.150:54614: 10.8.0.2
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed May 4 15:48:14 2022 Home/37.150.43.150:54614 SENT CONTROL [Home]: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)