Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ISSUE: Connection not working #181

Open
K14Mua opened this issue Apr 13, 2024 · 16 comments
Open

ISSUE: Connection not working #181

K14Mua opened this issue Apr 13, 2024 · 16 comments
Labels
bug Something isn't working

Comments

@K14Mua
Copy link

K14Mua commented Apr 13, 2024

If you disregard this template, your issue may risk being overlooked and closed. Kindly invest some time in furnishing as much information as possible. This enables us to promptly diagnose your issue without necessitating multiple follow-up inquiries. Your cooperation is greatly appreciated.

If any of the following questions are irrelevant, indicate them as "Not Applicable."

Describe the issue
When the Tunnel is turned on, one of two things happens.
a) The Internet disappears completely
b) The Internet is working, but by all indications the VPN has been activated (those sites for which I use the VPN do not open)

To Reproduce
Steps to reproduce the behavior:

  1. Go to TuunlTo app
  2. Click on Enable

Expected behavior
I expect that sites like YouTube will begin to open, and my IP address should also change

Tested on official WireGuard client
This is exactly the problem. When I import the same config into WireGuard, it works there without problems. But TuunlTo the same config does not work

Tested on different VPN servers
I used two different WireGuard configs. In WireGuard they both work without problems

Screenshots and GIF's
image
image
image
image

Tunnel Config
image

Logs
Tunnel Disabled. Wiresock process stopped

2024-04-13 07:30:37 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:65230 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:37 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:63677 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:36 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:50587 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:36 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:49347 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:36 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:36 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:63633 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:35 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:62521 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:35 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:61867 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:35 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:35 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:56121 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:34 [FILTER]: PROTOCOL 58 : fe80::325f:ca1:51f6:2491 -> fe80::c225:e9ff:fed3:49b0

2024-04-13 07:30:34 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:49525 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:34 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:51407 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:33 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:57356 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:33 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:33 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:52322 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:33 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:58799 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:33 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:57148 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:32 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:32 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:62833 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:32 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:31 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:53554 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:31 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:31 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:64411 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:31 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:57411 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:30 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:51835 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:29 [FILTER]: PROTOCOL 58 : fe80::325f:ca1:51f6:2491 -> fe80::c225:e9ff:fed3:49b0

2024-04-13 07:30:29 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:55681 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:29 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:29 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:50222 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:28 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:28 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:52545 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:28 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:28 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:49914 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:27 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:27 [TUN]: Handshake response received from ... : ****

2024-04-13 07:30:27 [TUN]: keep_alive_thread: Sending Handshake packet to WireGuard Server success

2024-04-13 07:30:27 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:27 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:56714 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:27 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:63807 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:27 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:27 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:57209 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:26 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:52214 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:26 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:52458 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:26 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:50601 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:25 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:25 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:25 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:57233 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:25 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:53342 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:25 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:59255 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:25 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : 192.168.1.10:59564 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:24 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:56609 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:24 [FILTER]: PROTOCOL 58 : fdc8:c503:564:0:ec4d:291:a4c3:4ee5 -> fe80::c225:e9ff:fed3:49b0

2024-04-13 07:30:24 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:53633 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:24 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:59454 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:24 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:59188 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:24 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:51143 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:23 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:54499 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:23 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:62937 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:23 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : 192.168.1.10:59875 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:22 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:58305 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:22 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:58616 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:21 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:61499 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:21 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:19 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:50262 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:19 [FILTER]: PROTOCOL 58 : fdc8:c503:564:0:ec4d:291:a4c3:4ee5 -> fdc8:c503:564::1

2024-04-13 07:30:19 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:19 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:18 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:50050 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:18 [FILTER]: Dnscache : DNS : 192.168.1.10:56117 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:17 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:60064 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:17 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:17 [TUN]: keep_alive_thread: Sending Keepalive packet to WireGuard Server success

2024-04-13 07:30:17 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:50738 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:17 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:17 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:17 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:17 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:56117 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:16 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:16 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:16 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:62795 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:15 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:65535 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:15 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:57111 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:14 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : 192.168.1.10:61565 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:14 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:50991 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:14 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:63083 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:13 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:54389 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:13 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:56745 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:13 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:12 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:62037 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:12 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : 192.168.1.10:59789 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:12 [TUN]: Handshake response received from ... : ****

