Differences

This shows you the differences between two versions of the page.

--- status-devices [2025/01/22 01:32] – -Condense, clarity hogwild
+++ status-devices [2025/02/22 16:19] (current) – [Device List] -Formatting, grammar hogwild
@@ Line 22: / Line 22: @@
  \\
-WiFi-connected devices appear under the interface name of the SSID to which they are connected.
+Devices connected by WiFi appear under the interface name of the SSID to which they are connected.
 Device names start at "0". The first WiFi adapter might be named "wl0". The second adapter might be "eth1".
@@ Line 47: / Line 47: @@
 WAN interfaces are shown with black and white inverted.\\ \\
-A greyed-out power icon represents a disconnected device or one that is off.
+A greyed-out power icon represents a device that is disconnected device or off.
  {{:pasted:20240531-232141.png}}
@@ Line 59: / Line 59: @@
  \\
-For this to work, the client also must support WoL. As well, WoL settings in the BIOS, network adapter and OS may need setting for it to work properly.
+For WoL to work, the client also must support it. As well, WoL settings in the BIOS, network adapter and OS may need adjusting.
 \\ **MAC Address: **the hardware address associated with the interface.
@@ Line 90: / Line 90: @@
 **Name:** the client device's DHCP Hostname.
-If no name is shown, the device got a lease from another router, or this router rebooted after the lease was given. A workaround is to add a //dhcp-host//  reference in the dnsmasq //Custom Configuration// field.
+If no name is shown, the device got a lease from another router, or this router rebooted after the lease was given. A workaround is to add a //dhcp-host//  reference in the dnsmasq //Custom Configuration// field.\\  \\ For example, ''dhcp-host=70:EE:50:37:E8:46,myhostname''
- \\  \\ For example, ''dhcp-host=70:EE:50:37:E8:46,myhostname''
 This field is also affected by the "//Generate a name for DHCP clients which do not otherwise have one//" parameter in [[advanced-dhcpdns|DHCP/DNS/TFTP]].
@@ Line 100: / Line 98: @@
 **RSSI:** shows Relative Signal Strength.
-This applies only to WiFi clients connected to this router. RSSI is measured in negative numbers, where "0" is the best possible value. Thus, -53 is a stronger signal than -74.
+This applies only to WiFi clients connected to this router. RSSI is measured in negative numbers, with "0" as the best possible value. Thus, -53 is a stronger signal than -74.
  \\
@@ Line 116: / Line 114: @@
 **Lease: **displays remaining time in the DHCP lease.
-Clicking this hyperlink deletes a WiFi device's current lease and deauthorizes it. This is useful when creating static IP reservations, to make connected devices refresh their previously automatically-assigned address to a new, manually-set one.
+Clicking this deletes the lease of a WiFi device and deauthorizes it. When creating static IP reservations, this makes connected devices refresh their previously automatically-assigned address to a new, manually-set one.
  \\
@@ Line 128: / Line 126: @@
 Noise, like RSSI, is measured in negative numbers. The best possible value is -100dBm. Any interference will increase the noise value and decrease the Quality.
-If you experience a strong RSSI //and// a strong Noise floor on your WiFi, it may be unusable. In these situations, the main cause is usually other WiFi gear transmitting on the same channel. Use the [[tools-survey|Wireless Survey]] tool to get more information.
+A strong RSSI //and// a strong Noise floor on your WiFi may mean your WiFi is unusable. This is usually caused by other WiFi gear transmitting on the same channel. Use the [[tools-survey|Wireless Survey]] tool to get more information.
  \\
-On the 2.4GHz band, common sources of interference include:
+On the 2.4GHz band, common interference sources include:
  \\
@@ Line 144: / Line 142: @@
  \\
-Typically, there is less interference on the 5GHz band. DFS (Dynamic Frequency Selection) is a common source of interference for certain channels. The DFS function lets 5GHz WiFi use frequencies reserved for radar. Ironically, DFS was designed to reduce interference. DFS interference varies, depending on equipment location. If you suspect DFS interference, see Wikipedia's [[https://en.wikipedia.org/wiki/List_of_WLAN_channels|List of WLAN Channels]] for details.
+Typically, the 5GHz band has less interference.
+DFS (Dynamic Frequency Selection) is a common source of interference for certain channels. This function lets 5GHz WiFi use frequencies reserved for radar. Ironically, DFS was designed to reduce interference. DFS interference varies with equipment location. If you suspect DFS interference, see Wikipedia's [[https://en.wikipedia.org/wiki/List_of_WLAN_channels|List of WLAN Channels]] for details.
  \\
-{{:pasted:20210804-210755.png}} \\  \\
+{{:pasted:20250216-074732.png?375}}\\  \\
 **Measure**: an extra button on certain (mostly MIPS-based) devices to trigger Noise Floor measurement (interference).
@@ Line 156: / Line 156: @@
  \\
-**Network Discovery**: recent versions of this function used to populate the Device List have been refined/offer new features.
-Since r2021.4, Network Discovery versions 1.7 - 2.0 scan all LAN IP addresses defined in the interface's network/netmask to populate the Device List.
+===== Network Discovery =====
-R2025.1 and later include network discovery v2.57. This version adds WAN scanning, and tweaks to allow better/deeper scanning. Version 2.57 also excludes the addresses of devices already in the scan list, or those with a statically-defined MAC address. These optimize scanning activity.
+Recent versions of this function used to populate the Device List have been refined/offer new features.
+Since r2021.4, Network Discovery (v1.7 - 2.0) scan all LAN IP addresses defined in the interface's network/netmask.
+R2025.1 and later: include v2.57. This version adds WAN scanning and tweaks to allow better/deeper scanning. Version 2.57 also excludes the addresses of devices already in the scan list, or those with a statically-defined MAC address. These optimize scanning activity.
 When enabled, discovery runs continuously and stops when set to "off" or when you leave the Device List page. (Default: off). This requires a global page refresh to have elements appear/disappear automatically in the Device List table.
-v2.57 also introduces a control on concurrent probes. If discovery is launched while another discovery process is running, the latter discovery is skipped. On the other hand, if discovery happens to be ongoing and a second run is triggered by any change of options, this would instead force a killing of the existing discovery to then impose a new execution with the modified parameters.
+Version 2.57 also introduces a control for concurrent probes. If discovery is launched while another discovery process is running, the latter discovery is skipped. On the other hand, if discovery happens to be ongoing and a second run is triggered by any change of options, this will instead force a killing of the existing discovery and impose a new execution with the modified parameters.
  \\
@@ Line 182: / Line 185: @@
  \\
-**Scan Target:** default LANs, defines where the probes should be developed in terms of interfaces.
+**Scan Target:** defines on which interfaces devices should be probed.
-Options included here are:
+Options include:
-  * LANs
+  * LANs *
   * WANs
   * LANs and WANs
@@ Line 192: / Line 195: @@
  \\
-These are categories. There is no granular interface name selection allowed. Due to HW/processing restrictions, there is a hardcoded minimum limit of /22 for each interface (providing 1022 IP addresses). Thus, if a given local interface has discovery enabled in the configuration, but the actual interface has a netmask of /21 or less, it.
+Note that these are categories. You cannot select specific interface names.
+There is a hardcoded minimum limit of netmask /22 for each interface (or 1022 IP addresses) due to hardware/processing restrictions.
+Thus, if a local interface has discovery enabled in the configuration, but the interface's netmask is /21 or less, it is not scanned.
  \\
-**Scan Mode:** default off, can be set to arping, traceroute, netcat or all.
+**Scan Mode:** sets the scanning method used to populate Device List.
  \\
-  * **arping** - is the preferred option for scanning as it's fast and doesn't produce any spurious neighbour records, it's good in the great majority of the cases.
+  * **arping** - the preferred option for scanning as it's fast and doesn't \\ produce spurious neighbour records. This is fine in the great majority of cases.
-  * **traceroute** - might occasionally be needed, some old Apple devices for some reason are visible only this way, however this creates spurious device neighbouring records, so the sanitize option is suggested to be enabled with traceroute.
+  * **traceroute** - might occasionally be needed. Some old Apple devices \\ appear only when this method is used. However this creates spurious \\ device neighbouring records,  so the sanitize option is recommended \\ when using this method.
-  * **netcat **(nc) - is an alternative scanning method. Like traceroute it generates spurious neighbouring entries and the sanitize option is effective. It's a good alternative scanning method when devices fail to otherwise be seen.
+  * **netcat **(nc) - as with traceroute, this generates spurious neighbouring entries. \\ The sanitize option corrects for this. This is a good alternative method \\ when devices otherwise fail to be seen.
-  * **all (round-robin)** - alternates sequentially arping, traceroute and netcat at each consecutive discovery run.
+  * **all (round-robin)** - alternates sequentially: arping, then traceroute \\ and then netcat at each consecutive discovery run.
  \\
-The non-adjustable countdown timer next to the Scan Mode shows how often the script runs. Basically, it reflects ARP cache aging-time, and it's expected to vary between e.g. ARM and MIPS devices.
+The unadjustable countdown timer beside //Scan Mode// indicates how often the scan script is run. It reflects ARP cache aging time, and may vary (say, between ARM and MIPS devices).
+The four options above are saved/executed as soon as they're modified (Save is unneeded). The settings are saved in browser cookies and will be remembered by the browser.
+Modern WiFi devices may stay connected to WiFi while in sleep mode. Network Discovery will likely detect those devices, but Hostname information may not display until they awaken.
+ \\ \\ {{:pasted:20250121-174729.png?419}}
+ \\
+**Debugging:**
+In the remote case when the discovery might not perform as expected it's possible to set manually the NVRAM variable:
+''nvram set discovery_debug=1''\\
+once set the very next discovery call will create some troubleshooting info inside the /tmp/discovery.debug file.
-The 4 options in the GUI are saved and executed as soon as they are modified (no Save button is needed). Their settings are saved in the browser's cookies and will be remembered by the browser.
+It is recommended to leave this NVRAM variable unset during normal operations.
-Modern WiFi devices may stay connected to the router while in sleep mode. Network Discovery will likely detect those devices, but Hostname information may not appear until they awaken.
+''nvram unset discovery_debug''\\
- \\ {{:pasted:20250121-174729.png}}
-\\ **Known issues:**
+===== Device List Notes and Troubleshooting =====
-- A device defined with a static mac address (DHCP Reservation/Static Arp option) will appear in the list as connected even if it's not
+  * Due to it's nature, a device defined with a static ARP binding (DHCP Reservation/Static Arp option) will appear in the device list as connected even if it's not switched on or not present. It is very hard to determine if such a device is really up because you might not know on which protocol and port it is listening, ping and traceroute response may have been disabled. Luckily there aren't much use cases for static ARP binding, be cautious.
  \\

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools