Also in current repository don't have Midnight Commander, it's not super important for me. But would be nice to have it. Or maybe I can use some other repos?
Atm I would try to make it from the sources.
P.s. my router is AXT1800.
Same issue here.. after a few hours the led was blinking.. and the AXT1800 was becoming unreachable. It was not the case with the release candidate. (RC7).
One of my favourite apps, I use it on every linux system I have, SBC to Desktop
I successfully found these packages the next day, not sure what was the issue. Thank you!
4.7 release 8 also has again problems with dnscrypt dns not founding any certificate after router is switched off. That was present in the beta, got solved in the release 7 and is again present in release 8.
Question regarding custom AT commands: I would like to edit the gl-sdk4-ui-modemmanage.common.js.gz file to add the ability to quickly use 4G mode as well as other module modes without having to enter them manually in the Custom AT Command box or enabling band masking. Can you please let me how I can update this file using the latest firmware? I've already updated the file but it is not being loaded.
Again,
The ability for me to edit the gl-sdk4-ui-modemmanage.common.js.gz no longer works in v4.7.4 but it did in v4.4.13. Please allow the system to be able to read the settings from the /www/views/ folder again or add the ability to add a custom setting and save it to the dropdown list.
@bruce Is this something that will be added in a future release or something I can do in the current 4.7.4 release? Enabling Band Masking works but it distrups my connection wheras setting AT Commands is pretty much instantanious.
Hello,
Please let me know how to reproduce this issue.
I tested on my AX1800 with 4.7.0 release8, the DNScrypt is normally after the router rebooted.
HI, yes after reboot is normally OK, the issue happen if you switch off the router the you switch it on again. I usually switch it off on Saturday and switch it on on Sunday morning just to have a fresh start once a week. Then after switching it on it complains about missing server certificates and it is not able to connect to any of my configured dnscrypt servers that are:
server_names = ["dnscry.pt-madrid-ipv4","dnscry.pt-lisbon-ipv4","dnscry.pt-geneva-ipv4","dnscry.pt-london-ipv4"]
This happen with 4.7.0 beta and final version. With RC release 7 version this do not happen.
If when it happen I reset the router and load the configuration again still dnscrypt do not work.
Please install this package, get it on /www/views/gl-sdk4-ui-modemmanage.common.js.gz
web-modemmanage_20250415.42112-1_aarch64_cortex-a53.zip (15.4 KB)
- unzip, and upload the .ipk file to
/root/
of X/XE3000 opkg install web-modemmanage_20250415.42112-1_aarch64_cortex-a53.ipk
unfortunately, this did not work for me. I uploaded the .ipk file to /root/ and ran the opkg command and this is what I got for a return:
Installing web-modemmanage (20250415.42112-1) to root...
Collected errors:
- check_data_file_clashes: Package web-modemmanage wants to install file /usr/share/oui/menu.d/modemmanage.json
But that file is already provided by package * gl-sdk4-ui-modemmanage - check_data_file_clashes: Package web-modemmanage wants to install file /www/views/gl-sdk4-ui-modemmanage.common.js.gz
But that file is already provided by package * gl-sdk4-ui-modemmanage - opkg_install_cmd: Cannot install package web-modemmanage.
I then re-ran the command using --force-overwrite and the package installed successfully.
However, I have made changes to the gl-sdk4-ui-modemmanage.common.js.gz file and they are not showing up in the shortcut dropdown list of the UI.
Any other suggestions?
Update:
Add a URL in step 3
Please install this package, get it on /www/views/gl-sdk4-ui-modemmanage.common.js.gz
web-modemmanage_20250415.42112-1_aarch64_cortex-a53.zip (15.4 KB)
- unzip, and upload the .ipk file to
/root/
of X/XE3000 opkg install web-modemmanage_20250415.42112-1_aarch64_cortex-a53.ipk
- After the web-modemmanage.js.gz is changed, please access this URL to use the customize AT commands (please login first): http://192.168.8.1/#/modemmanage
That URL works! My custom AT commands now show up using that URL but not from the main internet dropdown/popover page, which is fine for now but obviously will need to be looked at. I appreciate your help in this matter.
Hi, I am new here and use the 4.7.2 beta1 version, file SFT1200 1227, how to now which release it is ?
I had some bug (?) acceleration enabled by default and then disabled, and Anti DNS rebinding enabled by me, then disabled.
There is no 4.7.2 for GL-SFT1200
Check here
I am sorry but the latest release 4.7.4 is crap.
I have a Brume2 connected to a GL-M2 via a 4-port USB Hub. With 4.7.0 it only worked with a manual modfication of the library by the gl.inet staff.
This configuration worked excellent without any issues.
Now that it was confirmed that with release 4.7.4 no manual modifications should be necessary I upgraded and at first it seemed to work fine.
However after a few hours the problems started: The BRUME could no longer enumerate the GL-M2 and only a cold start could make it work but only again for several hours.
Brume looses the connection on and on and without unplugging the GL-M2 and replugging nothing works.
Even worse: Tethering doesn't work at all which drives me nuts.
I start to get annoyed about GL.Inet since this starts to be a kind of nerd toy instead of a reliable system.
For reference please see below protocol extract regarding the GL-M2.
Sun Apr 20 22:08:05 2025 kern.info kernel: [ 163.218656] usb 1-1.1: new high-speed USB device number 9 using xhci-mtk
Sun Apr 20 22:08:05 2025 kern.err kernel: [ 163.326651] usb 1-1.1: device descriptor read/64, error -71
Sun Apr 20 22:08:05 2025 kern.info kernel: [ 163.332231] usb 1-1.1: Device No Respond
Sun Apr 20 22:08:06 2025 kern.err kernel: [ 163.778585] usb 1-1.1: device descriptor read/64, error -71
Sun Apr 20 22:08:06 2025 kern.info kernel: [ 163.784163] usb 1-1.1: Device No Respond
Sun Apr 20 22:08:06 2025 kern.info kernel: [ 163.998534] usb 1-1.1: new high-speed USB device number 10 using xhci-mtk
Sun Apr 20 22:08:06 2025 kern.err kernel: [ 164.106534] usb 1-1.1: device descriptor read/64, error -71
Sun Apr 20 22:08:06 2025 kern.info kernel: [ 164.112109] usb 1-1.1: Device No Respond
Sun Apr 20 22:08:06 2025 kern.err kernel: [ 164.326506] usb 1-1.1: device descriptor read/64, error -71
Sun Apr 20 22:08:06 2025 kern.info kernel: [ 164.332081] usb 1-1.1: Device No Respond
Sun Apr 20 22:08:06 2025 kern.info kernel: [ 164.442722] usb 1-1-port1: attempt power cycle
Sun Apr 20 22:08:07 2025 kern.info kernel: [ 165.098365] usb 1-1.1: new high-speed USB device number 11 using xhci-mtk
Sun Apr 20 22:08:07 2025 kern.warn kernel: [ 165.105204] usb 1-1.1: Device not responding to setup address.
Sun Apr 20 22:08:07 2025 kern.warn kernel: [ 165.318364] usb 1-1.1: Device not responding to setup address.
Sun Apr 20 22:08:07 2025 kern.err kernel: [ 165.530293] usb 1-1.1: device not accepting address 11, error -71
Sun Apr 20 22:08:07 2025 kern.info kernel: [ 165.638277] usb 1-1.1: new high-speed USB device number 12 using xhci-mtk
Sun Apr 20 22:08:07 2025 kern.warn kernel: [ 165.645093] usb 1-1.1: Device not responding to setup address.
Sun Apr 20 22:08:08 2025 kern.warn kernel: [ 165.858276] usb 1-1.1: Device not responding to setup address.
Sun Apr 20 22:08:08 2025 kern.err kernel: [ 166.070219] usb 1-1.1: device not accepting address 12, error -71
Sun Apr 20 22:08:08 2025 kern.err kernel: [ 166.076561] usb 1-1-port1: unable to enumerate USB device
Check here GL.iNet download center
How do you managed to install it 7 days ago while it was released 3 days ago?
I tried it on XE-300 with
https://fw.gl-inet.com/firmware/xe300/testing/openwrt-xe300-4.7.2-0417-1744871549.tar
while eSIM manager worked (I was able to add a new profile there), it was unable to connect with 4G with eSIM from EIOTCLUB. The interface was telling that it was a 2G connection, but no data were delivered. Also, pinging the gateway was taking almost 30 seconds to get an answer.
Switching back to 4.3.23 beta restored the connection to 4G.
Also, the sim manager on 4.3.23 looked a little bit better, properly showing the available limits of the eSIM card that were already provided by the EIOTCLUB card.
How to know which version it is : file with 1227 in its file name (for december 27)