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.
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
Windows: v1.3.1 stopped working with VPN on #1417
Comments
Can you upgrade to 1.4.1 to see if that helps any by any random chance? |
Which VPN are you using? If it's one where it uses a custom network adapter instead of intercepting the default one, it might explain why it's choosing Ethernet/WiFi over the VPN network adapter. Seems like we're missing debug logs in the resolver, that's definitely something that needs to be added, because it'll tell us what's happening. I'm currently unable to do this myself, so if someone wants to do this: log the available adapter names, possible candidates and the adapter which is selected. If not, I'll look into PR'ing that myself soon so we can start figuring out the issue. |
that's the one I've started with to check the new great package signatures feature, it's also broken |
I think we will have to add more logging to discover the problem. |
I'm using OpenVPN, don't know whether that uses a custom network adapter (is it this TUN thing?) (the vpn provider is PIA, tested their native app as well, same result, also not sure whether/what kind of adapters they are using) |
@eugenesvk You can check which network adapters exist in the Control Panel. You can find it manually, or press Win + R and run this command to open the |
Well... it looks like I misread the issue initially, sorry about that. I mistakenly thought the VPN was blocking the primary Ethernet/LAN adapter (aka killswitch in most VPNs), but looking better at the verbose logs, it says Anyway, I've implemented verbose logging in my cargo install cargo-binstall --locked --force --git https://github.com/Sculas/cargo-binstall.git --branch dns-adapter-fix Then, run this command (using cargo binstall cargo-nextest -y --log-level trace --json-output > out.txt Open the Lastly, run Unfortunately, I don't have a VPN client at hand that uses OpenVPN, so I have to ask a lot of questions, but I'm sure we'll figure it out :) |
Thanks, will build&check your branch later
Maybe try with a native client as that one also bugs for me, I've just tested with OpenVPN as a double-check |
I only have AdGuard VPN which intercepts the primary Ethernet adapter instead of having its own network adapter, hence I'm unable to reproduce this myself. |
Hm, your version works fine (checked again the downloaded 1.4.2, and that one still fails). Can the fact that it's buit locally vs. downloaded from the CI explain it (the locally built version is also much smaller, 8.5m vs 13.5m)? Not sure whether the logs are relevant without an error, but FYI https://gist.github.com/eugenesvk/4a315b6ab8855bac2749a14deef07f9e The IP address matches the one from |
dns-adapter-fix contains latest update on main: We upgrade to @eugenesvk Can you try installing the latest version from main via |
the main repo still fails, so I guess the refactoring done to add logging also fixed the issue? |
That could very well be correct. Since I wanted to log all candidates (and not just the one that was found first), I rewrote the @NobodyXu I didn't spend too much effort in that branch since I just wanted to know if it works or not. Is it okay if I PR the branch and resolve any of the requested changes you may have? |
Yes @Sculas |
I would probably release a new version this weekend |
After updating cargo binstall to v1.3.1, I am unable to use it on Windows 10 behind a VPN due to some DNS issues
(maybe related to this fix in v1.3.1 "Fixed slow dns resolution inside VMware/VirtualBox(#1339 #1364 #1365)"?)
The full error message for "cargo binstall cargo-semver-checks -v"
The text was updated successfully, but these errors were encountered: