ARP-SCAN and NMAPDEV cannot operate with the same subnet settings if `--vlan` parameter used

[a-bali]

Is there an existing issue for this?

• I have searched the existing open and closed issues and I checked the docs https://jokob-sk.github.io/NetAlertX/

The issue occurs in the following browsers. Select at least 2.

• Firefox
• Chrome
• Edge
• Safari (unsupported) - PRs welcome
• N/A - This is an issue with the backend

Current Behavior

If I want to have VLANs scanned, it seems I cannot have it with both the ARP-SCAN and NMAPDEV plugins enabled, as:

• ARP-SCAN requires to be ran with the following parameters: 10.10.10.0/24 --interface=eth0 --vlan=10
• NMAP does not have a --vlan option
  So in SCAN_SUBNETS I can specify parameters that are either valid for ARP-SCAN or for NMAP, but not for both.

Expected Behavior

Recommendation: move SCAN_SUBNETS option to the device scanner level or implement a generic subnet configuration option that will generate specific configs for device scanners.

Steps To Reproduce

No response

app.conf

docker-compose.yml

What installation are you running?

Production (netalertx)

app.log

No response

Debug enabled

• I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.

[jokob-sk]

Thanks for the request. The next release will be stripping unsupported --vlan parameters from the subnets settings in the NMAPDEV plugin.

You can test this by mapping this file app/front/plugins/nmap_dev_scan/nmap_dev.py to this new version: https://raw.githubusercontent.com/jokob-sk/NetAlertX/refs/heads/next_release/front/plugins/nmap_dev_scan/nmap_dev.py

[jokob-sk]

releasing in 15 min -> Closing