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

ResolveError on Ubuntu 20.10 #210

Closed
mattwelke opened this issue Feb 8, 2021 · 9 comments
Closed

ResolveError on Ubuntu 20.10 #210

mattwelke opened this issue Feb 8, 2021 · 9 comments

Comments

@mattwelke
Copy link

Same issue as in #197.

My OS:

~ > lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.10
Release:	20.10
Codename:	groovy
~ > uname -r
5.8.0-41-generic

Steps to install:

  1. Installed Rust with curl https://sh.rustup.rs -sSf | sh.
  2. Installed bandwhich with cargo install bandwhich.
  3. Gave it permissions with sudo setcap cap_sys_ptrace,cap_dac_read_search,cap_net_raw,cap_net_admin+ep $(which bandwhich).

When I run it, I get an error:

~ > bandwhich
Error: Could not initialize the DNS resolver. Are you offline?

Reason: ResolveError { inner: Custom { kind: Other, error: "Error parsing resolv.conf: InvalidOption(17)" }

io error }
@FedX-sudo
Copy link

I have the same issue on Pop!_os 20.10. I was able to fix it by cloning the repo then running
cargo install --path /path/to/repo/

@niqdev
Copy link

niqdev commented Mar 14, 2021

Same issue on Ubuntu 20.04

uname -a
Linux dell 5.8.0-44-generic #50~20.04.1-Ubuntu SMP Wed Feb 10 21:07:30 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Cloning the repo worked for me too, thanks!

cargo install --path /path/to/repo/
sudo setcap cap_sys_ptrace,cap_dac_read_search,cap_net_raw,cap_net_admin+ep $(which bandwhich)

@gerrywastaken
Copy link

Hey everybody bandwhich -d 1.1.1.1 is a workaround so that it doesn't try to read your dns config and get confused. 🤷

@hut8
Copy link

hut8 commented Apr 28, 2022

@imsnif this is the fix, right? adb0dae

So, can you just make a new release, and this problem will go away?

@imsnif
Copy link
Owner

imsnif commented Apr 29, 2022

@hut8 - due to Travis CI closing shop, this project has incurred a bit of technical debt. That means that in order to make any changes to it, I'll have to spend a few hours fixing up the pipeline.

Please allow me to remind you that this is an open source work for which you pay nothing.

If this is important to you and the workaround suggested here is not good enough for you (nor is installing directly from source) - you're more than welcome to sponsor me on Github Sponsors for an amount equivalent to the hours of work I'll have to put in to get this fixed. Otherwise, I will get to this at some point in the future on my own time.

@hut8
Copy link

hut8 commented May 1, 2022

@imsnif Thanks for clarifying about the Travis issue. I was under the impression you could just hit a button to publish a new release. I really appreciate all the effort you put into this; it's a phenomenal project. I didn't mean to demand free work from you so I apologize if it came across that way. The suggested workaround is fine, and I did get it working by cloning and installing it that way. I would also sponsor you, but unfortunately I am poor and unemployed 😄 Instead, I will try to figure out exactly what you were using Travis for and will port that to GitHub Actions and open a PR.

@imsnif
Copy link
Owner

imsnif commented May 1, 2022

@imsnif Thanks for clarifying about the Travis issue. I was under the impression you could just hit a button to publish a new release. I really appreciate all the effort you put into this; it's a phenomenal project. I didn't mean to demand free work from you so I apologize if it came across that way. The suggested workaround is fine, and I did get it working by cloning and installing it that way. I would also sponsor you, but unfortunately I am poor and unemployed smile Instead, I will try to figure out exactly what you were using Travis for and will port that to GitHub Actions and open a PR.

Please don't do that, I will not have time to devote to reviewing said PR.

@TheLostLambda
Copy link
Collaborator

@imsnif Thanks for clarifying about the Travis issue. I was under the impression you could just hit a button to publish a new release. I really appreciate all the effort you put into this; it's a phenomenal project. I didn't mean to demand free work from you so I apologize if it came across that way. The suggested workaround is fine, and I did get it working by cloning and installing it that way. I would also sponsor you, but unfortunately I am poor and unemployed smile Instead, I will try to figure out exactly what you were using Travis for and will port that to GitHub Actions and open a PR.

I'm also quite tight on time, but if you can get the actions working in a fork (perhaps you could use the Zellij CI as an example, though those are more complex than this will probably be), then I'm happy to review. Can't promise it will be super fast, but I think it's pretty important that we get releases working again to keep this project healthy :)

Be sure to tag me in the PR is you do open one! Best of luck :)

@cyqsimon
Copy link
Collaborator

Moving discussion to #235. See also #275.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants