Forum Replies Created
-
Posts
-
I’ve tested it again but with persistentKeepalive=20 and it has been more than 3 hours, tunnel and websites work fine, so I guess it dropped connection and couldn’t get it up again last time.
I’ve done more testing with MSEdge, it works fine then I left my computer for about 15 min and when I came back no more websites load (dns address couldn’t be found).
I don’t know if connection dropped by ISP router again, I could test it again with persistentKeepalive=20 for example rather than 25.
PCAP files: https://easyupload.io/dp2r8q
Sorry, I can’t post for hours as it says my ip belongs to spam network!!
Another PCAP files: https://upload1.easyupload.io/a4vsj6It works really good, thank you so much for your work.
I tried tunneling MSEdge and worked just fine then waited for couple of min and it still works, even when tunneled app is not running it seems to do just fine and continue working after starting the app.
PCAP files: https://upload1.easyupload.io/o3lf49I’m afraid that the client only attempts to send only the first handshake and no more handshakes after that, the issue is still present unfortunately.
PCAP/log files: https://upload1.easyupload.io/2sz5co
I’ve tested it but unfortunately only first handshake sent and response received, the config has only one app to route in allowedapps and it is not running during test, so the expected behavior is that a keep-alive packet sent every 25 secs but there is nothing sent other than first handshake.
I’ve also tested it with firefox it works fine until I stop using firefox for about 30 sec then the connection dropped by ISP router (I think) and no keepalive packets are sent during this idle time.
Here are PCAP files: https://easyupload.io/rb00q9I’ve noticed inconsistency in sending keep-alive packets, sometimes sent every 20 sec or every 60 sec or even up to 120 sec (2min) which led to close of connection by ISP router and connection drops and client is trying to send keep-alive packets every 5 sec and no more handshake responses.
This is a log for a session when only one app uses the tunnel it works fine until I close it and tunnel idle for a few minutes which causes what described above.
https://upload1.easyupload.io/09ovbpThank you so much for your work. Now it is working really good. I’ve noticed that keep-alive packets are sent over socks (correct me if I’m wrong) so was that the problem, ISP router blocks keep-alive packets too?
Edit: keep-alive packets sent every 20 sec (and sometimes ~60 sec) not 25 sec like set in config.
I tried the build in #11988 and it works well, as for the build in #11993 still having same issue unfortunately, It only starts working only after wifi reset.
I’ve uploaded PCAP file and a copy of log for this session: https://upload1.easyupload.io/unw33c
You can see in log starting from line 411 it is working and no more dns issues and websites load normally.
I can try another router (old one) if you want so that I can eliminate router problems but my ip will change probably.People working at ISP in my country are doing a really good job at messing up everything.
I also wonder why resetting wifi connection seems to fix this issue, We can give it a try and pass all traffic through proxy too but I think it will hit the performance and speed will be reduced (which won’t be a problem with my 12Mbps adsl connection).
Here are PCAP files with adguard not running: https://easyupload.io/23402w
Actually I’ve done this but the problem still present, According to the log the dns requests are forwarded but there is no dns respons until I disable/enable wifi.
Wiresock works fine with other services other than warp+ and there is no ip leaks so far, but there is still a minor issue that after connecting the tunnel works (according to logs) but no website load (DNS address could not be found) until I disable/enable the wifi.
I’ve done some more testing and with wstunnel only >> no ip leaks, using another wireguard service other than warp+ (using official wireguard client) >> no ip leaks, both tests done with adguard running as usual (I suspected it is some sort of dns leak).
So I guess it has something to do with warp+ wireguard service, Sorry for the inconvenience.Thank you for your time, I really appreciate it.
I could do more testing on other machines as for mine it has been more than 3 years since I’ve installed this windows and doing a fresh install isn’t an option, I’m sorry.These are my pcap file: https://ufile.io/hkkf4vvp
It’s not the best host, my apologies. I hope you find them helpful.
