Windows 10 - built on mingw64 - "could not determine default interface"

robertdavidgraham / masscan

TCP port scanner, spews SYN packets asynchronously, scanning entire Internet in under 5 minutes.

GNU Affero General Public License v3.0

23.47k stars 3.07k forks source link

Windows 10 - built on mingw64 - "could not determine default interface" #734

Closed bill-e-ghote closed 10 months ago

bill-e-ghote commented 12 months ago

I have Npcap installed. I am running as a regular user without local administrator privileges.

bill-e-ghote commented 12 months ago

robertdavidgraham commented 10 months ago

I've cleaned mingw things up a bunch working with multiple different types in 32-bit and 64-bit mode. I think I might've fixed it. If not, could you please tell me which type of mingw you have installed? There are so many.

robertdavidgraham commented 10 months ago

I'm going to close this issue because I think I might've fixed it. please re-open if I haven't.

bill-e-ghote commented 9 months ago

Hi Rob,

Apologies for my long-delayed response. I just cloned the repo into a clean folder. I'm going to guess that masscan requires one to have Admin or SYSTEM privileges in order to access the network devices other than NPF_Loopback? I do not have Admin privs on this work computer.

$ uname -a MSYS_NT-10.0-19045 3.4.10.x86_64 2023-12-22 10:06 UTC x86_64 Msys

Msys2 is installed from here and provides multiple shell environments. https://www.msys2.org/

Compilation fails in the MSYS2 MSYS shell but succeeds in an MSYS2 MINGW64 shell, albeit with one warning:

bill-e-ghote commented 9 months ago

This is Wireshark installed using pacman from within Msys2. The messaging reinforces the need to start service 'npf' as Admin in order to be able to utilize packet capture methods. We may as well keep this one closed as the root problem is my not having "root".