Workaround:
echo -e "local function valid_macaddr(v)\n return true\nend\n\nreturn {\n connect = {\n ssid = '.+',\n key = '.+',\n identity = '.+',\n macaddr = valid_macaddr\n },\n remove_saved_ap = {\n ssid = '.+'\n }\n}" > /usr/share/gl-validator.d/repeater.lua
Means the AXT1800 / AX1800?
Due to the kernel update, many plugins packages that no longer apply were removed from the repo.
If you need any plugins packages, please give us feedback.
We tried to compile the corresponding plugins packages. Thank you.
The plugin nano:
htop_nano.zip (188.9 KB)
I installed the beta on my AXT1800 and I will test it in the coming days as my main router with a 1Gb symmetric fiber connection. Thank you for the firmware and thank you for the nano and htop!
I noticed that there is a process that execute every minute called aw_arp_scan ang give me strange errors in the log so I disabled it from cron. What is the purpose of this arp scan? Do it need to be executed so often?
Again thank you for your work!
@Alisa the issue about the missing packages I've experienced on all 4.7: Brume2, Beryl AX, and SlateAX-beta
EDIT - I think my memory is off. I'm working on a Brume2 4.7 now and do see nano still. It might have just been a SlateAX-beta
Thank you
I believe there might be something wrong specifically with your setup. I have upgrade a few devices now tp 4.7 (21 and 24) and none have had this issue you mention. But specifically I know python3-speedtest-cli is present on these as I have installed on 3 separate routers now. Are you certain DNS resolution is working properly? Is something else blocking access (pi-hole, adguard, firewall)?
@Alisa @bruce - Going back through my notes it appears the issues were specific to a customer running the 4.7 beta on a AX1800 (Flint1) and AXT1800 (SlateAX). I've not had the issues on other customer Mediatek based routers yesterday or today running non-beta 4.7 (e.g. Brume, Beryl, etc).
I assume the package @bruce provided will resolve the issues for any more customers running beta 4.7 on these specific models. Thank you very much!
@packetmonkey fyi
I see a lot of this:
kern.warn kernel: [51250.069517] ath11k c000000.wifi: ath11k_nss: unable to free peer mem, peer_id:22
kern.warn kernel: [51255.148827] ath11k c000000.wifi: timeout while waiting for nss peer delete msg response
Probably it is related to the AsrtoWarp feature. Did the router enable it?
What are the errors in the syslog?
Since one of the AsrtoWarp features is bind the clients into the tunnel network, and it use the arp to scan and find if new clients join/connect the router network in real time. It is normal.
If it brings some unknown questions to users, we try to optimize this log content.
Please add the interface name for the custom-added Wi-Fi radio on the /etc/config/wireless:
5GHz is 'wlan 1-2', 2.4GHz is 'wlan0-2'.
Where is the openwrt 24 version?
It said something about something not found probably because Astrowarp was not enabled and the scritp checked something that it was not there. I see it call the function get_arp_scan_ret() every 1 minute then call gl-arp-scan so may be calling this only if AstroWarp is in use could be a good thing also because is every 1 minute. I will put it on again and note the exact error it gives in the log.
cron.err crond[4295]: USER root pid 9222 cmd . /lib/functions/mptun.sh; get_arp_scan_ret
cron.err crond[4295]: USER root pid 9476 cmd . /lib/functions/mptun.sh; get_arp_scan_ret
cron.err crond[4295]: USER root pid 9921 cmd . /lib/functions/mptun.sh; get_arp_scan_ret
cron.err crond[4295]: USER root pid 10369 cmd . /lib/functions/mptun.sh; get_arp_scan_ret
cron.err crond[4295]: USER root pid 10817 cmd . /lib/functions/mptun.sh; get_arp_scan_ret
It go on like this forever. it do not seems even an error, is like is not doing anything and exit since there is very few things to do in my case.
Pretty sure only official stable builds are offered, hence why you didn't see the beta as available.
Thanks for your comment...
What I'm used to w/companies that offer a beta program (which I have accepted, per setting below) w/OTA updates is that I will get offered the current beta via their normal "Upgrade" process. To me the point of a setting like below is that I can get the latest beta via the quicker "Upgrade" process and not have to do a manual download/local install.
Not a huge deal, just wanted to share as it was different than expected for me. 
Sorry, I overlooked that message in your screenshot. I agree with you, you should probably be offered the beta. Maybe it just takes a while to sync up. I'm sure one of the Devs can answer / confirm for us.
Good day @bruce !
Are the recent proprietary MTK patches included in new builds such as beta 4.7.4 for MT6000 since it is using a close source driver? Thanks!
I successfully installed 4.7.0 on my Slate AX, but need package tcpproxy and any dependencies please!
Is there a fix for the slow wifi speeds on the flint 2? I have 1gb fibre I only get 100mb on the flint 2 when I try the flint 1 I get 1gb speeds..
