MatsuriDayo / nekoray

Qt based cross-platform GUI proxy configuration manager (backend: sing-box)
https://matsuridayo.github.io/
GNU General Public License v3.0
13.44k stars 1.26k forks source link

Can't connect to any protocol and shutdown internet when using TUN #1460

Open Heslimited opened 1 month ago

Heslimited commented 1 month ago

Hello, in Nekoray the Internet completely disappears when connecting in TUN mode and I get only errors of this kind: ERROR[0010] dns: exchange failed for www.msftconnecttest.com. IN A: Post "https://8.8.8.8/dns-query": context canceled ERROR[0010] dns: exchange failed for edge.microsoft.com. IN A: Post "https://8.8.8.8/dns-query": context canceled

The system proxy mode does not seem to give errors, the server works properly, I changed the DNS in Nekoray several times, I ran the program as administrator. Tell me what the problem could be?

sueta2 commented 1 month ago

same

erius0 commented 1 month ago

What OS are you using? Have you tried any of the solutions provided in the issue #118? I fixed this on my Fedora ARM64 device by disabling and stopping the systemd-resolved service and installing some other stub resolver.

Heslimited commented 1 month ago

What OS are you using? Have you tried any of the solutions provided in the issue #118? I fixed this on my Fedora ARM64 device by disabling and stopping the systemd-resolved service and installing some other stub resolver.

On PC I am using Windows, on server Ubuntu. Also, I haven’t tried solutions in #118. Can u please tell me more about your solution ?

erius0 commented 1 month ago

If you are on Windows, then most likely something's up with the DNS settings in nekoray. Could you go to Routing Settings -> DNS and send a screenshot of those settings?

Heslimited commented 1 month ago

If you are on Windows, then most likely something's up with the DNS settings in nekoray. Could you go to Routing Settings -> DNS and send a screenshot of those settings?

I tried changing the remote dns, I didn't touch the other settings.

Heslimited commented 1 month ago

https://imgur.com/a/LwZNvZR

erius0 commented 1 month ago

Try changing Direct DNS to something other than localhost (preferably to something that uses https)

Heslimited commented 1 month ago

Try changing Direct DNS to something other than localhost (preferably to something that uses https)

Still got this image

Halahad08 commented 1 month ago

same issue

Heslimited commented 1 month ago

Any other ideas?

walker2two commented 1 month ago

I've had the same issue and tried to fix it for quite a while yesterday.

What helped me is to delete every peice of other software that creates network adapters in windows. Including virtualbox and plethora of VPN clients I've had. And then perform network reset.

Also I think another major step that helped, is that I've changed network interface metric for my ethernet interface to a higher number of 100, because it seems that DNS requests were being sent to that interface instead of VPN tunnel.

After that all xray clients that use sing-tun started working

erius0 commented 1 month ago

I've had the same issue and tried to fix it for quite a while yesterday.

What helped me is to delete every peice of other software that creates network adapters in windows. Including virtualbox and plethora of VPN clients I've had. And then perform network reset.

Also I think another major step that helped, is that I've changed network interface metric for my ethernet interface to a higher number of 100, because it seems that DNS requests were being sent to that interface instead of VPN tunnel.

After that all xray clients that use sing-tun started working

Sometimes when removing Wireguard from your PC its wintun driver could still be present on the system and cause problems for sing-tun. Try the solution from this issue #1390

Heslimited commented 3 weeks ago

I've had the same issue and tried to fix it for quite a while yesterday. What helped me is to delete every peice of other software that creates network adapters in windows. Including virtualbox and plethora of VPN clients I've had. And then perform network reset. Also I think another major step that helped, is that I've changed network interface metric for my ethernet interface to a higher number of 100, because it seems that DNS requests were being sent to that interface instead of VPN tunnel. After that all xray clients that use sing-tun started working

Sometimes when removing Wireguard from your PC its wintun driver could still be present on the system and cause problems for sing-tun. Try the solution from this issue #1390

This solution didn't help. I still get some errors. I tried to turn off the system proxy, it doesn't help either. I changed the direct DNS and local, nothing helps.

VLESS: INFO[0014] [4077499838 0ms] inbound/mixed[mixed-in]: inbound connection to kv601.prod.do.dsp.mp.microsoft.com:443 INFO[0014] [4077499838 0ms] outbound/vless[proxy]: outbound connection to kv601.prod.do.dsp.mp.microsoft.com:443 INFO[0014] [769920682 0ms] inbound/tun[tun-in]: inbound connection from 172.19.0.1:57697 INFO[0014] [769920682 0ms] inbound/tun[tun-in]: inbound connection to 204.79.197.239:443 INFO[0014] [769920682 0ms] outbound/vless[proxy]: outbound connection to 204.79.197.239:443 INFO[0015] outbound/vless[proxy]: outbound packet connection to 1.1.1.1:53

ERROR[0015] dns: exchange failed for client-update.fastly.steamstatic.com. IN A: dial tcp 83.217.211.150:1080: i/o timeout

INFO[0017] [2910922398 0ms] inbound/mixed[mixed-in]: inbound connection from 127.0.0.1:57700

Shadowsocks:

INFO[0069] [3274792588 0ms] outbound/shadowsocks[proxy]: outbound connection to 172.217.16.131:443 ERROR[0069] dns: exchange failed for www.msftconnecttest.com. IN A: context deadline exceeded ERROR[0069] dns: exchange failed for www.msftconnecttest.com. IN A: context canceled INFO[0069] outbound/shadowsocks[proxy]: outbound packet connection to 1.1.1.1:53 ERROR[0069] dns: exchange failed for ipv6.msftconnecttest.com. IN A: context canceled INFO[0070] [1924440620 0ms] inbound/tun[tun-in]: inbound connection from 172.19.0.1:58106 INFO[0070] [1924440620 0ms] inbound/tun[tun-in]: inbound connection to 216.239.32.116:443

Nikitatut commented 1 week ago

same issue