Sorry, it is not final release version.
It is a error, 4.1.0 should not be in stable. This is the cause for us to test 3.216 by upgrading to version 4.x online. It will be removed later.
Ouch. Ok. We I’m running beta3 and so far so good. 
1 Like
In the meantime I have remote access. Unfortunately, switching on-off the wifi does not work. Also rebooting the wifi does not work. Clients disconnected for whatever reason and I do not find any other way to reconnect them remotely than rebooting the router 
Is there still movement in the development?
2 Likes
Installed Beta 3, no problems for now.
Using Wireguard VPN and Adblock in OpenWrt Luci. Tethering on iPhone is working.
the gui for mwan3 in the section Multi-wan is nice. Still missing the future request to make this visable on the homescreen. Like a checkmark witch connection is used. and on loadbalancing all are checked.
Beryl uses openwrt 22.03 so the progress is more delayed. Recent snapshot 4.2 will address some issues with VPN policy and will be released not long.
1 Like
Appreciate all the input here, alzhao.
I’ve been seeing the same “wifi radio is damaged” errors as dmurphy in dmesg on my Beryl unit running most recent firmware. What’s the best route to support and help you debug this issue? Happy to provide any necessary logs.
Also, is it possible for me to receive a replacement device as well? This one has become unusable.
Anyone tried the 4.2 snapshot build? Any show stoppers?
Maybe just get an replacement first. Just send email to support at glinet.biz
Will do. Thanks for your help!
Noticed that when you click on a connection on the homescreen, you’ll get to the matching page. (in my example, the page for multi-wan). So this works.
Installed snapshot 4.2 Only thing not working is the side button. I use it for my VPN. Works on beta 3.
Hi. I have a MT1300 Beryl. Installed 4.1.0b3. I don’t have any wireless interfaces coming up at all. Looking at the logs I see that radio0 appears down. The log shows me restarting the device in luci. Does anyone have any suggestions to progress or diagnose further? I should add that I am tethered through the router at the moment, so that works. I’ve tried both types of reset too:
Sat Feb 25 20:12:53 2023 daemon.info repeater: (/usr/sbin/repeater:1307) wait radio ‘radio0’ to be ready
Sat Feb 25 20:12:54 2023 daemon.notice netifd: radio0 (2255): sh: acs_survey: out of range
Sat Feb 25 20:12:54 2023 daemon.notice netifd: radio0 (2255): sh: acs_survey: out of range
Sat Feb 25 20:12:54 2023 daemon.info repeater: (/usr/sbin/repeater:1307) wait radio ‘radio0’ to be ready
Sat Feb 25 20:12:55 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) → new PHY
Sat Feb 25 20:12:55 2023 daemon.err hostapd: Could not set interface wlan0 flags (UP): I/O error
Sat Feb 25 20:12:55 2023 daemon.err hostapd: nl80211: Could not set interface ‘wlan0’ UP
Sat Feb 25 20:12:55 2023 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Sat Feb 25 20:12:55 2023 daemon.err hostapd: nl80211 driver initialization failed.
Sat Feb 25 20:12:55 2023 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Sat Feb 25 20:12:55 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn’t started
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): Command failed: ubus call hostapd config_add {“iface”:“wlan0”, “config”:“/var/run/hostapd-phy0.conf”} (Invalid argument)
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): Usage: ubus [] [arguments…]
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): Options:
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): -s : Set the unix domain socket to connect to
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): -t : Set the timeout (in seconds) for a command to complete
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): -S: Use simplified output (for scripts)
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): -v: More verbose output
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): -m : (for monitor): include a specific message type
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): (can be used more than once)
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): -M <r|t> (for monitor): only capture received or transmitted traffic
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255):
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): Commands:
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): - list [] List objects
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): - call [] Call an object method
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): - subscribe […] Subscribe to object(s) notifications
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): - listen […] Listen for events
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): - send [] Send an event
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): - wait_for […] Wait for multiple objects to appear on ubus
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): - monitor Monitor ubus traffic
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255):
Sat Feb 25 20:12:55 2023 daemon.notice netifd: radio0 (2255): Device setup failed: HOSTAPD_START_FAILED
Sat Feb 25 20:12:55 2023 daemon.notice netifd: Wireless device ‘radio0’ set retry=0
Sat Feb 25 20:12:55 2023 daemon.crit netifd: Wireless device ‘radio0’ setup failed, retry=0
Sat Feb 25 20:12:55 2023 daemon.notice netifd: Wireless device ‘radio0’ is now down
Sat Feb 25 20:12:55 2023 daemon.info repeater: (/usr/sbin/repeater:1307) wait radio ‘radio0’ to be ready
Sat Feb 25 20:12:56 2023 daemon.info repeater: (/usr/sbin/repeater:1307) wait radio ‘radio0’ to be ready
Sat Feb 25 20:12:57 2023 daemon.info repeater: (/usr/sbin/repeater:1307) wait radio ‘radio0’ to be ready
If you kept settings pls do a firmware set.
If still have this issues, then it seems that radio is damaged.
Thanks for getting back to me on this. I’ve reflashed the 4.1.0b3 firmware using uboot and unfortunately no change. Looks like the radio is dead unfortunately.
Does the latest MT3000 BerylAX use the same radio hardware? I might buy one if I can find one on the road here
Hardware are always the same.
Upgraded 4.2.0 snapshot on MT1300 but didn’t see the parental control and zerotier option. Is it not supported on MT1300 model. any idea?
Was answered earlier in the post
Thanks for the continuing support of this model, hope we can have the 4.2 firmware available soon!
I’ve given up on my beryl. Wish I’d researched more. It’s slow and unstable. Ordered a Slate Plus, hopefully more stable with the Qualcomm processor.
1 Like