2024-04-13 07:30:12 [TUN]: keep_alive_thread: Sending Handshake packet to WireGuard Server success

2024-04-13 07:30:12 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:61451 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:12 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:58281 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:11 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : 192.168.1.10:61399 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:11 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:50854 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:11 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:56999 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:11 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:51792 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:10 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:56143 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:10 [FILTER]: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\123.0.2420.81\msedgewebview2.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:56352 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:10 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:10 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:53082 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:09 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:61150 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:08 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:08 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:08 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:08 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:58436 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:08 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:59264 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:08 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:51562 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:07 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:07 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:07 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:07 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:57182 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:07 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:49792 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:06 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:06 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:06 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:53220 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:06 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:58223 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:06 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:50459 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:05 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:54867 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:05 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:60516 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:05 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:54290 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:05 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:55614 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:04 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:04 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:04 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:04 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:04 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:04 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:04 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:04 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:04 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:56616 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:03 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:49394 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:03 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:03 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:03 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:03 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:02 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:60349 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:30:02 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:02 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:01 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:57757 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:01 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:01 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:00 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:00 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:00 [FILTER]: Dnscache : DNS : 192.168.1.10:55648 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:30:00 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:00 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:00 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:30:00 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:59 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:59 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:58902 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:59 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:59 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:55648 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:59 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:59 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:57 [TUN]: Handshake response received from ... : ****

2024-04-13 07:29:57 [FILTER]: PROTOCOL 58 : fdc8:c503:564:0:ec4d:291:a4c3:4ee5 -> fdc8:c503:564::1

2024-04-13 07:29:57 [TUN]: keep_alive_thread: Sending Handshake packet to WireGuard Server success

2024-04-13 07:29:56 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:56 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:56 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:54 [FILTER]: Dnscache : DNS : 192.168.1.10:60801 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:53 [FILTER]: Dnscache : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:60801 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:52 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:52 [TUN]: keep_alive_thread: Sending Keepalive packet to WireGuard Server success

2024-04-13 07:29:51 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:51 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:53798 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:51 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:51450 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:50 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:49 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:49 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:49 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:50778 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:49 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:50216 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:49 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:63013 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:49 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:60823 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:48 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:48 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:51379 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:48 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:49368 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:48 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:50048 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:47 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:47 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:47 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:51726 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:47 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:55464 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:46 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:54617 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:46 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:52449 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:45 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:45 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:60627 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:44 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:43 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:42 [TUN]: Handshake response received from ... : ****

2024-04-13 07:29:42 [TUN]: keep_alive_thread: Sending Handshake packet to WireGuard Server success

2024-04-13 07:29:41 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:39 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:39 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:38 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:38 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:37 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:36 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:35 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:35 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:35 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:34 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:34 [FILTER]: PROTOCOL 58 : fdc8:c503:564:0:ec4d:291:a4c3:4ee5 -> fdc8:c503:564::1

2024-04-13 07:29:34 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:34 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:34 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:49774 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:34 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:62904 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:33 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:33 [FILTER]: PROTOCOL 58 : fe80::325f:ca1:51f6:2491 -> fe80::c225:e9ff:fed3:49b0

2024-04-13 07:29:33 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:33 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:33 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:32 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:61561 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:32 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:60655 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:32 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:49974 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:31 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:31 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:31 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:31 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:31 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : 192.168.1.10:53110 -> 1.1.1.1[192.168.1.1]:53

2024-04-13 07:29:31 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:58680 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:30 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:30 [FILTER]: C:\Program Files\Google\Chrome\Application\chrome.exe : DNS : fdc8:c503:564:0:ec4d:291:a4c3:4ee5:53711 -> 1.1.1.1[fdc8:c503:564::1]:53

2024-04-13 07:29:29 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:28 [FILTER]: PROTOCOL 58 : fe80::325f:ca1:51f6:2491 -> fe80::c225:e9ff:fed3:49b0

2024-04-13 07:29:27 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:27 [TUN]: wireguard_read result = 2 size = 13

