Changes between Version 50 and Version 51 of wireless/wifi

Timestamp:

03/30/2020 09:56:42 PM (4 years ago)

Author:

Cale Collins

Comment:

added mesh section

wireless/wifi

@@ -578 +578 @@
   - git git://w1.fi/srv/git/hostap.git (cgit: http://hostap.epitest.fi/cgit/hostap/)
 
+[=#mesh]
+= Mesh Network =
+== What is mesh
+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.
+
+https://en.wikipedia.org/wiki/Mesh_networking
+
+== Getting started with mesh == 
+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. 
+
+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:
+
+CONFIG_MAC80211_MESH=y
+
+CONFIG_LIBERTAS_MESH=y
+
+This can be verified in Linux userspace with the command:
+{{{#!bash
+zcat /proc/config.gz |grep mesh -i
+}}}
+
+During testing attach antennas or attenuators depending on the proximity of the radios.  Without a strong clean signal the network may behave unpredictably.  
+
+=== Configuring your BSP ===
+
+Beyond the aforementioned steps providing anything more than general pointers would be impractical. There are may 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.  
+
+Some circumstance will require testing multiple firmware versions.  Ath10k firmware can be downloaded from this repository:
+
+https://github.com/kvalo/ath10k-firmware
+
+The version of the current firmware being used can be verified by checking dmesg. 
+{{{#!bash
+dmesg |grep ath -i 
+}}}
+Example:
+{{{
+[   16.699066] ath10k_pci 0000:07:00.0: firmware ver 10.2.4-1.0-00037 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 a4a52adb
+}}}
+
+Depending on the firmware version you may be required to use a module parameter for rawmode.  In some situations using rawmode will cause the interface to not appear, it is best to test without this option enabled first.  When configuring the network you may receive a message informing you that it is required. 
+
+To enable raw mode:  
+{{{#!bash
+setenv bootargs "${bootargs} ath10k_core.rawmode=1"
+}}}
+This option can also be enabled in the bootscript.  On Newport make changes to "newport.env".    
+
+Check that your wireless interface is available:
+{{{#!bash
+ls /sys/class/net/
+}}}
+
+Check mesh point is an available network type: 
+{{{#!bash
+iw list |grep "mesh point"
+}}}
+If these two items are present proceed with bringing up with mesh interface.
+
+=== Bringing up the mesh network interface using "iw" ===
+
+Reference:
+* https://wireless.wiki.kernel.org/en/users/drivers/ath10k/mesh
+
+Create a mesh point interface “mesh0”.
+{{{#!bash
+iw phy phy0 interface add mesh0 type mp
+}}}
+Confirm the creation of the new interface.
+{{{#!bash
+iw mesh0 info
+Interface mesh0
+        type mesh point
+}}}
+Configure channel information, all radios on the networking must be configured to use the same frequency.
+{{{#!bash
+iw dev mesh0 set freq 5745 80 5775
+}}}
+
+Optionally, the interface’s MAC address can be set.
+{{{#!bash
+ifconfig mesh0 hw ether 00:11:22:33:44:56
+}}}
+
+Assign a static IP and bring up the interface.
+{{{#!bash
+ifconfig mesh0 192.168.1.10
+}}}
+
+Join a network. “mesh-ath10k” is the mesh ID which can be maximum of 32 bytes long.
+{{{#!bash
+iw dev mesh0 mesh join mesh-ath10k
+}}}
+
+Verify link status, this command will not return anything unless there are minimum two peers on the network.  
+{{{#!bash
+iw mesh0 station dump
+}}}
+
+=== Bringing up the mesh network interface using "wpa_supplicant" ===
+
+Some firmware will require compiling wpa_supplicant from source. 
+
+Download the source code from this address:
+
+http://www.linuxfromscratch.org/blfs/view/svn/basicnet/wpa_supplicant.html
+
+Install required packages:
+{{{#!bash
+apt-get install libssl-dev dbus libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libnl-3-dev libnl-genl-3-dev build-essential -y
+}}}
+Extract the .tar and create a .config:
+{{{#!bash
+tar -xvf wpa_supplicant-2.9.tar.gz
+cd wpa_supplicant-2.9/wpa_supplicant/
+cp defconfig .config
+}}}
+
+Use "vi" to edit the .config file, make sure CONFIG_MESH is not commented out and verify it is enabled:
+{{{
+CONFIG_MESH=y
+}}}
+
+Build wpa_supplicant:
+{{{#!bash
+make all & make install
+}}}
+* Optional - execute the command "which wpa_supplicant" to locate the file that is currently in your $PATH and replace it with the one you have freshly built. 
+Verify that wpa_supplicant is the desired version:
+{{{#!bash
+wpa_supplicant -v 
+}}}     
+Create an /etc/wpa_supplicant.conf file with the following contents:
+{{{ 
+ctrl_interface=/var/run/wpa_supplicant
+user_mpm=1
+network={
+        ssid="Mesh0"
+        mode=5
+        frequency=2442
+        key_mgmt=NONE
+}}}
+Create a mesh point interface “mesh0”:
+{{{#!bash
+iw phy phy0 interface add mesh0 type mp
+}}}
+Optinally set the interface’s MAC address:
+{{{#!bash
+ifconfig mesh0 hw ether 00:11:22:33:44:56
+}}}
+Assign a static IP and bring up the interface.
+{{{#!bash
+ifconfig mesh0 192.168.1.10
+}}}
+Verify wpa_supplicant is not already running, if so kill the PID:
+{{{#!bash
+ps -ef |grep wpa 
+kill -9 <PID>
+}}}
+Launch wpa_supplicant, run in the background.
+{{{#!bash
+wpa_supplicant -Dnl80211 -imesh0 -c /etc/wpa_supplicant.conf -B $
+}}}
+Check that two peers are connected:
+{{{#!bash
+iw mesh0 station dump
+}}}
+=== Pre-built image ===
+Gateworks does not offer an official pre-built image for mesh networking.  The .img.gz that was used for testing with Newport is linked below.    
+
+http://dev.gateworks.com/fae/mesh-newpor54.img.gz
+
+
+= Drivers =
 [=#drivers]
 == Linux Kernel Drivers ==