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

ipneigh.py

timestamp cleanup

2026-02-11 01:55:02 +00:00

README.md

docs + wf

2025-01-19 23:19:26 +11:00

README.md

Overview

This plugin reads from the ARP and NDP tables using the ip neigh command.

This differs from the ARPSCAN plugin because

It does not send arp requests, it just reads the table
It supports IPv6
It sends an IPv6 multicast ping to solicit IPv6 neighbour discovery

Quick setup guide

To set up the plugin correctly, make sure to add in the plugin settings the name of the interfaces you want to scan. This plugin doesn't use the global SCAN_SUBNET setting, this is because by design it is not aware of subnets, it just looks at all the IPs reachable from an interface.

Usage

Head to Settings > IP Neigh to adjust the settings
Interfaces are extracted from the SCAN_SUBNETS setting (make sure you add interfaces in the prescribed format, e.g. 192.168.1.0/24 --interface=eth1)

Notes

ARPSCAN does a better job at discovering IPv4 devices because it explicitly sends arp requests
IPv6 devices will often have multiple addresses, but the ping answer will contain only one. This means that in general this plugin will not discover every address but only those who answer

Other info

Version: 1.0
Author: KayJay7
Release Date: 31-Nov-2024