Temat: OpenVPN na gargoyle się rozsypał
Cześć
Próbowałem połączyć się na trzech urządzeniach z domowym routerem na openvpn. Nie można połączyć się, a logi są takie:
Mon Nov 25 07:36:45 2024 OpenVPN 2.5.5 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 15 2021
Mon Nov 25 07:36:45 2024 Windows version 10.0 (Windows 10 or greater) 64bit
Mon Nov 25 07:36:45 2024 library versions: OpenSSL 1.1.1l 24 Aug 2021, LZO 2.10
Mon Nov 25 07:36:45 2024 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Mon Nov 25 07:36:45 2024 Need hold release from management interface, waiting...
Mon Nov 25 07:36:46 2024 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Mon Nov 25 07:36:46 2024 MANAGEMENT: CMD 'state on'
Mon Nov 25 07:36:46 2024 MANAGEMENT: CMD 'log all on'
Mon Nov 25 07:36:46 2024 MANAGEMENT: CMD 'echo all on'
Mon Nov 25 07:36:46 2024 MANAGEMENT: CMD 'bytecount 5'
Mon Nov 25 07:36:46 2024 MANAGEMENT: CMD 'hold off'
Mon Nov 25 07:36:46 2024 MANAGEMENT: CMD 'hold release'
Mon Nov 25 07:36:46 2024 WARNING: INSECURE cipher (BF-CBC) 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). Support for these insecure ciphers will be removed in OpenVPN 2.7.
Mon Nov 25 07:36:46 2024 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Nov 25 07:36:46 2024 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Nov 25 07:36:46 2024 MANAGEMENT: >STATE:1732516606,RESOLVE,,,,,,
Mon Nov 25 07:36:46 2024 TCP/UDP: Preserving recently used remote address: [AF_INET]178.235.17.103:443
Mon Nov 25 07:36:46 2024 Socket Buffers: R=[65536->65536] S=[65536->65536]
Mon Nov 25 07:36:46 2024 Attempting to establish TCP connection with [AF_INET]178.235.17.103:443 [nonblock]
Mon Nov 25 07:36:46 2024 MANAGEMENT: >STATE:1732516606,TCP_CONNECT,,,,,,
Mon Nov 25 07:36:46 2024 TCP connection established with [AF_INET]178.235.17.103:443
Mon Nov 25 07:36:46 2024 TCP_CLIENT link local: (not bound)
Mon Nov 25 07:36:46 2024 TCP_CLIENT link remote: [AF_INET]178.235.17.103:443
Mon Nov 25 07:36:46 2024 MANAGEMENT: >STATE:1732516606,WAIT,,,,,,
Mon Nov 25 07:36:46 2024 MANAGEMENT: >STATE:1732516606,AUTH,,,,,,
Mon Nov 25 07:36:46 2024 TLS: Initial packet from [AF_INET]178.235.17.103:443, sid=4d4c354a 0a056fa0
Mon Nov 25 07:36:46 2024 VERIFY OK: depth=1, C=??, ST=UnknownProvince, L=UnknownCity, O=UnknownOrg, OU=UnknownOrgUnit, CN=ddjxovruvfcahaa, emailAddress=ddjxovruvfcahaa@phdopmlvcieescz.com
Mon Nov 25 07:36:46 2024 VERIFY KU OK
Mon Nov 25 07:36:46 2024 Validating certificate extended key usage
Mon Nov 25 07:36:46 2024 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Mon Nov 25 07:36:46 2024 VERIFY EKU OK
Mon Nov 25 07:36:46 2024 VERIFY OK: depth=0, C=??, ST=UnknownProvince, L=UnknownCity, O=UnknownOrg, OU=UnknownOrgUnit, CN=server, emailAddress=ddjxovruvfcahaa@phdopmlvcieescz.com
Mon Nov 25 07:36:46 2024 Connection reset, restarting [0]Konfiguracja klienta:
client
remote domena.duckdns.org 443
dev tun
proto tcp-client
status current_status
resolv-retry infinite
remote-cert-tls server
topology subnet
verb 3
data-ciphers AES-256-GCM
nobind
persist-key
persist-tun
push-peer-info
<ca>
-----BEGIN CERTIFICATE-----Na ten moment jestem poza domem, więc nie mam dostępu do routera. Konfiguracja routera nie była zmieniana od wielu miesięcy, a cały czas połączenie działało. Nawet na wszelki wypadek ustawiłem restart routera w nocy, żeby zapobiec zawieszaniu się na skutek jakiegoś ukrytego błędu oprogramowania, który może spowodować usterkę.
Linksys WRT3200ACM (Gargoyle)
Tp-link 1043NDv2 (Gargoyle)