This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
status-devices [2024/03/02 21:58] – -correct inaccuracies in wireless hardware section hogwild | status-devices [2024/05/07 02:17] – -format-remove one space before bullets hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Device List ====== | ====== Device List ====== | ||
- | \\ The Device List menu displays an overall view of the devices connected to your LAN. This information | + | \\ The Device List menu displays an overall view of the devices connected to your LAN. Information |
\\ {{: | \\ {{: | ||
- | \\ **Interface: | + | \\ **Interface: |
- | * '' | + | *'' |
- | * '' | + | *'' |
- | * This name might be used directly. | + | *This name might be used directly. |
- | * This name might be used indirectly if a bridge, PPP, or VPN connection is associated with the interface. | + | *The name may be used indirectly if a bridge, PPP, or VPN connection is associated with the interface. |
- | * '' | + | *'' |
- | * For example, in the example above, vlan2 represents the WAN interface. | + | *For example, in the example above, vlan2 represents the WAN interface. |
- | * '' | + | *'' |
- | * If you have Virtual Wireless set up, you'll probably have several of these. | + | *If you have Virtual Wireless set up, you'll probably have several of these. |
- | * This will depend on the number of radios in your hardware. | + | *This will depend on the number of radios in your hardware. |
- | * Virtual wireless interfaces will also appear here. | + | *Virtual wireless interfaces will also appear here. |
- | * Main wireless chipset interfaces are named as wlX. | + | *Virtual wireless interfaces are named as wlX.X . |
- | * Virtual wireless interfaces are named as wlX.X . | + | |
- | For WiFi-connected devices, the SSID to which they are connected | + | \\ |
+ | |||
+ | WiFi-connected devices | ||
+ | |||
+ | Device names start at " | ||
- | In FreshTomato, | + | Additional instances are created when virtual interfaces are created (secondary SSIDs). |
\\ **Media: | \\ **Media: | ||
Line 28: | Line 31: | ||
Interface types include: | Interface types include: | ||
- | * Ethernet | + | *Ethernet |
- | * WiFi (2.4GHz) | + | *WiFi (2.4GHz) |
- | * WiFi (5GHz) | + | *WiFi (5GHz) |
- | * Cellular 3G/4G/5G connection to ISP | + | *Cellular/LTE 3G/4G/5G connection to ISP |
- | * PPPoE connection to ISP | + | *PPPoE connection to ISP |
- | * Wireless client (to other router/ | + | *Wireless client (to other router/ |
- | * Wireless bridge (to other router/ | + | *Wireless bridge (to other router/ |
- | * PPTP client | + | *PPTP client |
\\ | \\ | ||
- | WAN interfaces are shown with black and white inverted. A greyed-out power icon represents a device that is disconnected or off. | + | WAN interfaces are shown with black and white inverted. |
- | \\ **MAC Address: **This | + | A greyed-out power icon represents a device that is disconnected or off. |
- | | + | \\ **MAC Address: **is the hardware address associated with the interface. |
+ | |||
+ | | ||
* 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 function is useful only for factory-programmed MAC addresses. | * This function is useful only for factory-programmed MAC addresses. | ||
* It will not work with manually-configured MAC addresses, since they can be arbitrarily assigned. | * It will not work with manually-configured MAC addresses, since they can be arbitrarily assigned. | ||
- | * [DR] stands for //DHCP Reservation. // | + | * [DR] stands for //DHCP Reservation.// |
* This forwards you to the [[: | * This forwards you to the [[: | ||
* From there, checking the //Bound to// option will enable static ARP mapping to the MAC address. | * From there, checking the //Bound to// option will enable static ARP mapping to the MAC address. | ||
Line 60: | Line 65: | ||
* [WLF] forwards you to the [[: | * [WLF] forwards you to the [[: | ||
- | \\ **IP Address: | + | \\ **IP Address: |
+ | |||
+ | If no address is shown, one is not known. This can happen briefly | ||
**Name:** This shows the DHCP Hostname of the client device. If no name is shown, it's usually because the device got its lease on the network from a different router, or this router was rebooted after the lease was given. You can work around this by adding your own dhcp-host reference in the dnsmasq Custom configuration. | **Name:** This shows the DHCP Hostname of the client device. If no name is shown, it's usually because the device got its lease on the network from a different router, or this router was rebooted after the lease was given. You can work around this by adding your own dhcp-host reference in the dnsmasq Custom configuration. | ||
Line 68: | Line 75: | ||
This field is also affected by the "// | This field is also affected by the "// | ||
- | **RSSI: | + | **RSSI: |
+ | |||
+ | RSSI is measured in negative numbers, where 0 is the best possible value. Thus, -53 is a stronger signal than -74. | ||
**Quality: **This is similar to RSSI, but considers other parameters, like noise floor, and interference. Quality is a more accurate assessment of the signal. | **Quality: **This is similar to RSSI, but considers other parameters, like noise floor, and interference. Quality is a more accurate assessment of the signal. | ||
Line 82: | Line 91: | ||
\\ | \\ | ||
- | **Noise floor: **This indicates 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 floor: **This indicates 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. | ||
- | If you experience a strong RSSI //and// a strong Noise floor, the WiFi is likely to be unusable. In these situations, the main cause is usually other routers | + | If you experience a strong RSSI //and// a strong Noise floor, the WiFi is likely to be unusable. In these situations, the main cause is usually other routers/APs 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 sources of interference include: | ||
Line 96: | Line 107: | ||
\\ | \\ | ||
- | Typically, there are fewer sources of interference on the 5GHz band. One source of interference is DFS (Dynamic Frequency Selection) | + | Typically, there is les interference on the 5GHz band. One source of interference is DFS (Dynamic Frequency Selection) |
\\ | \\ | ||
Line 104: | Line 115: | ||
**Measure**: | **Measure**: | ||
- | **Network Discovery**: | + | **Network Discovery**: |
- | Network Discovery can be set to use the Linux **arping** command or the **traceroute** command. Arping is the preferred setting, as it's faster and lighter on resources. However, sometimes, traceroute may perform network discovery more precisely. This is true with Apple devices. | + | Network Discovery can be set to use the Linux **arping** command or the **traceroute** command. Arping is the preferred setting, as it's faster and uses less resources. However, sometimes, traceroute may perform network discovery more precisely. This is true with Apple devices. |
- | To the right of the Network Discovery mode is a non-adjustable countdown timer which represents how often the script is run. Essentially, | + | To the right of the Network Discovery mode is a non-adjustable countdown timer which represents how often the script is run. Essentially, |
\\ | \\ |