nmap not working

[nlogozzo]

• Windows Version Number: 10.0.15063
• Bash Version: Ubuntu 16.04

-After installing nmap, when I try running sudo nmap -v -sn 192.168.0.0/16 to scan my network for devices I get the error:
Couldn't open a raw socket. Error: Permission Denied (13)

-When running nmap -v -sn 192.168.0.0/16 without using sudo I get the error:
Problem binding to interface , errno: 92
socket_bindtodevice : protocol not available

• The output I should be receiving is (example):
  Initiating Ping Scan at 20:14
Scanning 4096 hosts [2 ports/host]
Completed Ping Scan at 20:14, 33.00s elapsed (4096 total hosts)
Initiating Parallel DNS resolution of 4096 hosts. at 20:14
Completed Parallel DNS resolution of 4096 hosts. at 20:14, 0.01s elapsed
Nmap scan report for amazon-3c5740640.home (192.168.1.13)
Host is up (0.095s latency).

[stehufntdev]

Thanks for reporting the issue. WSL currently has limited support for raw sockets. Please give us feedback on UserVoice so we can prioritize the work - https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo

[therealkenc]

#1349. User Voice is here.

[tjwebb]

+1

[bmelnik]

+1 same behavior

[banaabraham]

+1

[cptBuggy]

+1

[Sndav]

+1

[ghost]

+1

[evertondornelas]

+1

[sunilmut]

Marking this duplicate of #1349

[chtapodi]

+1

[raiyuza]

+1

[mrcha0s]

+1

[sstodd7532]

+1

[WizardRyan]

+1

[Oxicode]

+1

[ghost]

+1

[mathisloge]

+1

[danhanley]

+1

[pitmacaloway]

+1

[maddie-j]

+100

[lacraig2]

+1

[sunilmut]

For everyone upvoting here, thanks, we understand that this is an important ask. I would also recommend heading down to the user voice and upvoting there as well. We use that to prioritize.

[dezza]

+1

[chriswood]

This would be great.

[artisticcheese]

I think even better way to use nmap on windows is to just launch docker container with nmap. You don't even need to switch to linux containers if you use windows ones.

Advantages:

1. No need to install and maintain nmap installation and all dependencies
2. Fully reproducible scenario regardless of where you run it
3. Always latest and up to date version of nmap
4. Faster execution time then on WSL

Command is docker run --rm --platform=linux instrumentisto/nmap -p 3389 --script ssl-enum-ciphers 10.40.129.61

PS C:\Users\admin> docker run --rm --platform=linux instrumentisto/nmap -p 3389 --script ssl-enum-ciphers 10.40.129.61
Starting Nmap 7.70 ( https://nmap.org ) at 2018-08-15 10:49 UTC
Nmap scan report for 10.40.129.61
Host is up (0.051s latency).

PORT     STATE SERVICE
3389/tcp open  ms-wbt-server
| ssl-enum-ciphers:
|   TLSv1.0:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A
|       TLS_DHE_RSA_WITH_AES_256_CBC_SHA (dh 1024) - A
|       TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 1024) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_RC4_128_SHA (rsa 2048) - C
|       TLS_RSA_WITH_RC4_128_MD5 (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       Broken cipher RC4 is deprecated by RFC 7465
|       Ciphersuite uses MD5 for message integrity
|       Key exchange (dh 1024) of lower strength than certificate key
|       Weak certificate signature: SHA1
|   TLSv1.1:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A
|       TLS_DHE_RSA_WITH_AES_256_CBC_SHA (dh 1024) - A
|       TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 1024) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_RC4_128_SHA (rsa 2048) - C
|       TLS_RSA_WITH_RC4_128_MD5 (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       Broken cipher RC4 is deprecated by RFC 7465
|       Ciphersuite uses MD5 for message integrity
|       Key exchange (dh 1024) of lower strength than certificate key

[Ironsecurity]

Why not just download the nmap binary installer to windows, install it and run it in either Powershell or command prompt? Works fine... It's obvious that Kali and other WSL apps will not work using nmap. Hoping for next updates will fix this issue.

[danhanley]

Mainly because nmap is a (one of many) precursor for many distributed systems which won't run on WSL without proper network support. If we just wanted nmap, as you suggest, then wouldn't bother running WSL :-)

…

On Wed, Aug 15, 2018 at 1:31 PM SecInfo007 ***@***.***> wrote: Why not just download the nmap binary installer to windows, install it and run it in either Powershell or command prompt? Works fine... It's obvious that Kali and other WSL apps will not work using nmap. Hoping for next updates will fix this issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2039 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIre57-wieuo7-2Y2IsMOG0ykti85xCks5uRBSZgaJpZM4NMvac> .

[entr0pia]

+86

[sgf]

Why ppl like Linux because Linux has fewer restrictions, people can do more what they want to do.
Please don't bring the limit from windows to the WSL.if only can do the windows can do,why we should be use WSL?

Soo,when could be the problem soloved?

https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/17817685-support-af-packet-address-family-tcpdump-wireshar

that has 1426 votes now ?
how many votes need ?

[mailinglists35]

that has 1426 votes now ?
how many votes need ?

You don't understand. Our votes do not really count. The uservoice website is just a simulation so you think your opinion matters, but in fact it doesn't.

They blatantly use the name Linux but in fact they don't really want a full blown Linux distro, and instead they just needed a dev environment beucause they realized linux has everything and setting up a dev env on powershell is a painful experience.

[mitokomon]

more than one year passed without solution :/

[sptramer]

This super sucks. WSL has a large number of socket issues.

[findli]

+1

[8270647]

+1

[matthewlewis91]

+1

[abersheeran]

So the problem hasn't been solved yet?

[ThomasSquall]

2 Years and still nothing

[symant233]

Waiting for the solution...

[EbrahimMajdey]

+1

[adotka]

+1

[mailinglists35]

@Moderators, please lock the comments. it's annoying to receive notifications with "+1", when everyone could instead subscribe.

[x41x41x90]

:-/ +1

[dinhluong]

Still waiting ...

[alexverboon]

just tried on the latest windows 10 insider fast ring and wsl 2 and this now seems to work.

[BlackRider97]

+1

[dreamtale90]

+1

[IandI187]

Still no fix? Any other ways around the problem?

[nlogozzo]

I think not

…

On Fri, Jul 12, 2019, 8:56 PM IandI187 ***@***.***> wrote: Still no fix? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2039?email_source=notifications&email_token=AEGUWRK6JJME4M4IYCHXI73P7ER5HA5CNFSM4DJS62OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3FZFQ#issuecomment-511073430>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEGUWROQFIN5QZLIA6IIX33P7ER5HANCNFSM4DJS62OA> .

[rafaelgdp]

Just came here to say that I'm suffering with this issue right now while troubleshooting my currently limited internet connection.

[jmvalente]

I'm also experiencing it. Happens even if using the workaround provided by @kartio

What does seem to work is modifying the alias slightly to alias nmap='"cmd.exe /R /mnt/c/Program Files (x86)/Nmap/nmap.exe"'

edit: For whatever reason this stopped working the morning after I posted this, but alias nmap='powershell.exe -Command nmap.exe' does work.

You may need to specify the full path of nmap.exe if running which nmap.exe doesn't indicate that the executable is in your path.

[Wayc0des-Land]

+1

[Hebertl]

+1