FreshTomato Wiki

User Tools

Site Tools

Trace: • dhcp_reservation • admin_access • howtos • advanced-access • admin-upgrade • qos-detailed • advanced-tor • advanced-misc • wireless_ethernet_bridge • restrict-edit
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/01/22 02:19] – [Device List] hogwildstatus-devices [2025/11/07 16:47] (current) – [Device List Notes and Troubleshooting] hogwild
Line 9: Line 9:
  \\ \\ {{:pasted:20210805-071313.png}} \\  \\ \\ {{:pasted:20210805-071313.png}} \\
  
-\\ **Interface:**  shows the interface on which the router sees the device.+\\  \\ 
 + 
 +**Interface:**  lists the interface on which the router sees the device.
  
-Since release 2021.3, this includes physical/logical interface name, and WiFi SSID.\\   \\+Since r2021.3, this includes the physical/logical interface name and WiFi SSID.\\   \\
  
-  * ''brX''  is a bridge representing the LAN. +  * brX - is a bridge representing the LAN. \\ \\  
-  * ''ethX''  is an Ethernet physical interface. This name might be used\\ directly, or it might be used indirectly if a bridge/PPP/VPN connection \\ is associated with the interface. +  * ethX - is an Ethernet physical interface. This name might be used\\ directly, or it might be used indirectly if a bridge/PPP/VPN connection \\ is associated with the interface. \\ \\  
-  * ''vlanX'' is a virtual interface, always related to a physical interface. \\ For example, in the above example, "vlan2" represents a WAN interface. +  * pppX - is a Point-to-Point Protocol interface, usually on the WAN. \\ \\  
-  * ''wlX'' is a (main) wireless radio interface. +  * vlanX- is a virtual interface, always related to a physical interface. \\ For example, in the above example, "vlan2" represents a WAN interface. \\ \\  
 +  * wlX - is a (main) wireless radio interface.\\ \\ 
     * If you have Virtual Wireless set up, you may have several  \\ of these, depending on the number of radios in your router.     * If you have Virtual Wireless set up, you may have several  \\ of these, depending on the number of radios in your router.
     * Virtual wireless interfaces are named as wlX.Y .     * Virtual wireless interfaces are named as wlX.Y .
Line 22: Line 25:
  \\  \\
  
-WiFi-connected devices appear under the interface name of the SSID to which they are connected.+Devices connected via WiFi appear under the interface name of the connection's SSID.
  
-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 might be "eth1".
  
 When virtual interfaces are created (secondary SSIDs), additional instances are created. When virtual interfaces are created (secondary SSIDs), additional instances are created.
Line 45: Line 48:
  \\  \\
  
-WAN interfaces are shown with black and white inverted.\\ \\+ \\
  
-A greyed-out power icon represents a device that is disconnected device or off.+A WAN interface shows with black and white inverted.
  
- {{:pasted:20240531-232141.png}}+{{::status-device_list-wan_icon-2025.3.png?50}}\\ \\
  
  \\  \\
  
-Clicking on the above icon sends a WoL (Wake-on-LAN) packet to the device to wake it up.+A greyed-out power icon is an off or disconnected device. 
 + 
 +{{::status-device_list-off_or_sleep_icon-2025.3.png?50}} 
 + 
 + \\  \\ 
 + 
 + \\ 
 + 
 +Clicking on a greyed out device icon will wake the device. 
 + 
 +{{::status-device_list-wake_device.png?588}} 
 + 
 +\\
  
-{{:pasted:20240531-232828.png?350}}+You will then be prompted to confirm you want to wake the device.
  
  \\  \\
  
-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. Also, 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 65: Line 80:
  \\  \\
  
