-
Notifications
You must be signed in to change notification settings - Fork 833
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
ss (a substitute for netstat) does not work in WSL1 #2249
Comments
@tats-u - WSL looks like not to support netstat; It was included in not working list but is not included in recent working list of @sunilmut's, so ss could not be supported yet, I think. Quote from #69 (comment) on Nov 19 2016;
Quote from #69 (comment) 10 days ago;
Maybe... @sunilmut forgot to include "netstat (#2084)" item or something to not working list, I guess :) But... as mentioned on #2084, nc (i,e., nc.openbsd) command works. |
@sunjoong Oh my goodness, I thought it works because of the following output:
|
@tats-u - I'm not sure weither netstat is working or not working; I have just searched it :) and netstat of mine does not work :(. On https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/17532637-netstat-appears-to-report-nothing , someone had said netstat had worked on 14986.rs_prerelease.161202-1928, but... other said it did not work on 15063 on #2084. Netstat is not included to working list nor not working list on the recent @sunilmut's list, you know. More confused.... #2084 was labeled as duplicate to #69 and closed becasue it was duplicated, but #69 was also closed becasue it contained too many issues, so both #2084 and #69 were closed for duplication like deadlock. BTW, opener of #2084 had mentioned /proc/net/tcp but... it might be " |
Since #2084 is closed, this tracker is as good a place as any for In the
Which is to say, if you There is a User Voice here with a big 5 votes as of this writing, for what it is worth. |
Thanks for the report. I can confirm that netstat does not work. And, yes @sunjoong, I forgot to include netstat in my working list. There are few blockers on the way for netstat and @therealkenc has listed some of them. We are working towards getting these tools to work. |
What's the status of this issue? |
why not solve this issue? |
note solved with ubuntu bionic win build 17134.112 |
@sousagaspar Could you provide a bit more detail ? What exactly is Ubuntu Bionic ? |
I think he meant 'not' instead of 'note', which is a most unfortunate type-o. 'Not' because (among other things) Stay patient. There are reasons to be cautiously optimistic there could (might, maybe, possibly) be some progress afoot in this area. Or, you know, maybe not. But if there is, you'll know. |
still not working. Any ideas? |
Because of this https://stackoverflow.com/a/38920711, you can run (any?!) windows exe from wsl bash, so: |
I tried a similar approach by executing a Windows command (netstat.exe) from WSL with the hope that netstat on Windows works as expected and returns the PID. The problem with such approaches is that the same process has PID xxx in Windows but is yyy in WSL so there is no way to correlate between the two pids. |
Therefore, wsl will not support the |
Well Done! but the native solution will be better |
alias netstat='/c/Windwos/System32/netstat.exe' add in file .bashrc or .profile source .bashrc or .profile |
netstat still no working in ver. 10.0.17763.914 |
In my case this (+ fixing a typo) worked:
To append it to your
|
@therealkenc WSL2 has a different network configuration. While WSL1 has the same one as host, WS2 behaves a VM in a local network like other Hyper-V VMs and Docker containers in Linux. |
This helps me a lot. Works like a charm. Thanks~ |
@sunilmut Hello Sir, could you please share an update on the status of this ticket? Is it on a todo list perhaps, or put into oblivion? |
This bug-tracker is monitored by developers and other technical types. We like detail! So please use this form and tell us, concisely but precisely, what's up. Please fill out ALL THE FIELDS!
If you have a feature request, please post to the UserVoice. If you're reporting a BSOD, don't post here! Instead, e-mail "secure@microsoft.com", and if possible attach the minidump from "C:\Windows\minidump".
Your Windows build number: (Type
ver
at a Windows Command Prompt)10.0.15063
What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
The administrator-privileged BoW also outputs same as above.
Linux example:
<cmd>
is failing, then runstrace -o strace.txt -ff <cmd>
, and post the strace.txt output here)See our contributing instructions for assistance.
The text was updated successfully, but these errors were encountered: