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 [2023/05/13 03:50] – -fix Bandwidth Limiter link hogwild | status-devices [2024/05/07 02:12] – =formatting-wrap bullet points earlier hogwild | ||
---|---|---|---|
Line 5: | Line 5: | ||
\\ {{: | \\ {{: | ||
- | \\ **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. | + | *This name might 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. |
- | * The , depending | + | *This will depend |
- | * Virtual wireless interfaces will also appear here. | + | *Virtual wireless interfaces will also appear here. |
- | * Main Wireless | + | *Main wireless |
- | * 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 |
- | In FreshTomato, | + | Device |
- | \\ **Media**: In this column, an icon represents the interface on which the device is connected and its connection status. | + | Additional instances are created when virtual interfaces are created (secondary SSIDs). |
+ | |||
+ | \\ **Media:** An icon in this column represents the interface on which the device is connected, and its connection status. | ||
Interface types include: | Interface types include: | ||
Line 37: | Line 39: | ||
* PPTP client | * PPTP client | ||
- | WAN interfaces are represented 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** is the physical (hardware) address associated with the interface. | + | \\ **MAC Address: **This is the hardware address associated with the interface. |
- | * Clicking | + | * Clicking the MAC address opens a search to identify the hardware vendor, based on the device' |
* 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 62: | ||
* [WLF] forwards you to the [[: | * [WLF] forwards you to the [[: | ||
- | \\ **IP Address** displays the IP address linked to the MAC address | + | \\ **IP Address:** |
- | **Name** shows the DHCP Hostname of the client device. If no name is shown, it is 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. | + | If no address is shown, one is not known. This can happen briefly while authenticating WiFi devices, even if the WiFi password is correct. |
+ | |||
+ | **Name:** This shows the DHCP Hostname of the client device. If no name is shown, it' | ||
For example, '' | For example, '' | ||
- | This field is also affected by the "// | + | This field is also affected by the "// |
- | **RSSI** | + | **RSSI:** This shows Relative Signal Strength. |
- | **Quality** is similar to RSSI, but considers other parameters, like noise floor, and interference. Quality | + | RSSI is measured in negative numbers, where 0 is the best possible value. Thus, -53 is a stronger |
- | **TX/RX Rate** is the current transmit/ | + | **Quality: |
- | **Lease** displays the time remaining before a DHCP lease expires. The lease time is also a hyperlink. Clicking on it lets you delete the current DHCP lease from the database, and deauthorize the device (if it' | + | **TX/RX Rate: **This is the current transmit/ |
+ | |||
+ | **Lease: **This displays the time remaining before a DHCP lease expires. The lease time is also a hyperlink. Clicking on it lets you delete the current DHCP lease from the database, and deauthorize the device (if WiFi-connected). This is useful when creating static IP reservations, | ||
\\ | \\ | ||
Line 82: | Line 88: | ||
\\ | \\ | ||
- | **Noise floor** 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. |
- | 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 | + | 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/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 94: | Line 102: | ||
* Microwave ovens | * Microwave ovens | ||
- | On the 5GHz band, there are typically fewer sources of interference. One source of interference is DFS (Dynamic Frequency Selection) | + | \\ |
+ | |||
+ | Typically, there is les interference | ||
\\ | \\ | ||
Line 100: | Line 110: | ||
{{: | {{: | ||
- | **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, |
\\ | \\ |