Forum Replies Created
-
Posts
-
I’ve been using Firefox 95.0.1 and even MS Edge, I’ve mentioned before that I’m using adguard with dns protection (adguard dns over DNSCrypt) and kaspersky total security (which is disabled for long time).
To make sure adguard doesn’t act weird I’ve disabled it too.
Now sometimes it is not working (logs show it is working but no website load) until I disable and re-enable my wifi connection, I don’t know why !! and it still leaks ip.I’m sorry for that.
I’ve checked the following:
http://www.whatismyip.com = real ip
whatismyipaddress.com = real ip
http://www.mon-ip.com = real ip
ipaddress.my = real ip
http://www.myip.com = real ip
ipcost.com = real ip
http://www.speedtest.net = vpn ip
http://www.mio-ip.eu = vpn ip
http://www.iplocation.net = vpn ipMy config:
[Interface]
PrivateKey = ————————
Address = 172.16.0.2/32
DNS = 1.1.1.1
MTU = 1280
[Peer]
PublicKey = ————————-
AllowedIPs = 0.0.0.0/0
DisallowedIPs = 10.10.137.0/28
Endpoint = 162.159.192.1:2408
PersistentKeepalive = 25
Socks5Proxy = 132.226.194.27:1080It works and I’m receiving handshake responses and according to log the traffic goes through tunnel but when checking my ip address it doesn’t change as I’ve tested multiple sites and only 2 sites reported vpn ip not mine. Is there anything that leaks my ip using this configration?
Thank you for your work, I’ve tested the version above and it connects to the socks proxy: associate_to_socks5_proxy: SOCKS5 ASSOCIATE SUCCESS port: 9070
but I don’t see the handshake response in log and my IP didn’t change and keep getting this in log: “[TUN]: wireguard_write result = 0 size = 0” and another FILTER logs.
I don’t know if I’m missing something or if I’m doing it wrong.I’ve tested it with wstunnel (like what I’ve been doing with the official client) and it works and keeps working after changing default interface (which wasn’t possible in the previous version).
Currently the client do not log when it receives a handshake response, it would be helpful so that we know if the handshake has been completed.
Is the client have problems running with Adguard as both of them use WFP?
Great news and thank you so much for your work and time.
I will be more than happy to test it whenever it is ready.Also there is shadowsocks since it has obfuscation plugin, but if I remember correctly it doesn’t work with UDP so that don’t know if it would be possible or not but good to mention.
OK, I will wait for it and test it whenever it is ready.
Thanks in advance.
PS: I would be nice if there is an option to make it only fallback to proxy server after X failed handshakes and log when handshake response received.It is a really good idea, but that does it mean we have to have control over the handshake obfuscator (ex: test.sshvpn.me:52220) or it can be as simple as socks5 server without obfuscation? As far as I understand that means we have to deploy the new service (obfuscator) on some sort of server.
I’m ready to help you and test this approach.
It would be great if we can pass the interface to be filtered and wiresock keep working on top of the secondary vpn for moments without dropping the connection and starting all over again, since wireguard (protocol) design do this as far as I can understand, it is not affected by connection changes (ex: switching between WiFi and mobile data on mobile phone) and wiresock should do this also and continue working.
So that the following scenario should work:
1- (First handshake/response go through secondary vpn)
wiresock <-> wstunnel <-> warp server
2- (Continue normal operation without disconnecting and reconnecting)
wiresock <-> warp serverUnfortunately, I don’t have server side control.
Secondary vpn (windsribe’s wstunnel) adds a default route so it can route all traffic (including warp+ traffic, so that’s why I don’t keep wstunnel connected) through wstunnel and deletes it after disconnecting. I am not sure if I can route handshake/response packets only using the current setup (Wireguard 0.5.2 + windscribe)
Thank you for your time.
I’m sorry if I didn’t explain it better (my English is not that good), but I am using warp+ *config* on the official wireguard client for windows (v0.5.2) not Warp app by cloudflare.
As for wstunnel it comes as part of vpn client (windscribe vpn) so I can’t determine exactly which version it is (it could be erebe’s implementation).
Sorry again for the confusion.Is there any chance to have a parameter that can be passed to wiresock so that it filter specific interface (ex: WiFi) and not change automatically to the tap/tun interface created by other vpn client (ex: windscribe) ?
I’m using Warp+ (cloudflare’s wireguard) and using wstunnel(websocket) for first handshake and receiving the response then disconnect it.
For some reason the DPI drops the first handshake response only (and even tried same config on my mobile and same thing happened) but after that since connection has been established the handshakes sent and received without problems.Maybe the first handshake goes outside the tunnel but once tunnel established the handshake response goes through the tunnel or first handshake has different response(signature)!! Just guessing and I could be wrong.
