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/10/17 18:45] – [Device List] hogwildstatus-devices [2025/11/07 16:47] (current) – [Device List Notes and Troubleshooting] hogwild
Line 15: Line 15:
 Since r2021.3, this includes the 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 55: Line 56:
  \\  \\
  
-A greyed-out power icon is an off or disconneted device.+A greyed-out power icon is an off or disconnected device.
  
 {{::status-device_list-off_or_sleep_icon-2025.3.png?50}} {{::status-device_list-off_or_sleep_icon-2025.3.png?50}}
Line 227: 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 neighbour cache 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.
  
Line 244: Line 245:
 **Debugging:** **Debugging:**
  
-In the remote case when the discovery might not perform as expected it's possible to set manually the NVRAM variable:+In the remote case that the discovery does not perform as expectedit'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".
  
-''nvram set discovery_debug=1''\\+ \\  
 + \\ 
  
-once set the very next discovery call will create some troubleshooting info inside the /tmp/discovery.debug file. +However, it is recommended to leave this NVRAM variable unset during normal operations.  \\   \\  ''nvram unset discovery_debug''\\
- +
- \\ +
- +
-It is recommended to leave this NVRAM variable unset during normal operations. +
- +
-''nvram unset discovery_debug''\\+
  
  
 ===== Device List Notes and Troubleshooting ===== ===== 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 listeningping and traceroute response may have been disabled. Luckily there are very few use cases for static ARP binding. Caution is advised.\\+  * 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.1760723114.txt.gz · Last modified: by hogwild