Computer loses network connectivity once connected

[esahins]

Hello all,

Until today, everything was working fine and I'm pretty sure I didn't change any configuration on my computer. But today, after connecting my VPN#2 (VPN#1 is still working fine), my internet connection goes down. I tried some route settings (which I don't have) but it didn't help. I'm sharing my VPN logs, can you help me please?

Code: Select all

Nov 07 11:26:16 PM: State changed to Connecting
Nov 07 11:26:16 PM: Viscosity Windows 1.11.3 (1828)
Nov 07 11:26:16 PM: Running on Microsoft Windows 11 Home 64 bit
Nov 07 11:26:16 PM: Running on .NET Framework Version 4.8.09032.533320
Nov 07 11:26:16 PM: Checking reachability status of connection...
Nov 07 11:26:16 PM: Connection is reachable. Starting connection attempt.
Nov 07 11:26:16 PM: Interface Type: ViscTunTap
Nov 07 11:26:16 PM: Bringing up interface...
Nov 07 11:26:16 PM: Note: --cipher is not set. OpenVPN versions before 2.5 defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
Nov 07 11:26:16 PM: OpenVPN 2.6.12 Windows [SSL (OpenSSL)] [LZO] [LZ4] [AEAD]
Nov 07 11:26:16 PM: library versions: OpenSSL 3.0.14 4 Jun 2024, LZO 2.10
Nov 07 11:26:16 PM: Resolving address: "[cencored].com"
Nov 07 11:26:17 PM: Valid endpoint found: [cencored].com:1194:udp
Nov 07 11:26:17 PM: TCP/UDP: Preserving recently used remote address: [AF_INET]185.89.248.32:1194
Nov 07 11:26:17 PM: UDPv4 link local: (not bound)
Nov 07 11:26:17 PM: UDPv4 link remote: [AF_INET]185.89.248.32:1194
Nov 07 11:26:17 PM: State changed to Authenticating
Nov 07 11:26:17 PM: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Nov 07 11:26:17 PM: [Aura OpenVPN Prod Server] Peer Connection Initiated with [AF_INET]185.89.248.32:1194
Nov 07 11:26:17 PM: State changed to Connecting
Nov 07 11:26:17 PM: WARNING: The block-outside-dns option has been ignored as it is not required under Viscosity's DNS management system. For more information please see the following article: https://www.sparklabs.com/support/kb/article/warning-the-block-outside-dns-option-has-been-ignored/
Nov 07 11:26:17 PM: Awaiting adapter to come up...
Nov 07 11:26:19 PM: Virtual Adapter Version: 0.7.2.1017
Nov 07 11:26:19 PM: Third-party filters attached to network interface: "Npcap Packet Driver (NPCAP) (INSECURE_NPCAP)".
Nov 07 11:26:20 PM: TAP-WIN32 device [VPN#2] opened: \\?\root#net#0001#{adda4c48-c32e-4ef6-9602-b3252f082583}, index: 24
Nov 07 11:26:21 PM: Waiting for DNS Setup to complete...
Nov 07 11:26:21 PM: Successful ARP Flush on interface [24] {F21771A3-667A-402E-8F5B-1BDBFCC4A716}
Nov 07 11:26:22 PM: Warning: route gateway is ambiguous: 192.168.0.1 (2 matches)
Nov 07 11:26:22 PM: Initialization Sequence Completed
Nov 07 11:26:22 PM: DNS set to Full:
Server: 172.18.0.24:53, Lookup Type: Any, Domains: None
Nov 07 11:26:22 PM: State changed to Connected
Nov 07 11:26:22 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)
Nov 07 11:26:23 PM: NOTE: --mute triggered...

I've highlighted some potential problems below.

• Nov 07 11:26:17 PM: WARNING: The block-outside-dns option has been ignored as it is not required under Viscosity's DNS management system. For more information please see the following article: https://www.sparklabs.com/support/kb/ar ... n-ignored/
• Nov 07 11:26:22 PM: Warning: route gateway is ambiguous: 192.168.0.1 (2 matches)
• Nov 07 11:26:22 PM: write UDPv4: No Route to Host (WSAEHOSTUNREACH) (fd=194,code=10065)

[esahins]

It's working again and I haven't changed anything.

I'll share the latest log with anyone who might be interested.

Code: Select all

Nov 08 5:48:03 PM: State changed to Connecting
Nov 08 5:48:03 PM: Viscosity Windows 1.11.3 (1828)
Nov 08 5:48:04 PM: Running on Microsoft Windows 11 Home 64 bit
Nov 08 5:48:04 PM: Running on .NET Framework Version 4.8.09032.533320
Nov 08 5:48:04 PM: Checking reachability status of connection...
Nov 08 5:48:04 PM: Connection is reachable. Starting connection attempt.
Nov 08 5:48:04 PM: Interface Type: ViscTunTap
Nov 08 5:48:04 PM: Bringing up interface...
Nov 08 5:48:04 PM: Note: --cipher is not set. OpenVPN versions before 2.5 defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
Nov 08 5:48:04 PM: OpenVPN 2.6.12 Windows [SSL (OpenSSL)] [LZO] [LZ4] [AEAD]
Nov 08 5:48:04 PM: library versions: OpenSSL 3.0.14 4 Jun 2024, LZO 2.10
Nov 08 5:48:04 PM: Resolving address: "[censored].com"
Nov 08 5:48:04 PM: Valid endpoint found: [censored].com:1194:udp
Nov 08 5:48:04 PM: TCP/UDP: Preserving recently used remote address: [AF_INET]185.89.248.32:1194
Nov 08 5:48:04 PM: UDPv4 link local: (not bound)
Nov 08 5:48:04 PM: UDPv4 link remote: [AF_INET]185.89.248.32:1194
Nov 08 5:48:04 PM: State changed to Authenticating
Nov 08 5:48:04 PM: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Nov 08 5:48:04 PM: [Aura OpenVPN Prod Server] Peer Connection Initiated with [AF_INET]185.89.248.32:1194
Nov 08 5:48:04 PM: State changed to Connecting
Nov 08 5:48:05 PM: WARNING: The block-outside-dns option has been ignored as it is not required under Viscosity's DNS management system. For more information please see the following article: https://www.sparklabs.com/support/kb/article/warning-the-block-outside-dns-option-has-been-ignored/
Nov 08 5:48:05 PM: Awaiting adapter to come up...
Nov 08 5:48:08 PM: Virtual Adapter Version: 0.7.2.1017
Nov 08 5:48:08 PM: Third-party filters attached to network interface: "Npcap Packet Driver (NPCAP) (INSECURE_NPCAP)".
Nov 08 5:48:09 PM: TAP-WIN32 device VPN#2 opened: \\?\root#net#0001#{adda4c48-c32e-4ef6-9602-b3252f082583}, index: 24
Nov 08 5:48:10 PM: Waiting for DNS Setup to complete...
Nov 08 5:48:10 PM: Successful ARP Flush on interface [24] {F21771A3-667A-402E-8F5B-1BDBFCC4A716}
Nov 08 5:48:11 PM: Warning: route gateway is ambiguous: 192.168.0.1 (2 matches)
Nov 08 5:48:11 PM: Initialization Sequence Completed
Nov 08 5:48:11 PM: DNS set to Full:
Server: 172.18.0.24:53, Lookup Type: Any, Domains: None
Nov 08 5:48:11 PM: State changed to Connected