NetAlertX

mirror of https://github.com/jokob-sk/NetAlertX.git synced 2026-04-04 01:01:35 -07:00

Files

sebingel 4c117db463 Fix elementOptions: rename typo 'ordeable' to 'orderable'

The key 'ordeable' in elementOptions was a long-standing typo for the
correct English word 'orderable'. Since the JS check in settings_utils.js
used the same misspelled key, the feature appeared to work — but it was
relying on the consistent propagation of a typo across the entire codebase.

Two pre-existing entries in front/plugins/ui_settings/config.json already
used the correct spelling 'orderable', but these had no effect because the
JavaScript check (option.ordeable === 'true') never matched them. As a
result, orderable behavior was silently disabled for those two settings.

Changes:
- front/js/settings_utils.js: renamed option.ordeable → option.orderable
  and isOrdeable → isOrderable (6 occurrences, lines 792/823/824/880/1079/
  1192/1228). The JS key check is the authoritative definition of the
  elementOptions property name, so this must change atomically with all
  config files.

- server/initialise.py:245: renamed "ordeable" → "orderable" in the
  hardcoded JSON string for LOADED_PLUGINS setting. This string is the
  source-of-truth for that setting's elementOptions and is not auto-
  generated from the plugin config files.

- front/plugins/*/config.json (33 files, 90 occurrences): renamed all
  "ordeable": "true" entries to "orderable": "true" via sed. All plugins
  used the typo consistently; they must be updated in the same commit to
  avoid a broken intermediate state.

The two formerly broken 'orderable' entries in ui_settings/config.json
are now matched by the corrected JS check and work as intended.

Fixes netalertx/NetAlertX#1584

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-04-03 18:28:48 +00:00

config.json

Fix elementOptions: rename typo 'ordeable' to 'orderable'

2026-04-03 18:28:48 +00:00

nmap_dev.py

PLG: ICMP v2 + incorrect import #1331

2026-01-04 11:32:45 +11:00

README.md

DOCS: new URL https://docs.netalertx.com/

2026-01-13 20:16:43 +11:00

README.md

Overview

NMAP-scan is a command-line tool used to discover and fingerprint IP hosts on your network. The NMAP-scan (and other Network-scan plugins using the SCAN_SUBNETS setting) runtime depends on the number of IP addresses to check — so configure it carefully with the appropriate network mask and interface.

Refer to the subnets documentation for help with setting up VLANs, understanding which VLANs are supported, and determining your network mask and interface.

Note

The NMAPDEV plugin is excellent for detecting device availability, but ARP-scan is better for scanning across multiple VLANs and subnets. NMAP cannot retrieve MAC addresses from other subnets (an NMAP limitation), which are often required to identify devices. You can safely combine different scan methods. See all available network scanning options (marked with 🔍 dev scanner) in the Plugins overview.

This plugin is not optimized for name resolution (use NSLOOKUP or AVAHISCAN instead), but if a name is available it will appear in the Resolved Name column.

Usage

In Settings, configure the SCAN_SUBNETS value as described in the subnets documentation. The plugin automatically strips unsupported --vlan parameters and replaces --interface with -e.
Enable the plugin by setting the RUN parameter from disabled to your preferred run mode (usually schedule).
Specify the schedule using the NMAPDEV_RUN_SCHD setting.
Adjust the scan timeout if necessary with the NMAPDEV_RUN_TIMEOUT setting.
If scanning remote networks, consider enabling the NMAPDEV_FAKE_MAC setting — review its description carefully before use.
Review all remaining settings.
Click SAVE.
Wait for the next scheduled scan to complete.