Mostly works, noticed that VPN client devices Wireguard or OpenVPN do not appear to have access to the Beryl LAN devices even of that option is set,
tcpdump can now be installed and runs correctly, good work, thankyou
what is the deal with DNS proxy in 4.1.0 beta 2, is it worth trying to connect dnsCrypt ?
Its a middleman, a protocol that encrypts, authenticates and optionally anonymizes communications between a DNS client and a DNS resolver. It prevents DNS spoofing. It uses cryptographic signatures to verify that responses originate from the chosen DNS resolver and haven’t been tampered with.
It is an open specification, with free and open source reference implementations, and it is not affiliated with any company nor organization.
Free, DNSCrypt-enabled resolvers are available all over the world.
I do not work for and I am not directly associated with GL.iNet 
2 Likes
yeah baby yeah, you should work for GL inet!
can anyone from GL inet advise if DNS proxy is working in Beta 2 firnware ? Has this been tested ?
Thanks for confirming my good Sir.
Well, I had not time to try this beta until now…
I upgraded from 3.215 to 4.1.0 beta 2 and I it seems my wifi completely died… I used Uboot to revert to 3.215 and Wifi still isn’t working, this is what I have on log:
Wed Sep 21 03:54:56 2022 daemon.notice netifd: mt7615e2 (3704): drv_mtk_teardown mt7615e2...
Wed Sep 21 03:54:56 2022 daemon.notice netifd: mt7615e5 (3705): drv_mtk_teardown mt7615e5...
Wed Sep 21 03:54:56 2022 daemon.notice netifd: mt7615e5 (3705): vif down ra0...
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.904525] FWCmdTimeout: command (1), ext_cmd_type (0), seq(6), timeout(3000ms)
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.911964] pAd->Flags = 0x11002000
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.915690] txq qlen = 0
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.918248] rxq qlen = 0
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.920828] kickq qlen = 0
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.923622] ackq qlen = 1
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.926382] tx_doneq.qlen = 0
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.929370] rx_done qlen = 0
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.932251] AndesSendCmdMsg: msg state = 8
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.936403] msg->retry_times = 0
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.939633] /home/glinet/work/openwrt-19.07.5/build_dir/target-mipsel_24kc_musl/linux-ramips_mt7621/mt7615-5.1.0.0/mt_wifi_ap/../mt_wifi/embedded/mcu/andes_core.c:887 assert FALSEfailed
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.956203] CPU: 0 PID: 3482 Comm: ifconfig Not tainted 4.14.241 #0
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.962462] Stack : 00000000 8edd0e40 8f712a14 8007351c 80610000 805a198c 00000000 00000000
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.970808] 8056b22c 8bf65a5c 8fd16fdc 805e09e7 80565fc0 00000001 8bf65a00 ac07f5e8
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.979144] 00000000 00000000 80740000 000070d8 00000000 000001bd 00000007 00000000
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.987477] 00000000 805e0000 000e972b 00000000 80000000 80600000 00000000 c13eedcc
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 43.995808] 8cfd9f80 c13eed94 c13eedb4 8edd0e40 00000002 802c48a0 00000000 80740000
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.004139] ...
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.006576] Call Trace:
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.009047] [<8000c7b0>] show_stack+0x58/0x100
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.013489] [<8049ee14>] dump_stack+0xa4/0xe0
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.019091] [<8d14e828>] AndesSendCmdMsg+0x830/0x9a8 [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.025633] [<8d163708>] MtCmdAddressLenReq+0xf4/0x1ac [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.032318] [<8d16aa28>] MtCmdSendNullFrame+0xaa4/0x2194 [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.039192] [<8d16c930>] mt_load_fw+0x158/0x2a4 [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.045284] [<8d08f9f8>] WfMcuInit+0x1e8/0x2c8 [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.051260] [<8d08fc6c>] WfInit+0xbc/0x234 [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.056917] [<8d1118a8>] mt_wifi_init+0x274/0x66c [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.063165] [<8d1e5964>] mt_wifi_open+0x140/0x1b4 [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.069421] [<8d1e5a24>] virtual_if_init_handler+0x4c/0xc0 [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.076460] [<8d095cec>] RTMP_COM_IoctlHandle+0x810/0x11f0 [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.083476] [<8d1e4ff4>] main_virtual_if_open+0xc4/0x1cc [mt_wifi]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.089999] [<8037d614>] __dev_open+0xdc/0x14c
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.094429] [<8037d95c>] __dev_change_flags+0xe8/0x1ac
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.099543] [<8037da48>] dev_change_flags+0x28/0x70
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.104417] [<803ff34c>] devinet_ioctl+0x2f8/0x890
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.109213] [<80358800>] sock_ioctl+0x300/0x35c
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.113730] [<8013f6cc>] do_vfs_ioctl+0x780/0x81c
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.118413] [<8013f7b8>] SyS_ioctl+0x50/0x98
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.122681] [<80016578>] syscall_common+0x34/0x58
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.127711] Start address = 0x209c400, DL length = 48336, Data mode = 0x80000009
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.135149] MtCmdAddressLenReq:(ret = 1)
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.139087] load_fw_v1: load fw fail
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.142656] mt_load_fw: fw download fail
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.146621] WfMcuHwInit: NICLoadFirmware failed, Status[=0x00000001]
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.157272] fw_own()::Set Fw Own
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.160535] WfInit(): initial faild!! ret=1
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.164811] WfInit faild!!, ret=1, cap=8f712818
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.169617] <---HwCtrlThread
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.173196] !!! mt_wifi_init fail !!!
Wed Sep 21 03:54:56 2022 kern.warn kernel: [ 44.177060] RTMP_COM_IoctlHandle -> CMD_RTPRIV_IOCTL_VIRTUAL_INF_UP
This error is much like due to power adapter. I have a power adapter causing wifi fails and it has this error.
Can you pls change one power adapter?
Just tried with Slate Plus & Slate AX power adapters, I still have this log:
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.057497] /home/glinet/work/openwrt-19.07.5/build_dir/target-mipsel_24kc_musl/linux-ramips_mt7621/mt7615-5.1.0.0/mt_wifi_ap/../mt_wifi/embedded/mcu/andes_core.c:887 assert FALSEfailed
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.074011] CPU: 0 PID: 3843 Comm: ifconfig Not tainted 4.14.241 #0
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.080255] Stack : 00000000 8cadfcc0 8cc70a14 8007351c 80610000 805a198c 00000000 00000000
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.088613] 8056b22c 8ca3fa5c 8b50e97c 805e09e7 80565fc0 00000001 8ca3fa00 ac07f5e8
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.096971] 00000000 00000000 80740000 0000b0d8 00000000 000002e3 00000007 00000000
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.105326] 00000000 805e0000 0001211b 00000000 80000000 80600000 00000000 c13eedcc
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.113681] 8bf37680 c13eed94 c13eedb4 8cadfcc0 00000002 802c48a0 00000000 80740000
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.122037] ...
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.124482] Call Trace:
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.126970] [<8000c7b0>] show_stack+0x58/0x100
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.131426] [<8049ee14>] dump_stack+0xa4/0xe0
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.137350] [<8d14e828>] AndesSendCmdMsg+0x830/0x9a8 [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.144341] [<8d163708>] MtCmdAddressLenReq+0xf4/0x1ac [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.151459] [<8d16aa28>] MtCmdSendNullFrame+0xaa4/0x2194 [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.158780] [<8d16c930>] mt_load_fw+0x158/0x2a4 [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.165574] [<8d08f9f8>] WfMcuInit+0x1e8/0x2c8 [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.171994] [<8d08fc6c>] WfInit+0xbc/0x234 [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.178104] [<8d1118a8>] mt_wifi_init+0x274/0x66c [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.184822] [<8d1e5964>] mt_wifi_open+0x140/0x1b4 [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.191499] [<8d1e5a24>] virtual_if_init_handler+0x4c/0xc0 [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.198976] [<8d095cec>] RTMP_COM_IoctlHandle+0x810/0x11f0 [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.206460] [<8d1e4ff4>] main_virtual_if_open+0xc4/0x1cc [mt_wifi]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.213204] [<8037d614>] __dev_open+0xdc/0x14c
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.217646] [<8037d95c>] __dev_change_flags+0xe8/0x1ac
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.222770] [<8037da48>] dev_change_flags+0x28/0x70
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.227663] [<803ff34c>] devinet_ioctl+0x2f8/0x890
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.232478] [<80358800>] sock_ioctl+0x300/0x35c
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.237011] [<8013f6cc>] do_vfs_ioctl+0x780/0x81c
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.241704] [<8013f7b8>] SyS_ioctl+0x50/0x98
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.245992] [<80016578>] syscall_common+0x34/0x58
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.251085] Start address = 0x209c400, DL length = 48336, Data mode = 0x80000009
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.258570] MtCmdAddressLenReq:(ret = 1)
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.262544] load_fw_v1: load fw fail
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.266203] mt_load_fw: fw download fail
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.270151] WfMcuHwInit: NICLoadFirmware failed, Status[=0x00000001]
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.282012] fw_own()::Set Fw Own
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.285413] WfInit(): initial faild!! ret=1
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.289644] WfInit faild!!, ret=1, cap=8cc70818
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.294404] <---HwCtrlThread
Wed Sep 21 03:55:38 2022 kern.warn kernel: [ 59.297744] !!! mt_wifi_init fail !!!
I am asking developer to have a check. Seems the radio burned.
@Max3 can you return the device back to me to investigate?
3 Likes
yes, of course I’ll send it back 
2 Likes
@alzhao if i use multi-wan on beryl 4.1 beta 2 i see DNS TLS packets port 853 cloudflare on WAN and no TLS google 8.8.4.4 on the TETHERING, which is set to priority 1 and failover is WAN. DNS is set to TLS cloudflare obviously. Not sure how the firmware handles DNS on muti-wan, thanks,
if i look at traffic graphs in luci, muti wan seems to be using priority 1 link for download and seems to be working correctly,failover data wasnt being used. just not sure about DNS. thanks
Can you test a setting, for the android TETHERING link, does setting a custom DNS server and setting TLS pass back to Beryl router ? i havent tried for the above, if so, can you inform the server to set on android. thanks.
DNS does not failover. You can use encrypted dns so that it stick to your settings.
Note: I’m running my rounter 24/7 in Repeater mode. This is a pretty random bug but two days in a row now I’ve had to reboot the router otherwise the Chromecast thinks it’s not on the same network as my phone. I had zero issues for two weeks. Then I moved to a new timezone and connected to a different Wifi for my Repeater. That’s when the Chromecast connections issue started. Easily could be totally random, but thought I should mention it… 
And yes, I tried all the usual Chromecast fixes first, but despite it showing as being on my network, it being connected in the “Client” list, I could not connect to it.
The only other thing I did each time before rebooting was delete the Chromecast from the Clients list in the router. No idea if that matters. If / when it happens again I’ll do better troubleshooting and just reboot first 
, then remove it from the Clients list and reboot again if it still doesn’t work.
You mean on firmware 4.1 right?
Yes, sorry, I’m running v4.1 Beta 2. I never tried Beta 1. I had no issue when I was on v3 for a week (I only just got the router last month).
Also, since I installed v4.1 Beta 2 I can no longer connect my Chromecast on to 5Ghz Wifi. It worked fine on v3. Not sure that matters, but thought I should mention it too.
A new issue for me, that just started yesterday. The router is struggling to hold a connection. It’s regularly going offline while trying to reconnect to the repeater. I have no custom settings, no VPN setup, only change I made recently (two days ago) was switching to Quad9 for DNS. From the logs…
Fri Nov 4 09:34:14 2022 daemon.info repeater: (/usr/sbin/repeater:372) IFNAME=wlan-sta0 <3>CTRL-EVENT-SCAN-STARTED
Fri Nov 4 09:34:18 2022 daemon.info repeater: (/usr/sbin/repeater:372) IFNAME=wlan-sta0 <3>CTRL-EVENT-SCAN-RESULTS
Fri Nov 4 09:35:41 2022 daemon.notice wpa_supplicant[2404]: wlan-sta0: WPA: Group rekeying completed with d4:35:1d:9c:d7:16 [GTK=CCMP]
Fri Nov 4 09:35:41 2022 daemon.info repeater: (/usr/sbin/repeater:372) IFNAME=wlan-sta0 <3>WPA: Group rekeying completed with d4:35:1d:9c:d7:16 [GTK=CCMP]
Fri Nov 4 09:36:45 2022 daemon.notice wpa_supplicant[2404]: wlan-sta0: WNM: Disassociation Imminent - Disassociation Timer 6000
Fri Nov 4 09:36:45 2022 daemon.notice wpa_supplicant[2404]: wlan-sta0: WNM: Preferred List Available
Fri Nov 4 09:36:45 2022 daemon.info repeater: (/usr/sbin/repeater:372) IFNAME=wlan-sta0 <3>WNM: Disassociation Imminent - Disassociation Timer 6000
Fri Nov 4 09:36:45 2022 daemon.info repeater: (/usr/sbin/repeater:372) IFNAME=wlan-sta0 <3>WNM: Preferred List Available
Fri Nov 4 09:36:45 2022 daemon.info repeater: (/usr/sbin/repeater:372) IFNAME=wlan-sta0 <3>CTRL-EVENT-SCAN-STARTED
Fri Nov 4 09:36:45 2022 daemon.info repeater: (/usr/sbin/repeater:372) IFNAME=wlan-sta0 <3>CTRL-EVENT-SCAN-RESULTS
Fri Nov 4 09:36:46 2022 daemon.notice netifd: Network device 'wlan-sta0' link is down
Fri Nov 4 09:36:46 2022 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Fri Nov 4 09:36:46 2022 kern.info kernel: [ 853.544216] wlan-sta0: deauthenticated from d4:35:1d:9c:d7:16 (Reason: 2=PREV_AUTH_NOT_VALID)
Fri Nov 4 09:36:46 2022 daemon.notice netifd: wwan (8898): udhcpc: received SIGTERM
Fri Nov 4 09:36:46 2022 daemon.notice netifd: wwan (8898): udhcpc: unicasting a release of 192.168.0.50 to 192.168.0.1
Fri Nov 4 09:36:46 2022 daemon.notice netifd: wwan (8898): udhcpc: sending release
Fri Nov 4 09:36:46 2022 daemon.notice netifd: wwan (8898): udhcpc: entering released state
Fri Nov 4 09:36:46 2022 daemon.notice netifd: wwan (8898): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wwan" } (Permission denied)
Fri Nov 4 09:36:46 2022 daemon.notice netifd: Interface 'wwan' is now down
Fri Nov 4 09:36:46 2022 daemon.notice netifd: Interface 'wwan' is disabled
Fri Nov 4 09:36:46 2022 daemon.notice netifd: Interface 'wwan' is enabled
I can confirm this issue, when I was away for work in a hotel it struggled to keep a connection in repeater mode. V3 has no such issue.