| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| playground:playground [2019/08/23 10:35] – vgaetera | playground:playground [2024/08/17 15:32] – [Bootlogs] thomascrisan |
|---|
| ====== PlayGround ====== | ====== PlayGround ====== |
| <WRAP info> | |
| The playground is for experimenting. Play around as you like!\\ | |
| This page is for playing around and experimenting only, and can be deleted any time, therefore don't put anything here that shall last long time.\\ | |
| Use the [[inbox:start|Inbox]] to create new pages that are WIP, but shall find a permanent place in the wiki once they are considered finished. | |
| </WRAP> | |
| |
| test1 | ====== Bootlogs ====== |
| {{tag>ns1:tag1 ns1:tag2 ns2:subns1:tag3}} | ==== OEM bootlog ==== |
| | <WRAP bootlog> |
| | <nowiki> |
| | ... TBD ... |
| | </nowiki> |
| | </WRAP>\\ |
| |
| test2 | ====== Bootlogs ====== |
| {{topic>ns1?tag1 tag2}} | OpenWrt's implementation of IEEE 802.11s provides a framework for creating wireless mesh networks, which allow devices to connect without a central access point, using each device as a node that forwards data to other nodes. This setup is particularly beneficial for extending network coverage and creating resilient network topologies. |
| |
| test3 | ==== Key Features and Setup ==== |
| {{topic>.?tag1 tag2}} | |
| |
| test4 | 1. **Mesh Network Mode**: IEEE 802.11s introduces a mesh network mode distinct from the traditional infrastructure mode. In this setup, each node can forward 802.11 frames, potentially extending the network's range and robustness[4]. |
| {{count>tag1 tag2}} | |
| |
| test5 | 2. **Configuration**: |
| {{count>tag1 tag2 tag3&. ns1 ns2}} | - OpenWrt uses the Unified Configuration Interface (UCI) system to manage network configurations. The `/etc/config/wireless` file is crucial for defining wireless interfaces and their roles, such as access points or mesh points[1]. |
| | - The `iw` utility is used to configure and manage wireless devices, showing radios and associated interfaces. However, manual configuration through `iw` is generally not necessary as UCI handles these settings[1]. |
| |
| test6 | 3. **Performance Considerations**: |
| {{topic>openvpn}} | - Users have reported performance issues with OpenWrt's 802.11s implementation compared to proprietary solutions like Linksys OEM firmware. This is partly due to the lack of hardware optimizations for 802.11s in many Wi-Fi chips, which are often optimized for access point and station modes instead[2]. |
| | - The throughput in OpenWrt's 802.11s mesh networks may be lower than expected, and adjustments such as changing Wi-Fi drivers or configurations may be necessary to optimize performance[2]. |
| |
| test7 | 4. **Mesh Parameters**: |
| {{count>openvpn}} | - Parameters such as `mesh_hwmp_rootmode` are important for mesh stability and can be configured using tools like `mesh11sd`. However, setting these parameters may require a deeper understanding of the mesh protocol and network requirements[5]. |
| | |
| | 5. **Best Practices**: |
| | - For reliable operation, especially in complex setups involving multiple access points, it's recommended to use Spanning Tree Protocol (STP) to prevent route loops[3]. |
| | - Ensuring that each mesh node is configured to seek the strongest local access point can improve network performance and reliability[3]. |
| | |
| | OpenWrt's 802.11s implementation is a robust solution for creating mesh networks, but it requires careful configuration and optimization to achieve the best performance. Users may need to experiment with different settings and hardware configurations to meet their specific network needs. |
| | |
| | Citations: |
| | [1] https://forum.openwrt.org/t/802-11s-based-wireless-mesh-network-configuration-better-documentation/93645 |
| | [2] https://forum.openwrt.org/t/not-so-great-speeds-on-mesh-802-11s/148175 |
| | [3] https://forum.openwrt.org/t/best-practice-for-multi-ap-wlan-802-11s-and-route-loops/162092 |
| | [4] https://mjuenema.github.io/80211s_wireless_mesh/ |
| | [5] https://forum.openwrt.org/t/more-information-about-mesh-parameters/195234 |
| | |
| | * * * |
| | In the IEEE 802.11s mesh design, the Time-To-Live (TTL) settings are not specifically meant to prevent switching loops. Instead, TTL is used to limit the lifespan of a packet within the network by reducing its value each time it is forwarded by a mesh node. This mechanism helps prevent packets from circulating indefinitely in the network, which can occur in the presence of routing loops or network topology changes[1]. |
| | |
| | Switching loops, on the other hand, are typically addressed by using routing protocols that can dynamically adjust to network changes, such as the Hybrid Wireless Mesh Protocol (HWMP), which is the default path selection protocol in IEEE 802.11s networks[2]. These protocols ensure that data packets follow optimal paths and help prevent loops by maintaining updated routing tables. |
| | |
| | Citations: |
| | [1] https://datatracker.ietf.org/meeting/110/materials/slides-110-babel-babel-for-ieee-80211-wi-fi-mesh-00 |
| | [2] https://www.acldigital.com/sites/default/files/2020-07/802-Wireless-Mesh-Solution.pdf |
| | [3] https://forum.openwrt.org/t/more-information-about-mesh-parameters/195234 |
| | [4] https://forum.openwrt.org/t/802-11s-based-wireless-mesh-network-configuration-better-documentation/93645 |
| | [5] https://mjuenema.github.io/80211s_wireless_mesh/ |
| | * * * |
| | In an IEEE 802.11s mesh network, the Time-To-Live (TTL) setting plays a crucial role in managing network performance by controlling the lifespan of packets within the network. Here's how TTL affects performance: |
| | |
| | 1. **Prevention of Packet Circulation**: TTL helps prevent packets from circulating indefinitely within the mesh network. Each time a packet is forwarded by a mesh node, the TTL value is decremented. Once the TTL reaches zero, the packet is discarded. This mechanism ensures that packets do not loop endlessly, which could congest the network and degrade performance[1]. |
| | |
| | 2. **Network Efficiency**: By limiting the number of hops a packet can take, TTL helps maintain network efficiency. It ensures that packets are only forwarded a reasonable number of times, reducing unnecessary load on the network and conserving bandwidth[1]. |
| | |
| | 3. **Control Over Network Reach**: TTL settings can be adjusted to control how far packets are allowed to travel within the mesh network. This can be useful in large networks to prevent packets from reaching nodes that are too far away, which might not be necessary for certain applications[1]. |
| | |
| | Overall, TTL is an important parameter in managing the performance and reliability of an 802.11s mesh network by preventing packet loops and controlling packet propagation. |
| | |
| | Citations: |
| | [1] https://datatracker.ietf.org/meeting/110/materials/slides-110-babel-babel-for-ieee-80211-wi-fi-mesh-00 |
| | [2] https://www.acldigital.com/sites/default/files/2020-07/802-Wireless-Mesh-Solution.pdf |
| | [3] https://upcommons.upc.edu/bitstream/handle/2099.1/12595/PFCE_Marc_Esquius.pdf |
| | [4] https://mjuenema.github.io/80211s_wireless_mesh/ |
| | [5] https://www.areinhardt.de/publications/2012/Reinhardt_LCN_2012.pdf |
| | |
| | * * * |
| | The Time-To-Live (TTL) setting in IEEE 802.11s mesh networks impacts scalability in several ways: |
| | |
| | 1. **Limiting Packet Propagation**: TTL restricts how far packets can travel within the network by limiting the number of hops a packet can take before being discarded. This helps prevent packets from circulating indefinitely, which is crucial in large networks to avoid congestion and excessive resource usage[4]. |
| | |
| | 2. **Network Efficiency**: By controlling packet lifespan, TTL ensures that only necessary packets are forwarded across the network. This reduces the load on the network infrastructure, thereby improving efficiency and potentially enhancing scalability as the network grows[4]. |
| | |
| | 3. **Resource Management**: In a scalable mesh network, managing resources like bandwidth and processing power is essential. TTL helps in conserving these resources by preventing unnecessary packet forwarding, which can be particularly beneficial in dense or large-scale deployments[4]. |
| | |
| | 4. **Impact on Routing Protocols**: TTL can influence the performance of routing protocols used within the mesh network. For instance, protocols that rely on broadcasting for route discovery and maintenance might be affected by TTL settings, as it limits the reach of these broadcast messages, potentially impacting the network's ability to scale efficiently[5]. |
| | |
| | Overall, TTL is a critical parameter in managing the scalability of an 802.11s mesh network by controlling packet propagation and ensuring efficient use of network resources. |
| | |
| | Citations: |
| | [1] https://www.dpss.inesc-id.pt/~ler/reports/ricardopinto-midterm.pdf |
| | [2] https://www.mdpi.com/1999-5903/11/4/99 |
| | [3] https://www.acldigital.com/sites/default/files/2020-07/802-Wireless-Mesh-Solution.pdf |
| | [4] https://datatracker.ietf.org/meeting/110/materials/slides-110-babel-babel-for-ieee-80211-wi-fi-mesh-00 |
| | [5] https://www.researchgate.net/publication/225436073_A_Secure_Hybrid_Wireless_Mesh_Protocol_for_80211s_Mesh_Network |
| | * * * |
| | While the search results do not provide specific best practices for setting the Time-To-Live (TTL) in large IEEE 802.11s mesh networks, some general considerations can be inferred based on the nature of mesh networks and the role of TTL: |
| | |
| | 1. **Balancing Reach and Efficiency**: In large mesh networks, setting a TTL that is too high might allow packets to travel unnecessarily long distances, potentially leading to network congestion and inefficiencies. Conversely, setting it too low might prevent packets from reaching distant nodes that are still within the intended network coverage. Therefore, finding a balance is crucial. |
| | |
| | 2. **Network Topology and Density**: Consider the topology and density of the network. In dense networks where nodes are closely spaced, a lower TTL might be sufficient to ensure packets reach their destinations without excessive propagation. |
| | |
| | 3. **Application Requirements**: Different applications may have varying requirements in terms of latency and reliability. Adjusting TTL to meet these requirements can help optimize performance for specific use cases. |
| | |
| | 4. **Testing and Iteration**: It may be beneficial to experiment with different TTL settings in a controlled environment to observe their impact on network performance and scalability. This can help in determining the optimal TTL for a given network configuration. |
| | |
| | 5. **Routing Protocols**: Since TTL interacts with routing protocols, understanding how these protocols handle packet forwarding and route discovery can help in setting an appropriate TTL. For example, protocols like HWMP (Hybrid Wireless Mesh Protocol) might have specific considerations regarding TTL. |
| | |
| | While these points provide a general framework, the optimal TTL setting will depend on the specific characteristics and requirements of the mesh network in question. |
| | |
| | Citations: |
| | [1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3821297/ |
| | [2] https://datatracker.ietf.org/meeting/110/materials/slides-110-babel-babel-for-ieee-80211-wi-fi-mesh-00 |
| | [3] https://www.acldigital.com/sites/default/files/2020-07/802-Wireless-Mesh-Solution.pdf |
| | [4] https://www.mdpi.com/1999-5903/11/4/99 |
| | [5] http://www.makikiweb.com/netsig/2021_05_wireless_mesh.html |
| | |
| | |
| | [802-Wireless-Mesh-Solution.pdf](:/5d52594aca414b56a744fd4264bea598) |
| | |
| | |
| | * * * |
| | The Airtime Link Metric (ALM) is primarily used in IEEE 802.11s mesh networks to evaluate the quality of links based on transmission time and error rates, rather than just the number of hops. ALM influences the path selection process in mesh networks by helping the Hybrid Wireless Mesh Protocol (HWMP) choose paths that optimize these factors. However, ALM does not directly influence the Time-To-Live (TTL) settings in 802.11s mesh networks. |
| | |
| | TTL settings are used to limit the number of hops a packet can take before being discarded, preventing packets from circulating indefinitely and potentially causing network congestion. While ALM helps determine the best paths based on link quality, TTL is concerned with controlling packet lifespan to manage network resources and efficiency. |
| | |
| | In summary, while ALM and TTL both play roles in optimizing network performance, they address different aspects: ALM focuses on path quality, while TTL manages packet propagation limits. There is no direct interaction between ALM and TTL settings, but both contribute to the overall performance and efficiency of the network. |
| | |
| | Citations: |
| | [1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3821297/ |
| | [2] https://web.fe.up.pt/~mricardo/doc/journals/wifix-wcm.pdf |
| | [3] https://www.acldigital.com/sites/default/files/2020-07/802-Wireless-Mesh-Solution.pdf |
| | [4] https://upcommons.upc.edu/bitstream/handle/2099.1/12595/PFCE_Marc_Esquius.pdf |
| | [5] https://www.dpss.inesc-id.pt/~ler/reports/ricardopinto-midterm.pdf |
| | |
| | In an OpenWrt IEEE 802.11s mesh network, "mesh local PS mode" refers to the power-saving mode of a mesh node. This setting indicates whether the mesh node is actively participating in power-saving operations. The modes can be "ACTIVE," meaning the node is not in power-saving mode and is fully operational, or it can be in a power-saving state to conserve energy. This mode is part of the mesh power management features that help optimize the energy consumption of devices within a mesh network[4][5]. |
| | |
| | Citations: |
| | [1] http://www.makikiweb.com/netsig/2021_05_wireless_mesh.html |
| | [2] https://forum.archive.openwrt.org/viewtopic.php?id=64779 |
| | [3] https://github.com/openwrt/mt76/issues/72 |
| | [4] https://forum.openwrt.org/t/cannot-connect-to-batman-mesh/46933 |
| | [5] https://trac.gateworks.com/wiki/expansion/gw16146 |
| | [6] https://github.com/openwrt/openwrt/issues/13880 |
| | [7] http://ipv6hawaii.org/?paged=2 |
| | [8] https://openwisp.io/docs/dev/OpenWISP-dev.pdf |
| | |
| | In an OpenWrt IEEE 802.11s mesh network, "mesh peer PS mode" refers to the power-saving mode of a remote peer link in the mesh network. This setting indicates the power-saving status of a peer node that is part of the mesh network. The possible modes for "mesh peer PS mode" include: |
| | |
| | - **ACTIVE**: The peer is not in power-saving mode and is fully operational. |
| | - **LIGHT SLEEP**: The peer is in a light power-saving state. |
| | - **DEEP SLEEP**: The peer is in a deep power-saving state. |
| | - **UNKNOWN**: The power-saving status of the peer is not known or not applicable[1]. |
| | |
| | Citations: |
| | [1] https://openwrt.github.io/luci/jsapi/network.js.html |
| | [2] http://www.makikiweb.com/netsig/2021_05_wireless_mesh.html |
| | [3] https://forum.archive.openwrt.org/viewtopic.php?id=64779 |
| | [4] https://trac.gateworks.com/wiki/expansion/gw16146 |
| | [5] https://forum.openwrt.org/t/cannot-connect-to-batman-mesh/46933 |
| | [6] https://github.com/openwrt/mt76/issues/72 |
| | [7] https://forum.openwrt.org/t/best-practice-for-multi-ap-wlan-802-11s-and-route-loops/162092 |
| | [8] https://openwrt.org/docs/guide-user/network/wifi/basic |
| | |
| | In an OpenWrt IEEE 802.11s mesh network, "mesh non-peer PS mode" refers to the power-saving mode for all non-peer neighbors. This setting indicates the power-saving status of devices that are not directly peered with the mesh node but are within the network's vicinity. The possible modes include: |
| | |
| | - **ACTIVE**: The non-peer devices are not in power-saving mode and are fully operational. |
| | - **LIGHT SLEEP**: The non-peer devices are in a light power-saving state. |
| | - **DEEP SLEEP**: The non-peer devices are in a deep power-saving state. |
| | - **UNKNOWN**: The power-saving status of the non-peer devices is not known or not applicable[1]. |
| | |
| | Citations: |
| | [1] https://openwrt.github.io/luci/jsapi/network.js.html |
| | [2] https://forum.archive.openwrt.org/viewtopic.php?id=64779 |
| | [3] http://www.makikiweb.com/netsig/2021_05_wireless_mesh.html |
| | [4] https://trac.gateworks.com/wiki/expansion/gw16146 |
| | [5] https://forum.openwrt.org/t/cannot-connect-to-batman-mesh/46933 |
| | [6] https://forum.openwrt.org/t/solved-network-configuration-for-mesh11sd-with-wired-nodes/172472 |
| | [7] https://github.com/openwrt/mt76/issues/72 |
| | [8] https://forum.openwrt.org/t/best-practice-for-multi-ap-wlan-802-11s-and-route-loops/162092 |
| | |
| | In an OpenWrt IEEE 802.11s mesh network, the terms "authorized," "authenticated," "associated," and "preamble" in response to the `iw dev <devname> station dump` command have specific meanings: |
| | |
| | - **Authorized**: This indicates whether a peer is authorized to associate with the network. Authorization is a step that typically follows successful authentication and allows the peer to fully participate in the network[3]. |
| | |
| | - **Authenticated**: This specifies whether the peer has completed the authentication process with the network. Authentication is a security measure that verifies the identity of the peer before it can join the network[3]. |
| | |
| | - **Associated**: This term refers to whether the peer is currently associated with the network. Association is the process by which a device connects to a network and is able to communicate with other devices within that network. |
| | |
| | - **Preamble**: This denotes the preamble mode used by the peer, which can be either "long" or "short." The preamble is a part of the wireless communication protocol that helps synchronize the transmission and reception of data[3]. |
| | |
| | Citations: |
| | [1] https://github.com/openwrt/mt76/issues/72 |
| | [2] https://forum.archive.openwrt.org/viewtopic.php?id=64779 |
| | [3] https://openwrt.github.io/luci/jsapi/network.js.html |
| | [4] https://openwrt.org/docs/guide-user/network/wifi/basic |
| | [5] https://trac.gateworks.com/wiki/expansion/gw16146 |
| | [6] http://www.makikiweb.com/netsig/2021_05_wireless_mesh.html |
| | [7] https://forum.openwrt.org/t/cannot-connect-to-batman-mesh/46933 |
| | [8] https://forum.openwrt.org/t/best-practice-for-multi-ap-wlan-802-11s-and-route-loops/162092 |
| | |
| | In an OpenWrt IEEE 802.11s mesh network, the terms "WMM/WME," "MFP," and "TDLS peer" in response to the `iw dev <devname> station dump` command refer to specific features and capabilities of the wireless connection: |
| | |
| | - **WMM/WME (Wi-Fi Multimedia/Wireless Multimedia Extensions)**: This indicates whether the station supports WMM/WME, which are features that provide Quality of Service (QoS) for wireless networks. They prioritize traffic to improve the performance of applications such as video streaming and voice over IP. |
| | |
| | - **MFP (Management Frame Protection)**: This specifies whether Management Frame Protection is enabled. MFP is a security feature that protects management frames from being spoofed or tampered with, enhancing the security of the wireless network. |
| | |
| | - **TDLS peer (Tunneled Direct Link Setup peer)**: This indicates whether the station supports TDLS, which allows devices to establish a direct link with each other while remaining connected to the access point. This can improve performance by reducing latency and increasing throughput between the two devices. |
| | |
| | Citations: |
| | [1] https://trac.gateworks.com/wiki/expansion/gw16146 |
| | [2] https://forum.archive.openwrt.org/viewtopic.php?id=64779 |
| | [3] https://github.com/openwrt/mt76/issues/72 |
| | [4] http://www.makikiweb.com/netsig/2021_05_wireless_mesh.html |
| | [5] https://forum.openwrt.org/t/cannot-connect-to-batman-mesh/46933 |
| | [6] https://forum.openwrt.org/t/solved-network-configuration-for-mesh11sd-with-wired-nodes/172472 |
| | [7] https://openwrt.github.io/luci/jsapi/network.js.html |
| | [8] https://github.com/openwrt/openwrt/issues/13880 |
| | |
| | If the "Connected Time" is greater than the "Associated at [boottime]" in an OpenWrt IEEE 802.11s mesh network, it suggests that the device has been connected to the network for a longer period than the time since the system booted when it first associated with the network. This situation could occur if the system's clock was adjusted or reset after the device initially associated, leading to a discrepancy between the connected time and the association time relative to the boot time. |
| | |
| | Citations: |
| | [1] https://trac.gateworks.com/wiki/expansion/gw16146 |
| | [2] https://www.reddit.com/r/openwrt/comments/169wu00/could_flashing_openwrt_help_with_long_boot_time/ |
| | [3] https://forum.openwrt.org/t/best-practice-for-multi-ap-wlan-802-11s-and-route-loops/162092 |
| | [4] https://github.com/openwrt/openwrt/issues/12905 |
| | [5] https://forum.openwrt.org/t/cannot-connect-to-batman-mesh/46933 |
| | [6] https://forums.raspberrypi.com/viewtopic.php?t=324925 |
| | [7] https://forum.openwrt.org/t/connection-time-for-associated-stations/155329 |
| | [8] http://www.makikiweb.com/netsig/2021_05_wireless_mesh.html |
| | |
| | If the "Connected Time" is less than the "Associated at [boottime]" in an OpenWrt IEEE 802.11s mesh network, it indicates that the device has been connected to the network for a shorter duration than the time since the system booted when it first associated with the network. This situation can occur if the device was disconnected and reconnected after the initial association. For instance, if a device is associated at 23.836 seconds after boot and has a connected time of 203 seconds, it means the device reconnected to the network after some downtime or disconnection period since the initial association[4]. |
| | |
| | Citations: |
| | [1] https://www.reddit.com/r/openwrt/comments/169wu00/could_flashing_openwrt_help_with_long_boot_time/ |
| | [2] https://forum.archive.openwrt.org/viewtopic.php?id=14333 |
| | [3] https://forum.openwrt.org/t/best-practice-for-multi-ap-wlan-802-11s-and-route-loops/162092 |
| | [4] https://trac.gateworks.com/wiki/expansion/gw16146 |
| | [5] https://news.ycombinator.com/item?id=38934013 |
| | [6] https://forums.raspberrypi.com/viewtopic.php?t=324925 |
| | [7] http://www.makikiweb.com/netsig/2021_05_wireless_mesh.html |
| | [8] https://forum.openwrt.org/t/connection-time-for-associated-stations/155329 |