vh/NetAlertX
1
0
Fork 0
mirror of https://github.com/jokob-sk/NetAlertX.git synced 2026-04-09 19:51:57 -07:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

DOCS: subnets
Some checks are pending
✅ Code checks / check-url-paths (push) Waiting to run
Details
✅ Code checks / lint (push) Waiting to run
Details
✅ Code checks / docker-tests (push) Waiting to run
Details
🐳 👩‍💻 docker dev / docker_dev (push) Waiting to run
Details
📘 Deploy MkDocs / deploy (push) Waiting to run
Details

Browse Source 
Signed-off-by: jokob-sk <jokob.sk@gmail.com>
This commit is contained in:
jokob-sk
2026-04-10 07:58:07 +10:00
parent 6044a41852
commit 623fabd125
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/SUBNETS.md
View File

@@ -11,11 +11,12 @@ You need to specify the network interface and the network mask. You can also con
> If this command returns no results: > If this command returns no results:
> >
> - ✅ If you see output like `IPv4: (none)` or `Using 0.0.0.0`: > - ✅ If you see output like `IPv4: (none)` or `Using 0.0.0.0`:
> → The interface was not detected correctly. > - The interface was not detected correctly.
> → Fix: explicitly set the interface using `--interface=<name>`. > - Fix: explicitly set the interface using `--interface=<name>`.
> >
> - ❌ If the scan runs correctly but still finds no devices: > - ❌ If the scan runs correctly but still finds no devices:
> → The network may not be accessible due to firewall, VLAN, or network restrictions (Wi-Fi extenders, VPNs, etc.). If direct scans are not possible, check the [remote networks documentation](./REMOTE_NETWORKS.md) for workarounds. > - The network may not be accessible due to firewall, VLAN, or network restrictions (Wi-Fi extenders, VPNs, etc.).
> - If direct scans are not possible, check the [remote networks documentation](./REMOTE_NETWORKS.md) for workarounds.
## Example Values ## Example Values