HELP, i have upgrade my AX3200 RB01 with the last sysupgrade bin (http://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/openwrt-mediatek-mt7622-xiaomi_redmi-router-ax6s-squashfs-sysupgrade.bin) and now the router is bricked without network 
Edit: RESOLVED
I have tftp and pxesrv without success.
And finaly, with the official tools "MIWIFIRepairTool.x86" its return to the original Xiaomi firmware "miwifi_rb01_firmware_36352_1.0.50_INT.bin".
Telnet is still working 
Hi,
so I have 3 of these (RB01) flashed with the 22.03.0-rc1 so what's the best way to mesh these together? Following this https://openwrt.org/docs/guide-user/network/wifi/mesh/80211s guide setting up 802.11s?
this maybe?
Same here, without any idea why this happens or how to reproduce.
Have you tried disabling "Disassociate On Low Acknowledgement" to see if makes any difference?
with these drivers only the mt7615.1.dat is loaded and only 2g network is working. The luci module only shows mt7615.1.dat. Can you share a working mt7615.2.dat and how is the l1profile.dat supposed to look? lsmod shows that both mt_wifi and mt7622_mt_wifi are loaded...
HI. If I have access to Telnet in BR01 can I change the global version to Chinese. And how to do it?
result["mt7615.2.dat"] = "/etc/wireless/mt7615/mt7615.2.dat"
add it here
For the braves who running the SNAPSHOT version of openwrt-22.03 branch ...
A few days ago it got a bunch of backports like Wireless Ethernet Dispatch and a PPPoE fix! 
auc (0.2.5-2)
Server: https://sysupgrade.openwrt.org
Running: 22.03-SNAPSHOT r19316-4c5d2cde13 on mediatek/mt7622 (xiaomi,redmi-router-ax6s)
Available: 22.03-SNAPSHOT r19338-ae64d0624c
Requesting package lists...
...
22.03-SNAPSHOT r19338-ae64d0624c is build from commit ae64d06.
It means these improvements would be in the final release of 22.03.0. 
I'm using 22.03 snapshot (I do my own builds). Right after the ae64d0624c commit I did a new build, and I am running it for 2 days now, without major problems.
However today I had some issues when trying to connect from work to the Wireguard server at home running on OpenWrt. For some reason the connection to the WG server on the AX6S could not be established. After a few minutes I tried again and it worked. I did not have time to troubleshoot, for now I will assume it was some sort of transient internet routing issue and not the new build.
I've had this device up and running for a few days and have struggled to maintain a stable PPPoE connection. Every hour or so (sometimes every few minutes) the WAN connection drops and I get Modem Hangup in the logs. My ISP is BT in the UK on their Fibre 900 (900 down/100 up). I have tried the release candidate version, various snapshot versions and experience the same issue. I am currently running SNAPSHOT r19617-4a8eaa5c7c. I have tried both with and without software and hardware flow offloading as I have read this may be related. I'm wondering if these issues are at all related to those mentioned by xabolcs.
Logs:
Tue May 10 09:46:30 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:46:50 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:47:10 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:47:30 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:47:50 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:47:58 2022 daemon.notice pppd[2969]: Modem hangup
Tue May 10 09:47:58 2022 daemon.info pppd[2969]: Connect time 3.2 minutes.
Tue May 10 09:47:58 2022 daemon.info pppd[2969]: Sent 2670477263 bytes, received 221568772 bytes.
Tue May 10 09:47:58 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:47:58 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:47:58 2022 daemon.err odhcp6c[3023]: Failed to send RS (Network unreachable)
Tue May 10 09:47:58 2022 daemon.err odhcp6c[3023]: Failed to send RELEASE message to ff02::1:2 (Network unreachable)
Tue May 10 09:47:58 2022 daemon.notice netifd: Network device 'pppoe-wan' link is down
Tue May 10 09:47:58 2022 daemon.notice netifd: Network alias 'pppoe-wan' link is down
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Tue May 10 09:47:58 2022 daemon.notice pppd[2969]: Connection terminated.
Tue May 10 09:47:58 2022 daemon.info pppd[2969]: Connect time 3.2 minutes.
Tue May 10 09:47:58 2022 daemon.info pppd[2969]: Sent 2670477263 bytes, received 221568772 bytes.
Tue May 10 09:47:58 2022 daemon.notice netifd: wan6 (3023): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan6" } (Permission denied)
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' has lost the connection
Tue May 10 09:47:58 2022 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Tue May 10 09:47:58 2022 daemon.info pppd[2969]: Exit.
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' is now down
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' is disabled
Tue May 10 09:47:58 2022 kern.info kernel: [ 526.250425] mt7530 mdio-bus:00 wan: Link is Down
Tue May 10 09:47:58 2022 kern.info kernel: [ 526.260029] mt7530 mdio-bus:00 wan: configuring for phy/gmii link mode
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' is enabled
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' is setting up now
Tue May 10 09:47:58 2022 daemon.notice netifd: Network device 'wan' link is down
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue May 10 09:47:58 2022 daemon.err insmod: module is already loaded - slhc
Tue May 10 09:47:58 2022 daemon.err insmod: module is already loaded - ppp_generic
Tue May 10 09:47:58 2022 daemon.err insmod: module is already loaded - pppox
Tue May 10 09:47:58 2022 daemon.err insmod: module is already loaded - pppoe
Tue May 10 09:47:58 2022 daemon.notice netifd: wan (3345): Command failed: ubus call network.interface notify_proto { "action": 1, "command": [ "\/usr\/sbin\/pppd", "nodetach", "ipparam", "wan", "ifname", "pppoe-wan", "lcp-echo-interval", "1", "lcp-echo-failure", "5", "lcp-echo-adaptive", "+ipv6", "nodefaultroute", "usepeerdns", "maxfail", "1", "user", "bthomehub@btinternet.com", "password", "bt", "ip-up-script", "\/lib\/netifd\/ppp-up", "ipv6-up-script", "\/lib\/netifd\/ppp6-up", "ip-down-script", "\/lib\/netifd\/ppp-down", "ipv6-down-script", "\/lib\/netifd\/ppp-down", "mtu", "1492", "mru", "1492", "plugin", "pppoe.so", "nic-wan" ], "interface": "wan" } (Permission denied)
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' is now down
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' is disabled
Tue May 10 09:47:58 2022 daemon.notice netifd: Interface 'wan' is enabled
Tue May 10 09:47:58 2022 kern.info kernel: [ 526.341806] mt7530 mdio-bus:00 wan: configuring for phy/gmii link mode
Tue May 10 09:47:59 2022 daemon.err odhcp6c[3023]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Tue May 10 09:47:59 2022 daemon.notice netifd: Interface 'wan6' is now down
Tue May 10 09:47:59 2022 daemon.notice netifd: Interface 'wan6' is disabled
Tue May 10 09:48:02 2022 daemon.notice netifd: Network device 'wan' link is up
Tue May 10 09:48:02 2022 daemon.notice netifd: Interface 'wan' has link connectivity
Tue May 10 09:48:02 2022 daemon.notice netifd: Interface 'wan' is setting up now
Tue May 10 09:48:02 2022 kern.info kernel: [ 529.953705] mt7530 mdio-bus:00 wan: Link is Up - 1Gbps/Full - flow control off
Tue May 10 09:48:02 2022 kern.info kernel: [ 529.960993] IPv6: ADDRCONF(NETDEV_CHANGE): wan: link becomes ready
Tue May 10 09:48:02 2022 daemon.err insmod: module is already loaded - slhc
Tue May 10 09:48:02 2022 daemon.err insmod: module is already loaded - ppp_generic
Tue May 10 09:48:02 2022 daemon.err insmod: module is already loaded - pppox
Tue May 10 09:48:02 2022 daemon.err insmod: module is already loaded - pppoe
Tue May 10 09:48:02 2022 daemon.info pppd[3446]: Plugin pppoe.so loaded.
Tue May 10 09:48:02 2022 daemon.info pppd[3446]: PPPoE plugin from pppd 2.4.9
Tue May 10 09:48:02 2022 daemon.notice pppd[3446]: pppd 2.4.9 started by root, uid 0
Tue May 10 09:48:02 2022 daemon.info pppd[3446]: PPP session is 4675
Tue May 10 09:48:02 2022 daemon.warn pppd[3446]: Connected to f8:13:08:40:c8:96 via interface wan
Tue May 10 09:48:02 2022 kern.info kernel: [ 530.211458] pppoe-wan: renamed from ppp0
Tue May 10 09:48:02 2022 daemon.info pppd[3446]: Renamed interface ppp0 to pppoe-wan
Tue May 10 09:48:02 2022 daemon.info pppd[3446]: Using interface pppoe-wan
Tue May 10 09:48:02 2022 daemon.notice pppd[3446]: Connect: pppoe-wan <--> wan
Tue May 10 09:48:05 2022 daemon.info pppd[3446]: CHAP authentication succeeded: CHAP authentication success
Tue May 10 09:48:05 2022 daemon.notice pppd[3446]: CHAP authentication succeeded
Tue May 10 09:48:05 2022 daemon.notice pppd[3446]: peer from calling number F8:13:08:40:C8:96 authorized
Tue May 10 09:48:05 2022 daemon.notice pppd[3446]: local LL address REDACTED
Tue May 10 09:48:05 2022 daemon.notice pppd[3446]: remote LL address REDACTED
Tue May 10 09:48:05 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:05 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:05 2022 daemon.notice pppd[3446]: local IP address REDACTED
Tue May 10 09:48:05 2022 daemon.notice pppd[3446]: remote IP address REDACTED
Tue May 10 09:48:05 2022 daemon.notice pppd[3446]: primary DNS address 81.139.56.100
Tue May 10 09:48:05 2022 daemon.notice pppd[3446]: secondary DNS address 81.139.57.100
Tue May 10 09:48:05 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:05 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:05 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:05 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:05 2022 daemon.notice netifd: Network device 'pppoe-wan' link is up
Tue May 10 09:48:05 2022 daemon.notice netifd: Interface 'wan6' is enabled
Tue May 10 09:48:05 2022 daemon.notice netifd: Network alias 'pppoe-wan' link is up
Tue May 10 09:48:05 2022 daemon.notice netifd: Interface 'wan6' has link connectivity
Tue May 10 09:48:05 2022 daemon.notice netifd: Interface 'wan6' is setting up now
Tue May 10 09:48:05 2022 daemon.notice netifd: Interface 'wan' is now up
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using nameserver 81.139.56.100#53
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using nameserver 81.139.57.100#53
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using only locally-known addresses for test
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using only locally-known addresses for local
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Tue May 10 09:48:05 2022 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Tue May 10 09:48:05 2022 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Tue May 10 09:48:05 2022 user.notice firewall: Reloading firewall due to ifupdate of wan (pppoe-wan)
Tue May 10 09:48:10 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:10 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:10 2022 daemon.notice netifd: Interface 'wan6' is now up
Tue May 10 09:48:10 2022 user.notice firewall: Reloading firewall due to ifup of wan6 (pppoe-wan)
Tue May 10 09:48:10 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:48:12 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:12 2022 daemon.warn dnsmasq[1]: failed to create listening socket for REDACTED%pppoe-wan: Address not available
Tue May 10 09:48:30 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:48:50 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:49:10 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Tue May 10 09:49:30 2022 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 0.0.0.0 00:46:a8:02:12:18 wrong server-ID
Any Idea if the 2.4GHz radio is also WiFi 6 compliant? If it is shouldn't the wiki page read b/g/n/ax next to the 2.4GHz?
Wiki is correct. This device supports 802.11ax only on the 5.0GHz band. It does not support 802.11ax on the 2.4GHz band.
It is not. The SoC wifi on the MT7622 is most similar to a single-band MT7615, running on the 2.4ghz band only.
So best you get is bgn. 256-QAM will most likely work too, but you'll need to pull in a couple patches for that to work. (Assuming that both ends even have support)
For 11ax on 2.4ghz + a chonkier CPU, you may want to keep an eye on MT7986, or a router with one of the DBDC 11ax radios. (Although I believe the DBDC version of the MT7915 is 2x2 on both bands, not 4x4?)
Shame. Is there even any OpenWRT supported device that does WiFi6 on 2.4GHz? Other than the BananaPi (MT7986)?
ipq807x does support 802.11ax on 2.4 GHz, but support for that target is still pending.
The new Redmi AX6000 (take apart here) seems a quite good hardware for its price point (CPU MT7986A 4 cores@2GHz, 512MiB RAM, 128 MiB Flash, MT7976GN for 2.4GHz and MT7976AN for 5.0GHz) and it supports 802.11ax (4x4:4) on both bands.
However it is not yet supported by OpenWrt yet. There is already a topic about adding OpenWrt support to this device:
why is the need for AX on the 2.4Ghz? I personally never used 2.4GHz if I'm not forced to like now with Roborock S7 that only supports 2.4GHz, everything on 5GHz, I would personally not pay extra for that and for this silly money this router cost I'm very happy, bought three of them and gave one to my parents and one for backup or incase I need mesh in future but I don't think so as I already have unlimited 4G/5G dataplan so no need for WiFi in every corner. 
Indeed. Rather than looking for 802.11ax on the 2.4GHz band, I would prioritize a router with support to a 6GHz band ("WiFi 6E"). Now back to the topic.... 
I just received AX6S from china to europe no taxes bought from
delivery about 14 days was able to install old firmware and enable telnet so far so good