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

ifconfig Warning: cannot open /proc/net/dev (No such file or directory). Limited output. #602

Closed
Mr-Hamdan opened this issue Jun 30, 2016 · 23 comments
Labels

Comments

@Mr-Hamdan
Copy link

@Mr-Hamdan Mr-Hamdan commented Jun 30, 2016

image

@benhillis benhillis added the duplicate label Jun 30, 2016
@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 30, 2016

Thank you for reporting, this is the same underlying issue as #66 and #239.

@benhillis benhillis closed this Jun 30, 2016
@Mr-Hamdan

This comment has been minimized.

Copy link
Author

@Mr-Hamdan Mr-Hamdan commented Jun 30, 2016

@odoland

This comment has been minimized.

Copy link

@odoland odoland commented Aug 4, 2016

Same problem when using ifconfig

@bitcrazed

This comment has been minimized.

Copy link
Contributor

@bitcrazed bitcrazed commented Aug 11, 2016

Reopening since ifconfig is not fixed by the changes that enabled ping etc.

@bitcrazed bitcrazed reopened this Aug 11, 2016
@DaveKZN

This comment has been minimized.

Copy link

@DaveKZN DaveKZN commented Aug 14, 2016

I have just now (Aug 14) installed Windows 10 Anniversary Edition and enabled the Ubuntu Bash shell. I am able to run basic bash commands and it is able to update and install from the internet. But ifconfig returns Warning: cannot open /proc/net/dev (No such file or directory). Limited output.

@vaibhavbhalla

This comment has been minimized.

Copy link

@vaibhavbhalla vaibhavbhalla commented Aug 16, 2016

For me sbin path was not included:
Command 'ifconfig' is available in '/sbin/ifconfig'
The command could not be located because '/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative privileges associated with your user account.
ifconfig: command not found

after using:
$ export PATH=$PATH:/sbin
getting:
Warning: cannot open /proc/net/dev (No such file or directory). Limited output.

@ewan-fanduel

This comment has been minimized.

Copy link

@ewan-fanduel ewan-fanduel commented Aug 16, 2016

Also having the above issue @vaibhavbhalla is experiencing

ifconfig
Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
@kimiazhu

This comment has been minimized.

Copy link

@kimiazhu kimiazhu commented Aug 20, 2016

I have the same issue. and also the ping can not work properly.

$ ping google.com
ping: icmp open socket: Permission denied
@sandros87

This comment has been minimized.

Copy link

@sandros87 sandros87 commented Aug 21, 2016

To solve the ping issue you need to start bash as administrator.

@rtosman

This comment has been minimized.

Copy link

@rtosman rtosman commented Aug 23, 2016

ifconfig does not work, ping does.

@odoland

This comment has been minimized.

Copy link

@odoland odoland commented Aug 24, 2016

It seems that WSL does not currently support this feature. Here is the user voice page to vote for prioritizing this issue:

https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/15202875-would-you-like-to-support-ifconfig-iw-iwconfig-t

@sunilmut

This comment has been minimized.

Copy link
Member

@sunilmut sunilmut commented Sep 14, 2016

Just FYI that starting build 14926, admin is no longer a requirement for ping/ping6 (thanks to the Windows networking team).

@mawadhwa

This comment has been minimized.

Copy link

@mawadhwa mawadhwa commented Sep 26, 2016

Same problem while running ifconfig. Any update when can Microsoft fix this ?

@sunilmut

This comment has been minimized.

Copy link
Member

@sunilmut sunilmut commented Sep 26, 2016

Yes, we understand that ifconfig and similar tools such as ip currently don't work. We are looking into it, but no ETA at the moment. You can also voice your opinion at our User Voice Page post for this and help us prioritize it. Thanks for your feedback!

@sunilmut

This comment has been minimized.

Copy link
Member

@sunilmut sunilmut commented Nov 10, 2016

Just an update that 'ifconfig' and the 'ip' commands for network enumeration should be working in the latest fast insider build 14965, also see release notes

@sunilmut sunilmut added the fixed label Nov 10, 2016
@squeezyPig

This comment has been minimized.

Copy link

@squeezyPig squeezyPig commented Nov 17, 2016

I fixed it. You need to reinstall bash and choose "root" as username. It's not very safe, but then 'ifconfig' is working. Just be patient ^^

@sunilmut

This comment has been minimized.

Copy link
Member

@sunilmut sunilmut commented Nov 18, 2016

Closing this out since this has been marked fixed for sometime. If the issue persists, please reopen.

@sunilmut sunilmut closed this Nov 18, 2016
@AggelosM

This comment has been minimized.

Copy link

@AggelosM AggelosM commented Nov 23, 2016

I fixed it. You need to reinstall bash and choose "root" as username. It's not very safe, but then 'ifconfig' is working. Just be patient ^^

I chose "root" as username but I'm still getting the same warning.

@aseering

This comment has been minimized.

Copy link
Contributor

@aseering aseering commented Nov 23, 2016

@amaklp @Timmy1337 -- choosing "root" as the username didn't help me. ifconfig works on my machine as an ordinary (non-root) WSL user. However, I did have to update to a recent Windows Insider build (I'm currently running build 14971).

@MrAliFu

This comment has been minimized.

Copy link

@MrAliFu MrAliFu commented Feb 21, 2017

same problem here as well

@bitcrazed

This comment has been minimized.

Copy link
Contributor

@bitcrazed bitcrazed commented Feb 23, 2017

@akapucu You'll need to be running a build > 14965 for ifconfig or 14986 for ping to work. Essentially, install a current Insider build and you should be able to do both.

@Joshua-Cody

This comment has been minimized.

Copy link

@Joshua-Cody Joshua-Cody commented Mar 6, 2017

same problem here as well.

@aseering

This comment has been minimized.

Copy link
Contributor

@aseering aseering commented Mar 6, 2017

@Joshua-Cody -- what Windows build are you running? (Type ver at a Windows command prompt.)

The fix to this issue is currently only available to people who have subscribed to Windows Insider builds. It's coming to stable Windows with the "Creators" update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.