-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
Failed to listen on network interface: Address family not supported by protocol (os error 97) on Ubuntu (WSL) #40
Comments
Does this also happen when running as root? |
Looks like #31 |
@imsnif Yes. And I ran the shell as an administrator in all cases. |
@sbmthakur - it might be #31 as @grishy mentions. This means that one of the network cards in the subsystem is virtual (or "problematic" in a different way) and what is trying to pick it up and fail (@grishy is working on a fix for this so such a situation won't fail the entire run and would just ignore that card). If you use the -i flag with one of the interfaces, does it work for you? Another sadder option might be that we're having issues with linux-in-windows (that's what you're running, right?) so I'd be very interested to know if the -i option solved your problem. |
Interesting. I'm going to take a look at this and would generally be interested in investigating further. What seems to be happening is that we're failing to read the frames coming from any of your network interfaces. For this we're using the Would it be okay for you to help debug this by running some code I'll whip up to pin-point the issue? |
@imsnif Sure. I am always happy to help. |
Hi all. I'm currently cleaning up old issues. Can you please check if this issue still persists on the latest release? Thank you. |
@cyqsimon works fine for me now on 0.21.0 👍 |
In which case I will close this issue as completed. Please reopen if it's still problematic, thanks. |
Platform details:
OS: Ubuntu 18.04.1 LTS (Windows Subsystem Linux)
Rust version: 1.40.0
Steps to reproduce:
cargo build
.cargo run
.The text was updated successfully, but these errors were encountered: