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.

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

Linux: not working with wired? connection #1437

Open
passcod opened this issue Oct 6, 2023 · 1 comment
Open

Linux: not working with wired? connection #1437

passcod opened this issue Oct 6, 2023 · 1 comment
Labels
Report: bug Something isn't working

Comments

@passcod
Copy link
Member

passcod commented Oct 6, 2023

Migrated from #1417

I still have the problem after compiling from the right repo (commit af04e45 according to cargo install), logs below.

Observation: I noticed that it only have when my computer is on a wired connection (Ethernet over USB). On wireless, it works. I have a suspicion: my computer disables the WiFi conncetion when I plug it into ethernet (otherwise I get other problems). Perhaps binstall is trying to use the WiFi connection for some reason, even when it's disabled?

Let's see if these logs are any better. The final error is ~ the same as in my last comment. Again, I used cargo binstall cargo-nextest -y --log-level trace --json-output | tee out.txt.

cargo-binstall-logs.txt

Originally posted by @ilyagr in #1417 (comment)

@passcod
Copy link
Member Author

passcod commented Oct 6, 2023

Ah, I only just now noticed you're on Linux 😅. That explains why I couldn't find the log again (I was searching for the Windows log line). Given that this was initially only a problem on Windows, we only implemented the fix for that and kept using the auto system config on Linux. It really does look like trust-dns's system config is unreliable.

[excluded off-topic discussion of "why trust-dns"] Seems like we'll just have to port over the changes from the Windows-side to the Linux-side (find a replacement for the ipconfig crate, default_net can be removed since we're only using 1 small function which we can extract).

Hmm... trust-dns's system config reads the nameservers from /etc/resolv.conf, which could mean something might be wrong there? There might be more to this, but I'll have to look at the logs properly when I'm back.

Originally posted by @Sculas in #1417 (comment)

@passcod passcod added the Report: bug Something isn't working label Oct 6, 2023
@passcod passcod changed the title Linux: not working with wifi connection Linux: not working with VPN connection Oct 6, 2023
@passcod passcod changed the title Linux: not working with VPN connection Linux: not working with wired? connection Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Report: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant