AirGuy24 0 Posted ... Hello, I'm using the Eddie client v2.24.2 to connect via WireGuard and I'm unable to get it working. It keeps hanging on "Checking route IPv4" then eventually restarts the connection. I've tested this with the WireGuard client (which works) so UDP 1637 is *not* being blocked: I 2024.04.17 10:41:46 - Session starting. I 2024.04.17 10:41:47 - Checking authorization ... ! 2024.04.17 10:41:47 - Connecting to Wurren (Canada, Toronto, Ontario) . 2024.04.17 10:41:47 - Routes, add 199.189.27.125/32 for interface "Prod - DHCP (Red Hat VirtIO Ethernet Adapter)". . 2024.04.17 10:41:47 - WireGuard > Setup start . 2024.04.17 10:41:48 - WireGuard > Setup complete . 2024.04.17 10:41:48 - WireGuard > Starting WireGuard/0.5.3 (Windows 10.0.19045; amd64) . 2024.04.17 10:41:48 - WireGuard > Watching network interfaces . 2024.04.17 10:41:48 - WireGuard > Resolving DNS names . 2024.04.17 10:41:48 - WireGuard > Creating network adapter . 2024.04.17 10:41:48 - WireGuard > Warning: the VirtIO network driver (NetKVM) is out of date and may cause known problems; please update to v100.85.104.20800 or later . 2024.04.17 10:41:48 - WireGuard > Using existing driver 0.10 . 2024.04.17 10:41:48 - WireGuard > Creating adapter . 2024.04.17 10:41:48 - WireGuard > Using WireGuardNT/0.10 . 2024.04.17 10:41:48 - WireGuard > Dropping privileges . 2024.04.17 10:41:48 - WireGuard > Setup interface . 2024.04.17 10:41:48 - WireGuard > Setting interface configuration . 2024.04.17 10:41:48 - WireGuard > Interface created . 2024.04.17 10:41:48 - WireGuard > Peer 1 created . 2024.04.17 10:41:48 - WireGuard > Setting device v6 addresses . 2024.04.17 10:41:48 - WireGuard > Interface up . 2024.04.17 10:41:48 - WireGuard > Setting device v4 addresses . 2024.04.17 10:41:48 - WireGuard > Startup complete . 2024.04.17 10:41:48 - WireGuard > Received first handshake . 2024.04.17 10:41:48 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2024.04.17 10:41:48 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2024.04.17 10:41:48 - DNS leak protection with packet filtering enabled. . 2024.04.17 10:41:48 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2024.04.17 10:41:48 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2024.04.17 10:41:48 - DNS IPv4 of a network adapter forced (Prod - DHCP, from automatic to 10.128.0.1) . 2024.04.17 10:41:48 - DNS IPv6 of a network adapter forced (Prod - DHCP, from automatic to fd7d:76ee:e68f:a993::1) . 2024.04.17 10:41:48 - DNS IPv4 of a network adapter forced (Prod - Local - 192.168.10.105, from automatic to 10.128.0.1) . 2024.04.17 10:41:49 - DNS IPv6 of a network adapter forced (Prod - Local - 192.168.10.105, from automatic to fd7d:76ee:e68f:a993::1) . 2024.04.17 10:41:49 - Routes, add 0.0.0.0/1 for interface "Eddie (WireGuard Tunnel)". . 2024.04.17 10:41:49 - Routes, add 128.0.0.0/1 for interface "Eddie (WireGuard Tunnel)". . 2024.04.17 10:41:49 - Routes, add ::/1 for interface "Eddie (WireGuard Tunnel)". . 2024.04.17 10:41:49 - Routes, add 8000::/1 for interface "Eddie (WireGuard Tunnel)". . 2024.04.17 10:41:49 - Routes, add 199.189.27.123/32 for interface "Eddie (WireGuard Tunnel)". . 2024.04.17 10:41:50 - Routes, add 2001:550:907:23:7413:852c:e946:eefa/128 for interface "Eddie (WireGuard Tunnel)". . 2024.04.17 10:41:50 - Flushing DNS I 2024.04.17 10:41:50 - Checking route IPv4 . 2024.04.17 10:42:26 - Checking route (4° try) . 2024.04.17 10:42:40 - Checking route (5° try) E 2024.04.17 10:42:50 - Checking route IPv4 failed, last reason: Fetch url error:Timeout was reached . 2024.04.17 10:42:50 - WireGuard > Retrying handshake with peer 1 (199.189.27.125:1637) because we stopped hearing back after 15 seconds . 2024.04.17 10:42:50 - WireGuard > Retrying handshake with peer 1 (199.189.27.125:1637) because we stopped hearing back after 15 seconds . 2024.04.17 10:42:50 - WireGuard > Retrying handshake with peer 1 (199.189.27.125:1637) because we stopped hearing back after 15 seconds . 2024.04.17 10:42:50 - WireGuard > Handshake for peer 1 (199.189.27.125:1637) did not complete after 5 seconds, retrying (try 2) ! 2024.04.17 10:42:50 - Disconnecting . 2024.04.17 10:42:50 - WireGuard > Stop request received . 2024.04.17 10:42:50 - WireGuard > Stopping . 2024.04.17 10:42:51 - WireGuard > Completed . 2024.04.17 10:42:51 - Routes, delete 0.0.0.0/1 for interface "{7CB6D269-0786-7E57-C13F-6CDFFF02FB02}", not exists. . 2024.04.17 10:42:51 - Routes, delete 128.0.0.0/1 for interface "{7CB6D269-0786-7E57-C13F-6CDFFF02FB02}", not exists. . 2024.04.17 10:42:51 - Routes, delete ::/1 for interface "{7CB6D269-0786-7E57-C13F-6CDFFF02FB02}", not exists. . 2024.04.17 10:42:51 - Routes, delete 8000::/1 for interface "{7CB6D269-0786-7E57-C13F-6CDFFF02FB02}", not exists. . 2024.04.17 10:42:51 - Routes, delete 199.189.27.125/32 for interface "Prod - DHCP (Red Hat VirtIO Ethernet Adapter)". . 2024.04.17 10:42:51 - Routes, delete 199.189.27.123/32 for interface "{7CB6D269-0786-7E57-C13F-6CDFFF02FB02}", not exists. . 2024.04.17 10:42:51 - Routes, delete 2001:550:907:23:7413:852c:e946:eefa/128 for interface "{7CB6D269-0786-7E57-C13F-6CDFFF02FB02}", not exists. . 2024.04.17 10:42:51 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2024.04.17 10:42:52 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2024.04.17 10:42:52 - DNS IPv4 of a network adapter restored to original settings (Prod - DHCP, to automatic) . 2024.04.17 10:42:52 - DNS IPv6 of a network adapter restored to original settings (Prod - DHCP, to automatic) . 2024.04.17 10:42:52 - DNS IPv4 of a network adapter restored to original settings (Prod - Local - 192.168.10.105, to automatic) . 2024.04.17 10:42:52 - DNS IPv6 of a network adapter restored to original settings (Prod - Local - 192.168.10.105, to automatic) . 2024.04.17 10:42:52 - DNS leak protection with packet filtering disabled. . 2024.04.17 10:42:52 - Connection terminated. Share this post Link to post
Staff 9972 Posted ... @AirGuy24 Hello! The route check failure claimed by Eddie seems correct, because it is confirmed by WireGuard: 52 minutes ago, AirGuy24 said: . 2024.04.17 10:42:50 - WireGuard > Retrying handshake with peer 1 (199.189.27.125:1637) because we stopped hearing back after 15 seconds . 2024.04.17 10:42:50 - WireGuard > Handshake for peer 1 (199.189.27.125:1637) did not complete after 5 seconds, retrying (try 2) Therefore, this problem could be peculiar to the WireGuard code implemented in Eddie 2.21 (or Eddie is blocked by some other blocking tool, can you please check?) and the new WireGuard resolves the problem. Can you please test whether or not the same problem occurs with Eddie 2.24.x? Please see here to download it: https://airvpn.org/forums/topic/57401-eddie-desktop-224-beta-released/ Kind regards Share this post Link to post
AirGuy24 0 Posted ... 18 minutes ago, Staff said: @AirGuy24 Hello! The route check failure claimed by Eddie seems correct, because it is confirmed by WireGuard: Therefore, this problem could be peculiar to the WireGuard code implemented in Eddie 2.21 (or Eddie is blocked by some other blocking tool, can you please check?) and the new WireGuard resolves the problem. Can you please test whether or not the same problem occurs with Eddie 2.24.x? Please see here to download it: https://airvpn.org/forums/topic/57401-eddie-desktop-224-beta-released/ Kind regards Hello! - I was using 2.24.x. The issue was with the adapter for Windows 10.. Once I updated that (current version is v100.94.104.24800), the tunnels started working. 2024.04.17 10:41:48 - WireGuard > Warning: the VirtIO network driver (NetKVM) is out of date and may cause known problems; please update to v100.85.104.20800 or later Share this post Link to post