[Feature Request] RTTY/SSH access within GL GUI
2 Likes
Re: Since firmware 4.6+, WireGuard & DDNS
The WireGuard watch dog script from WireGuard Extras hasnât been tested?
# SPDX-License-Identifier: GPL-2.0
#
# Copyright (C) 2018 Aleksandr V. Piskunov <aleksandr.v.piskunov@gmail.com>.
# Copyright (C) 2015-2018 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
#
# This watchdog script tries to re-resolve hostnames for inactive WireGuard peers.
# Use it for peers with a frequently changing dynamic IP.
# persistent_keepalive must be set, recommended value is 25 seconds.
#
# Run this script from cron every minute:
# echo '* * * * * /usr/bin/wireguard_watchdog' >> /etc/crontabs/root
1 Like
This feature is under development and will be released in beta within this month if things go well.
2 Likes
Feature request - Band Masking:
- allow band masking (OPEN or BLOCK) of WCDMA bands
This is a very small issue, but on my Spitz AX, the is no ability to either OPEN or BLOCK the WCDMA bands (only LTE, 5G NSA, and 5G SA bands are listed).
2 Likes
That strikes me as more of a bug than a feature request. One would expect the ability to lock down ea. individual of the set, no?
Feature request - Tailscale for Opal (GL-SFT1200)
- It is capable of running WireGuard, therefore it is capable of running Tailscale. Sadly its architecture is ruining everything
Please donât artificially limit devices.
1 Like
FYI: Tailscale is still in beta on the current stable 4.2.1-release4. âUpgrade to 4.x firmware for older products. (Beta versions of most models will be coming soon)â is stated to be released for v 4.6 so presumably that includes the Opal.
I tried to build it myself but failed pretty quickly, seems the Siflower/Sichang architecture is a bit different from regular MIPS so the binary wonât run. I really hope nobody pulls an âoh, this device is too old for us now, we donât want to support itâ kind of move. The beta is available for the Opal, just not tailscale, sadly.
Well good news, it seems! GL mentioned just 5 hours ago theyâre building a 4.x for the Mango (GL-MT300N)⌠which was released, what, around 2017?:
⌠which is striking given whatâs listed on
Great then! Still not the biggest fan of openwrt being seemingly stuck on 18.06 for my Opal, but I guess itâs fine as long as GL keeps updating it with patches and such
Then youâll be happy to know GL f/w 4.2.1-release4, the current stable, is based on OpenWrt 21.02-SNAPSHOT. Their version 4.3 is mentioned to be based on owrt 22.0x.
They seem to be once release behind Upstream. I can live with that. YMMV.
Well, Iâm currently on 4.3.2-beta1, itâs still 18.06. Seems like the version scheme doesnât entirely correlate with OpenWRT releases haha
1 Like
Huh; well then⌠I guess thatâs what I get for making an assumption of myself. I am corrected.
Hey, check this out fr GL re: Mango firmware:
The Mango is an MTK7620-based device, very well supported by even the official branch of OpenWRT. The SiFlower/SiChang SoC the Opal uses might as well be completely proprietary, there is an SDK but nobody really knows how to use it. Except GL.
As for Tailscale, itâs not looking good by GLâs vague response of âhardware limitationsâ. This is a very generic write-off. And I doubt itâs truly hardware limited, rather itâs limited because Golang wont directly compile for it 
Damn; when you put it like that⌠the news re: Mangoâs age & f/w still being developed for it isnât as exciting give the circumstances w/ Opal.
Well, it ainât Tailscale but are you up to self hosting/VPS hosting an install of Firezone?
simple one add Watchcat within the interface, so wifi reboots if no internet
âHardware limitationsâ say what? Now I have to figure out how to compress it. UPX seems to make it segfault.
Some relevant info might be here, 19.07-related: