Skip to content

Basic Usage#

Binaries#

Running as a binary allows you to skip dealing with any container related networking issues and leverage the same network interface that the host machine is using.

You can validate that the binary is working by scanning the publicly available scanme.sh.

networkscan discover port --target 127.0.0.1 --ports 22 --ports 80

Docker#

Running networkscan within a Docker container should typically work similarly to running directly on a host, however, occasionally there are a few things to keep in mind.

If you're running on a Docker container on a MacOS machine and you are trying to scan a locally running service, you can leverage the host.docker.internal address as mentioned in the Docker documentation here.

docker run ghcr.io/method-security/networkscan discover port --target 127.0.0.1 --ports 22 --ports 80