2024-04-13 07:29:27 [TUN]: Handshake response received from ... : ****

2024-04-13 07:29:27 Wireguard tunnel has been started.

2024-04-13 07:29:27 [MGR]: Tunnel has started

2024-04-13 07:29:27 [TUN]: Sent handshake packet to the WireGuard server at 162.159.193.5:2408

2024-04-13 07:29:27 [TUN]: Using local IPv6 = fe80::325f:ca1:51f6:2491 for the {6E6CE964-F17E-4451-BA08-637F320D6A5E}

2024-04-13 07:29:27 [TUN]: Using local IPv4 = 192.168.1.10 for the {6E6CE964-F17E-4451-BA08-637F320D6A5E}

2024-04-13 07:29:27 [TUN]: Detected default interface {6E6CE964-F17E-4451-BA08-637F320D6A5E}

2024-04-13 07:29:27 [MGR]: Using WireGuard server: ... : ****

2024-04-13 07:29:27 WireSock Service has started.

WireSock WireGuard VPN Client 1.2.37 is running as a regular process.

The service is starting using C:\Users\K14M\AppData\Local\TunnlTo\tunnel.conf WireGuard client configuration.

2024-04-13 07:29:27 WireSock WireGuard VPN Client Service 1.2.37

Starting WireSock directly
If possible, follow the instructions below and comment on the outcome:

  1. Open TunnlTo and Enable the tunnel (this will save the config file to disk)
  2. Disable the tunnel and close TunnlTo
  3. Open a command prompt and issue the following commands:
cd "C:\Program Files\WireSock VPN Client\bin"

// Ensure you alter the <YOUR USERNAME> component of the path
wiresock-client.exe run -config C:\Users\<YOUR USERNAME>\AppData\Local\TunnlTo\tunnel.conf -log-level all

image
@K14Mua K14Mua added the bug Something isn't working label Apr 13, 2024
@K14Mua
Copy link
Author

K14Mua commented Apr 24, 2024

Is anyone home?

@wiresock
Copy link
Collaborator

It seems the issue may be linked to the handling of DNS traffic, as there are no DNS responses visible in the logs. Could you please share your Wireguard configuration and the pcap files produced by wiresock-client.exe when you run it with the '-debug-level all' option? Please ensure to remove any real keys from the Wireguard configuration before sharing.

@K14Mua
Copy link
Author

K14Mua commented Apr 25, 2024

Could you please share your Wireguard configuration

I already showed this above

the pcap files produced by wiresock-client.exe

wiresock_enc.zip

@brendanosborne brendanosborne changed the title ISSUE: ISSUE: Connection not working Apr 29, 2024
@cr0wdelex
Copy link

I have the same issue.
There is no Internet for all the app go through TunnlTo.
Switch back to Wireguard client, the Internet works.

@K14Mua
Copy link
Author

K14Mua commented May 12, 2024

Any news?

@usanry
Copy link

usanry commented May 14, 2024 •
edited

Any news?

Similar problem, do you have hyper-v and its virtual network switch installed? TunnlTo started working after changing virtual switch to Internal network, but this is not a solution.
Looks like TunnlTo is choosing the wrong interface. And somehow TunnlTo breaks connections in vmware bridged virtual machines.

@K14Mua
Copy link
Author

K14Mua commented May 14, 2024

do you have hyper-v and its virtual network switch installed?

Which of these do you mean by virtual network?

image

My system is a little over a month old from installation. Before reinstalling Windows, I had Hamachi installed, Radmin VPN, and also the Windows sandbox and VirutalBox installed. At least one of these programs used a virtual network adapter. And this did not interfere with the work of TunnlTo. Now what?

I generated a config file. I imported it into TunnlTo, turned it on and the Internet disappeared. Then I import the same config into WireGuard and it works without problems. WireGuard also works without problems on a smartphone. Even my router runs WireGuard. But TunnlTo refuses to work...

@usanry
Copy link

usanry commented May 14, 2024

Which of these do you mean by virtual network?

Hyper-V Virtual Ethernet
изображение

looks like this is not your problem

@K14Mua
Copy link
Author

K14Mua commented May 14, 2024

