Skip to content

Bandlocking on GoldenOrb reverts to old settings #9

Description

@Dude4Linux

I have a ZBT-WG3526 (16M) with a Sierra Wireless MC7411 modem running the latest stable release of GoldenOrb 2023-08-03.
Since the initial installation, I've been struggling to get the Bandlocking feature of the GUI to work properly. Any changes made to the selected bands are reverted back to the original bands after the modem is reset. Originally, I thought that it was due to the MC7411 not being fully supported. I found that the correct commands were being issued, but the settings weren't permanent. I know the AT commands are correct, because they work when I enter them one at a time at the AT-Command Terminal.

Eventually I noticed the following error in the system logs:

Sat Jan 13 10:16:36 2024 user.notice Lock Band 1: AT!BAND=11,"Test",0,0,42,0,0,0
Sat Jan 13 10:16:36 2024 daemon.err uhttpd[3879]: /usr/lib/rooter/luci/lock.sh: line 338: 0: not found
Sat Jan 13 10:16:39 2024 user.notice Lock Band 1: AT!BAND=00;!BAND=11 OK

**Examining line 338 of lock.sh, we see the following:

if "$flg" = "0" ]; then

which looks like a malformed If statement. After replacing the line with the correct syntax, the bandlocking GUI works as expected.

if [ "$flg" = "0" ]; then

I was unable to find a way to patch the GoldenOrb firmware, so I resorted to the tempory fix by adding the following lines to /etc/rc.local

# Fix Bandlocking
sed -i 's/if "$flg" = "0" ]/if [ "$flg" = "0" ]/' /usr/lib/rooter/luci/lock.sh

This appears to survive a reboot.

**Note the line number has changed to 345 in the current ROOTer Source

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions