The purpose of this change is to improve communication reliability since I will be installing and controlling the MM8108-EKH19 on a small unmanned vehicle. It will not be connected to an external network.
There doesn’t appear to be a GUI frontend for mesh11sd available in the open source, and we don’t provide one.
Are you just wanting the configuration to be persistent? Or will the unmanned vehicle somehow be controlling the configuration of the EKH19 as well?
In either case, I’m not really sure why you can’t use UCI directly?
The reason I requested a GUI is because the person testing the unmanned vehicle is unfamiliar with Linux.
However, there’s a chance that the person might need to change the parameters.
Is the following approach optimal?
Create file
/etc/hotplug.d/iface/99-mesh-params.
Write it like this:
iw dev mesh0 set mesh_param mesh_hwmp_active_path_timeout 2000
iw dev mesh0 set mesh_param mesh_hwmp_preq_min_interval 200
iw dev mesh0 set mesh_param mesh_gate_announcements 1
You will need to insert these values via UCI, which will keep them persistent across reboots.
For example:
uci set mesh11sd.mesh_params.mesh_hwmp_active_path_timeout='2000'
uci set mesh11sd.mesh_params.mesh_hwmp_preq_min_interval='200'
uci set mesh11sd.mesh_params.mesh_gate_announcements='1'