-  * Clicking the MAC address opens a search to identify router vendor, \\ based on device OUI ([[https://en.wikipedia.org/wiki/Organizationally_unique_identifier|OUI]]). +  * Clicking a MAC address runs a search to identify the device  \\ vendor, based on its device OUI ([[https://en.wikipedia.org/wiki/Organizationally_unique_identifier|OUI]]). 
     * The OUI is derived from the first 6 digits of its MAC address.      * The OUI is derived from the first 6 digits of its MAC address. 
     * This functions only for factory-programmed MAC addresses.      * This functions only for factory-programmed MAC addresses. 
Line 72: Line 87:
   * [DR] stands for the DHCP Reservation feature//.//   * [DR] stands for the DHCP Reservation feature//.//
     * This forwards you to the [[:dhcp_reservation|DHCP Reservation]] menu \\ where you can assign a reservation to the MAC address.      * This forwards you to the [[:dhcp_reservation|DHCP Reservation]] menu \\ where you can assign a reservation to the MAC address. 
-    * While there, checking //Bound to//  will enable static ARP mapping \\ to the MAC address. This protects against [[https://en.wikipedia.org/wiki/ARP_spoofing|ARP spoofing]].+    * While there, checking //Bound to// will enable static ARP mapping \\ to the MAC address. This protects against [[https://en.wikipedia.org/wiki/ARP_spoofing|ARP spoofing]].
  
   * [BWL] forwards you to the [[bwlimit|Bandwidth Limiter]] menu. There, you \\ can limit the bandwidth of the device with this MAC address.   * [BWL] forwards you to the [[bwlimit|Bandwidth Limiter]] menu. There, you \\ can limit the bandwidth of the device with this MAC address.
Line 78: Line 93:
   * [AR] forwards you to the [[:access_restrictions|Access Restriction]] menu, \\ where you can restrict the device's WAN communications.   * [AR] forwards you to the [[:access_restrictions|Access Restriction]] menu, \\ where you can restrict the device's WAN communications.
  
-  * [WLF] forwards you to the [[:wireless_filter|Wireless Filter]] menu. There, the device's \\ MAC address is prefilled and can be blocked from/allowed \\ to connect via WiFi.+  * [WLF] forwards you to the [[:wireless_filter|Wireless Filter]] menu. There,  \\ the device's MAC address is prefilled and can be blocked from  \\ or allowed to connect via WiFi.
  
 \\  \\ \\  \\
Line 84: Line 99:
 **IP Address:** displays the address linked to the client MAC address. **IP Address:** displays the address linked to the client MAC address.
  
-Unknown addresses aren't shown. This can occur briefly while authenticating, even with WiFi clients with the correct passkey.+Unknown addresses aren't shown. This can occur briefly while authenticating, even for WiFi clients with the correct passkey.
  
  \\  \\
Line 90: Line 105:
 **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 a lease was given. As a workaround, add a //dhcp-host//  reference in dnsmasq //Custom Configuration//.\\  \\ 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//" setting 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 113:
 **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 this router's WiFi clients. It's measured in negative numbers, with "0" as the best value. -53 is a stronger signal than -74.
  
  \\  \\
Line 114: Line 127:
  \\  \\
  
-**Lease: **displays remaining time in the DHCP lease.+**Lease: **displays the remaining time of 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 WiFi device lease and deauthorizes it. A new, manually-set static reservation address will replace the last auto-assigned address. 
 + 
 + \\ {{::status-device_list-delete_lease-2025.3.png?100}}
  
  \\  \\
  
-{{::status-device_list-delete_lease.png?360}}+You will then be prompted to confirm you wish to delete the lease. 
 + 
 + \\
  
  \\  \\
  
-**Noise floor: **indicates the amount of interference affecting each physical radio interface.+**Noise floor: **show the amount of interference affecting each physical radio interface.
  
-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. Interference may increase this value and decrease 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// Noise floor may make WiFi unusable. Usually, this is caused by other WiFi gear on the same channel. Check with the [[tools-survey|Wireless Survey]] tool.
  
  \\  \\
  
-On the 2.4GHz band, common sources of interference include:+On the 2.4GHz band, common interference sources include:
  
  \\  \\
Line 144: Line 161:
  \\  \\
  
-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. DFS lets 5GHz WiFi use frequencies reserved for radar. Ironically, it was designed to reduce interference. DFS interference varies with equipment location. If you suspect 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?294}}\\  \\
  
 **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 175:
  \\  \\
  
-**Network Discovery**: 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.+===== Network Discovery ===== 
 + 
 +Recent versions of Network Discovery used to collect data for Device List have been improved. Since r2021.4, (Discovery v1.7 - 2.0) scans all LAN addresses in the interface's network/netmask. 
 + 
 +Releases since r2025.1 include v2.57 of Discovery. This adds WAN scanning and tweaks to allow better/deeper scanning. It also excludes addresses of devices already in the scan list, or those with a static MAC address. This optimizes scanning activity.
  
-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 until turned off or until you leave the Device List menu. A global page refresh is required to make elements appear/disappear automatically in the List.
  
-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.+(Default: off).
  
-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.+v2.57 also introduced a control for concurrent probes. If discovery is launched while another discovery process is running, the second discovery is skipped. On the other hand, if discovery is ongoing and an option change triggers a second run, this will force the killing of the existing discovery and impose a new execution with the changed options.
  
  \\  \\
  
-**Sanitize result:** clears IP neighbour/ARP table content from spurious information.+**Sanitize result:** clears IP neighbour/ARP table content of spurious information.
  
-Neighbouring devices in a FAILED or INCOMPLETE state are always removed immediately after a scan. However, if this option is enabled, neighbouring devices in a STALE, DELAY or PROBE state also are removed.+Neighbouring devices in a FAILED/INCOMPLETE state are removed immediately after a scan. However, with this option enabled, neighbouring devices in a STALE, DELAY or PROBE state are removed too. Removal is performed after a period defined by (//Max Probes// * 30ms).
  
-This removal is performed after a period defined by (//Max Probes// * 30ms).+ \\ 
 + 
 +{{:pasted:20250121-174729.png?419}}
  
  \\  \\
Line 178: Line 202:
 **Max Probes:** defines how many concurrent probes are allowed at any given time. **Max Probes:** defines how many concurrent probes are allowed at any given time.
  
-If the number rises above the limit, a 250ms delay is used before forking additional probes. A value too high might complete discovery quickly, but might also affect device performance or cause system instability. A low value uses less resources but would delay discovery completion time. The limit is considered globally at system level, not per interface. (Default: 60).+If this value rises above its limit, a 250ms delay occurs before forking additional probes. A value too high might complete discovery quickly, but might also affect device performance/system stability. A low value uses less resources but will delay discovery completion time. The limit is considered globally at a systemic level, not per interface. (Default: 60).
  
  \\  \\
Line 185: Line 209:
  
 Options include: Options include:
 +
 + \\
  
   * LANs *   * LANs *
Line 192: Line 218:
  \\  \\
  
-Note that these are categories. You cannot select specific interface names.+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.+Each interface has a hardcoded minimum of netmask /22 for each interface (or 1022 IP addresses) due to hardware/processing restrictions. Thus, if a local interface had discovery enabled, but its  netmask were /21 or less, it would not be scanned.
  
  \\  \\
Line 202: Line 228:
  \\  \\
  
-  * **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. +  * 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 \\ appear only when this method is used. However this creates spurious \\ device neighbouring records,  so the sanitize option is recommended \\ when using this method. +  * traceroute - might occasionally be needed. Some old Apple devices \\ appear only when this method is used. However this creates spurious \\ device neighbour cache records,  so the sanitize option is recommended \\ when using this method. \\ \\  
-  * **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. +  * 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, then traceroute \\ and then netcat at each consecutive discovery run.+  * all (round-robin**)** - alternates sequentially: arping, then traceroute \\ and then netcat at each consecutive discovery run.
  
  \\  \\
  
-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 nonadjustable countdown timer near //Scan Mode// shows how often the scan runs. 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.+Scan Mode options save/execute as soon as they're selected. Settings are saved in browser cookies. Your browser will remember them.
  
-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.+Network Discovery will likely detect modern WiFi devices connected but in sleep mode. However, their Hostname details may not display until they wake up.
  
- \\ \\ {{:pasted:20250121-174729.png?419}}+ \\
  
 +**Debugging:**
  
-===== Device List Notes and Troubleshooting =====+In the remote case that the discovery does not perform as expected, it's possible to manually set the relevant NVRAM variable:  \\   \\ ''nvram set discovery_debug=1''\\   \\ Once set, the next discovery call will generate troubleshooting information inside the file: "/tmp/discovery.debug".
  
-  * A known issues exists, in 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.+ \\  
 + \\ 
  
- \\+However, it is recommended to leave this NVRAM variable unset during normal operations.  \\   \\  ''nvram unset discovery_debug''\\ 
 + 
 + 
 +===== Device List Notes and Troubleshooting ===== 
 + 
 +  * 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 and ping and traceroute response may have been disabled. Luckily there are very few use cases for static ARP binding. Caution is advised.\\
  
  \\  \\
status-devices.1737512353.txt.gz · Last modified: by hogwild

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki