Site Tools


status-devices

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
status-devices [2025/02/17 09:45] rs232status-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". Device names start at "0". The first WiFi adapter might be named "wl0". The second adapter might be "eth1".
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. \\ **MAC Address: **the hardware address associated with the interface.
Line 90: Line 90:
 **Name:** the client device's DHCP Hostname. **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]]. 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. **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. **Lease: **displays remaining time in the DHCP lease.
  
-Clicking this 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. 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.+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:20250216-074732.png}}\\  \\+{{:pasted:20250216-074732.png?375}}\\  \\
  
 **Measure**: an extra button on certain (mostly MIPS-based) devices to trigger Noise Floor measurement (interference). **Measure**: an extra button on certain (mostly MIPS-based) devices to trigger Noise Floor measurement (interference).
Line 156: Line 156:
  \\  \\
  
-===== Network Discovery ===== + 
 +===== Network Discovery ===== 
 Recent versions of this function used to populate the Device List have been refined/offer new features. Recent versions of this function used to populate the Device List have been refined/offer new features.
  
Line 195: Line 197:
 Note that these are categories. You cannot select specific interface names. Note that these are categories. You cannot select specific interface names.
  
-Due to hardware/processing restrictions, there is a hardcoded minimum limit of netmask /22 for each interface (providing 1022 IP addresses). Thus, if a local interface has discovery enabled in the configuration, but that interface's netmask is /21 or less, it is not scanned.+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.
  
  \\  \\
Line 228: Line 232:
 once set the very next discovery call will create some troubleshooting info inside the /tmp/discovery.debug file. once set the very next discovery call will create some troubleshooting info inside the /tmp/discovery.debug file.
  
-It is reccommended to leave this NVRAM variable unset during normal operations.+It is recommended to leave this NVRAM variable unset during normal operations.
  
 ''nvram unset discovery_debug''\\ ''nvram unset discovery_debug''\\
 +
 +
 ===== Device List Notes and Troubleshooting ===== ===== Device List Notes and Troubleshooting =====
  
-  * A known issues existsin which 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 connected.+  * 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.
  
  \\  \\
status-devices.1739785520.txt.gz · Last modified: 2025/02/17 09:45 by rs232