We are using the GL-INET 300m v2 as a hotspot .
The default firmware onboard is OpenWrt with a layer made by GL-inet, which allows Captive portals to be created with Nodogsplash, not compatible for our purpose.
We have chosen to re-flash the device with standard OpenWrt firmware, allowing coovachilli.
We had to build our own coovachilli package because the default available with opkg doesn’t have the flag --open-ssl and --enable-json, and libjson-c4 has to be added manually, not available on the package manager, required with json enabled.
We also built our own simple luci plugin to add a page where the user can change the coovachilli settings and change the ssid in the wireless config file.
To apply all the changes from the default OpenWrt, we build a sh script that does all these steps automatically (copying the config and the packages, install the required packages, apply change on the networks files).
Our installation process goes like this:
- Install the fresh OpenWrt firmware
- open a terminal and launch the install.sh script
For a few months now, we have an issue on the opkg part, where the hotspot doesn’t have dns by default, and once provided, the opkg still cannot update/install any package, due to ssl or other issues.
A reset button is available on the hotspot device, and clicking on it reset the OpenWrt from scratch, erasing our configuration. Instead, we would like to have, a reset of OpenWrt with our own default settings.
Here is http://bit.ly/3py3YAB our current config applied to the default openwrt, with the config added, the luci-queen module, the 2 packages coova + libjson-c4, the install script with the edit of the dhcp and network config file (at the end).
We would like to get some help so we can successfully achieve the building of our firmware, fixing partially the issue of opkg (hotpot can then be used even if the package manager doesn’t reply), and adding our settings to the default value in case of reset.
I ll be happy to compensate for your time helping me with this.
Here is my email: firstname.lastname@example.org