The BE3600 comes with a number of third-party packages pre-installed. Some of these I will never use as I have no use for them, and so I'd like to remove them from both the device and the UI. I just like a tidy working environment
I notice from Applications->Plug-ins that Tailscale (for example) is installed and is presented with an "uninstall" button:
Clicking the very inviting "uninstall" button results in the following failure message:
Collected errors:
print_dependents_warning: Package tailscale is depended upon by packages:
print_dependents_warning: gl-sdk4-tailscale
print_dependents_warning: These might cease to work if package tailscale is removed.
print_dependents_warning: Force removal of this package with --force-depends.
print_dependents_warning: Force removal of this package and its dependents
print_dependents_warning: with --force-removal-of-dependent-packages.
Clicking on the "tailscale" link back on the Plug-ins, confirming the removal of dependencies and clicking on the uninstall button results in the same error above.
Obviously, logging into the device as root, identifying the packages, then removing them and finally restarting the UI results in the package removal from the UI:
root@GL-BE3600:~# opkg list-installed | grep -Ei 'tailscale'
gl-sdk4-tailscale - git-2025.115.14079-8810705-1
gl-sdk4-ui-tailscaleview - git-2025.021.39013-acb38d8-1
tailscale - 1.66.4-1
root@GL-BE3600:~# opkg remove --autoremove \
> gl-sdk4-tailscale \
> gl-sdk4-ui-tailscaleview \
> tailscale
Removing package gl-sdk4-tailscale from root...
coreutils-timeout was autoinstalled and is now orphaned, removing.
Removing package coreutils-timeout from root...
coreutils was autoinstalled and is now orphaned, removing.
Removing package coreutils from root...
Removing package gl-sdk4-ui-tailscaleview from root...
Removing package tailscale from root...
Updating database.
Database update completed.
root@GL-BE3600:~# /etc/init.d/uhttpd restart
root@GL-BE3600:~#
Is the removal of this "optional" package not actually supported?
Are the generated errors bugs?
Since I've had to use root to remove the packages, have I angered the GL-iNet deities/pixies and will suffer their wrath when I'm stranded halfway up a mountain and I need to email my dog back at home but can't because my BE3600 is mysteriously somehow bricked?
Thanks for taking the time to reply - I really appreciate it.
I should have also added that I was using the same firmware (v4.7.3), and that any superfluous software is removable without errors via LuCI (System->Software)
I don't see the point. That's a travel router. If you want addition space then configure opkg to install to a USB drive. I don't think it's worth the effort to save a few MB & potientually brick your device when you can easily have multiple GB.
If it were a home router I'd just say dump the GL.iNet GUI & flash pure OpenWrt if you can accept any potiental bandwidth decrease(s).
In this instance, it's not about clawing back those few scraps of MBs; it's about clearing away some of the stuff/junk/bloat/clutter/telemetry that appears on the UI that I know I will never use. For me, it's tidy and UI ergonomics. If they weren't on the UI, then I probably would have left them alone until such a point where I felt the need to scrounge around for a few more MBs.
Just a point of order: the closest thing I've seen to telemetry from GL.iNet is related to pinging their update server to notify of new firmware releases. That may have changed since the v4.6 series but they seem to have enough on their hands already before totally nuking their reputation for VPN/privacy-oriented devices. I say that after scanning days worth of .pcaps via tcpdump with WireShark. tcpdump should be available in the default GL.iNet opkg feeds.
Well, I'll put it like this. 'Domino', the (old? -- it may have changed in the years since) GL.iNet Web GUI on these routers make use of a custom API & even more scripts that aren't compatible with stock/'pure' OWRT. For example:
If your primary motivation is for a web GUI you can work with, I'd just flash pure OWRT. You'd be giving up Domino, GL.iNet support, and, as stated probably take a noticeable performance hit on at least the VPN-side of things if not Wi-Fi. The Qualcomm SDK for these SBCs aren't open source. It's not just OWRT GL.iNet builds on.
I hear 'Argon' is a pretty popular theme but I don't chase trends though I get a custom dashboard is always nice. I need my travel router to work so I can work. If you're going to get all 'experimental' with yours be sure to read up on how U-boot works in the GL.iNet online docs so you can recovery in a worst case scenario. For lesser scenarios you'll probably want this:
But before you fawk around and find out you might be interested in this:
As you say, to each their own... & it's your kit. Just make sure you have an escape hatch if/when things start going belly up.
