Changes between Version 7 and Version 8 of wireless/wifi/mesh
- Timestamp:
- 04/01/2020 04:03:39 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
wireless/wifi/mesh
v7 v8 1 fnetw[=#mesh] 2 = Mesh Network = 1 [[PageOutline]] 2 [=#mesh] 3 = Mesh Networking = 4 5 This wiki page is an showcase exhibiting 802.11s Mesh Networking on Gateworks Single Board Computers. 6 3 7 [[Image(mesh01.png,600px)]] 4 8 5 This screenshot was generated using Zenmap. Nmap ping scan was ran on a Gateworks board with two peers connected via mesh, scan output was then exported to a desktop PC in .xml format.6 9 7 == What is mesh 10 11 This screenshot helps visualize a mesh network. It was generated using Zenmap. Nmap ping scan was ran on a Gateworks board with two peers connected via mesh, scan output was then exported to a desktop PC in .xml format. 12 13 == What is Mesh Networking 8 14 A mesh network is a local network topology in which nodes connect dynamically without a hierarchy. Data transfer will follow the most efficient path between clients. This technology is applicable in many different industries, such as transportation, defense, and energy sectors. 9 15 … … 11 17 12 18 == Getting started with mesh == 13 Unfortunately, there's not an all purpose approach for how a mesh network should be configured. It will require research to decide what hardware and software configuration will fit your needs closest. The first thing to consider is what radio to use, not all radios support mesh and some that do will require specific kernel versions or firmware to accomplish this. The best source of information will be the radio manufacturer — something to consider when selecting a radio is the level of support that will be available. Linux kernel mailing lists should be used as a primary resource if you suspect there's an issue with the driver, kernel, or radio firmware. WLE900VX is an excellent choice of radio and is available from the [https://shop.gateworks.com/ Gateworks store]. This radio has been tested to work with 4.14, 4.20, and 5.4 kernels. A second radio which has been tested by Gateworks is the WPEQ-261ACNI(BT), this card is half length and includes bluetooth. According to the manufacturer this card will only mesh in kernel versions 5.3 and newer, and only when using a custom built wpa_supplicant. When creating a mesh network not all radios need to be the same model, we have tested creating a mesh network using a combination of these two radio models successfully.19 There are many variables in mesh networking, thus there's not an all purpose approach for how a mesh network should be configured. It will require research to decide what hardware and software configuration will fit your needs closest. 14 20 15 Select a BSP that is appropriate for your application. In our testing the Bionic Ubuntu root filesystem was used with both Newport and Ventana family boards. OpenWRT and Buildroot are viable options as well. Enabling the necessary kernel modules will be required, though you may find in Gateworks kernel defconfigs these options have already been added. In our testing the following kernel config options were enabled: 21 ==== Single Board Computer 22 Gateworks manufactures ARM single board computers that act as a node in a mesh network. The single board computers have Mini-PCIe slots that allow for WiFi Mini-PCIe cards. 23 24 Gateworks offers a few different families of SBCs, with each family having a specific CPU. The Newport Family features a 64-bit CPU with DDR4 RAM while the Ventana Family features a 32-bit ARM CPU with DDR3 RAM. Both families are excellent choices as platforms in a mesh network. 25 26 ==== !WiFi Radios 27 28 The first thing to consider is what radio to use, not all radios support mesh and some that do will require specific kernel versions or firmware to accomplish this. The best source of information will be the radio manufacturer — something to consider when selecting a radio is the level of support that will be available. Linux kernel mailing lists should be used as a primary resource if you suspect there's an issue with the driver, kernel, or radio firmware. WLE900VX is an excellent choice of radio and is available from the [https://shop.gateworks.com/ Gateworks store]. This radio has been tested to work with 4.14, 4.20, and 5.4 kernels. A second radio which has been tested by Gateworks is the WPEQ-261ACNI(BT), this card is half length and includes bluetooth. According to the manufacturer this card will only mesh in kernel versions 5.3 and newer, and only when using a custom built wpa_supplicant. When creating a mesh network not all radios need to be the same model, we have tested creating a mesh network using a combination of these two radio models successfully. 29 30 Recommended WiFi Radio: 31 * [https://shop.gateworks.com/index.php?route=product/product&product_id=196 Gateworks GW17032 - Compex WLE900VX 802.11AC Radio] 32 33 ==== Operating System 34 35 Select a Board Support Package (BSP) that is appropriate for your application. In our testing the Bionic Ubuntu root filesystem was used with both Newport and Ventana family boards. OpenWRT and Buildroot are viable options as well. Enabling the necessary kernel modules will be required, though you may find in Gateworks kernel defconfigs these options have already been added. In our testing the following kernel config options were enabled: 16 36 17 37 CONFIG_MAC80211_MESH=y … … 26 46 During testing attach antennas or attenuators depending on the proximity of the radios. Without a strong clean signal the network may behave unpredictably. 27 47 28 === Configuring your BSP ===48 === Configuring your Operating System / BSP === 29 49 30 50 Beyond the aforementioned steps providing anything more than general pointers would be impractical. There are many variables in how hardware can behave, what works in one case will cause a different configuration to fail. The following guidance is intended for those using Ath10k radios.