Hyper-V Virtual Ethernet

I installed it two months ago, and then it did not interfere with the work of TunnlTo

@brendanosborne
Copy link
Contributor

I'm just looking at this screenshot again.

  • It appears you have not set an IPv4 address in TunnlTo, whereas your WireGuard config has one set to 172.16.0.2/32.
  • The WireGuard config has 0.0.0.0/0 in the AllowedIP's but that is not set in TunnlTo.

Could you test the WireGuard connection without IPv4 set, or add those values to TunnlTo so that it is a like for like test?

If it is still not working, once you click "Enable" in TunnlTo, post up the contents of the file in C:\Users\[YOUR USERNAME]\AppData\Local\TunnlTo\tunnel.conf with the keys etc. removed.

@K14Mua
Copy link
Author

K14Mua commented May 28, 2024

I DID NOT SET? Have you CAREFULLY read what I wrote to you? I DID NOT INSTALL ANYTHING AT ALL! I IMPORTED the config through the BUILT-IN IMPORT FUNCTION!

image

And if something is not correct there, then YOUR APPLICATION is not importing the WORKING CONFIG correctly. What questions might you have for me?

@K14Mua
Copy link
Author

K14Mua commented May 28, 2024 •
edited

The config is working, because when I IMPORT it into WireGuard it works IMMEDIATELY without any intervention on my part!

@K14Mua
Copy link
Author

K14Mua commented May 28, 2024

Here I have a config

image

Here I import it into WireGuard

image

Here I turn it on and it works!

image

And here I import the SAME CONFIG into your application

image

Do you see?

image

This field is EMPTY!

image

Why is it empty if IP 4 is written in the original config file?

@brendanosborne
Copy link
Contributor

I can see you're frustrated but please understand we're volunteering our free time to help you diagnose an issue with a free app. We assume our users have a basic understanding of WireGuard as advised in the Prerequisites section of our home page. Considering that, it initially seemed you were deliberately trying to use only IPv6, since it’s unusual for someone to recognize missing parameters and still expect a connection to succeed.

The import feature is not importing critical parameters from your particular config files. TunnlTo assumes config files follow standard convention and will have parameters with multiple values (in your case Address and AllowedIPs) to be split with a comma. For example:

Address = [value 1], [value 2]

You can see the specific code for that here.

It appears you're using Warp+ from CloudFlare and they've decided to split multiple values by duplicating parameters. For example:

Address = [value 1]
Address = [value 1]

This is something I can look into improving in a future release. In the meantime I recommend simply adding the missing IPv4 Address (172.16.0.2) to the local interface section and 0.0.0.0/0 to Rules > Allowed > IP Addresses text box.

@K14Mua
Copy link
Author

K14Mua commented May 29, 2024

It appears you're using Warp+ from CloudFlare and they've decided to split multiple values by duplicating parameters.

At the same time, WireGuard normally understands such an address record, but your TunnlTo does not. I have never manually entered any parameters from a config file into the application. I imported the config into WireGuard on a PC, I imported the config into WireGuard for a smartphone, and even imported the config into WireGuard on the router. And I didn’t see any problems anywhere. How was I supposed to know that TunnlTo couldn't do that?

@brendanosborne
Copy link
Contributor

At the same time, WireGuard normally understands such an address record, but your TunnlTo does not.

Yes, we've already established that. I've explained why this is happening in my previous post. I've outlined:

  • Why there was a misunderstanding about what your issue is.
  • Technical details as to why the application is not behaving in the way you expect.
  • What will be done about it.
  • How to resolve the issue in the meantime.

How was I supposed to know that TunnlTo couldn't do that?

There is no expectation that you would know about an issue before it's discovered. On the other hand, there are no guarantees with the import feature in TunnlTo (or import features in any app for that matter) so I would advise to carefully review the imported data. For example, in your original screenshot you can see that the values highlighted in the yellow box do not exist in TunnlTo. This would typically be an indicator that the import feature has not correctly imported all of the data.
image

@TunnlTo TunnlTo locked as resolved and limited conversation to collaborators May 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@cr0wdelex @brendanosborne @wiresock @K14Mua @usanry