Adding OpenWrt support for Xiaomi AX3600 (Part 1)

It's not clear to me who is the router or how it is connected to what?
Do you use ax3600 as a wired AP?
Maybe you have more than one DHCP server in your LAN.

Hello sqrwv when i configure first time ax3600 as AP and activate wifi radio 0 and radio 1 all working good. When i reboot the ax3600 and try to connect to wifi or ping the router from a wired computer of the network cant .

I configure it as AP . the main modem of ISP have the dhcp of the whole network with 192.168.1. 1.

The ax3600 as AP set at 192.168.1.254. with no dhcp at v4 or v6.

My problem is that when i configure for first time the wifi working well . When i restart the router and try to login after 10 mins the router went down. I see the ssid. But i cant connect to them.

Finally come around to replace my asus ac-56u MIPS, installed robimarko on AX3600, setup vlan, static ip's, ect. But cannot really get vpn working, both openwrt and wireqguard require kmod packages that are not douns in py packages list (even after update) does robimarko build not support VPN ?

Please read this thread first, that question has been answered numerous times. The prebuilt images only contain a very basic configuration + webinterface/ luci, anything beyond that is not prebuilt - while you can add many userspace applications 'by chance' (as there are other ARMv8 targets building those for OpenWrt), you're out of luck as soon as you need any kernel modules (by definition, as the dependencies between the running kernel and its modules are even stricter than 'just' the target, which doesn't even exist in OpenWrt yet).

tl;dr: if you need any kernel modules, you will have to build the firmware from source yourself, based on robimarko's trees and enabling/ statically including your desired additions.

I have two AX3600 configured as dumb APs and they always worked well.

Did you disabled ax3600 DHCP server here :
Network->Interfaces->Lan->Edit->DHCP Server->General Setup
enable this option: Ignore interface

Please see in you wifi client/device what IP and gateway did he got when he can't connect.

Also if you enable a MAC filter allow only list in wifi, remember some devices use random MACs.

1 Like

Thanks,

isnt there a compiled image with OpenVPN or Wireguard kernel modules here somewhere ? I dont have the skills to do it myself :frowning:

In that case the current state of ipq807x support for OpenWrt doesn't meet your requirements and you should (have chosen-) a different device.

i guess ill setup vpn server to some other device in the network for the mean while then

Masking what you did as "open discussion" is a nice trick, but you fool no one. You rant and insult developers, that is what you did, just to be clear.

"this is openwrt not robimarko openwrt"

"why you are so protective"

and such. And when you got an answer, instead of stopping you go on and on. His code is public, fork it, make it better, create PRs on your own so other can take a look and judge your code quality for example. That is opensoiurce, and not you ranting about how someone else should do anything about the code he created, especially if you cant add anything valuable to it.

6 Likes

There is a lot of builds with custom configurations. https://github.com/rodriguezst/ipq807x-openwrt-builder/network/members. You can select one or build your own, only select one and learn how they did it. It is very easy and you can customize the build.

1 Like

can't help about other things that could go wrong, just the obvious: have you triple checked the line pc-tx -> router-rx?

It's not even the first time he's doing this.

He deleted his posts after but the guy clearly got some issues..

Iirc the original posts were like robi's firmware is shit and nothing was working for him etc

I found the reason for poor roaming in the 2.4GHz network, on the stock firmware. Judging by the logs, 802.11k only works on a 5GHz network, and on a 2.4GHz network it works with errors. In the logs, the upper part of the 5GHz network, it is clear that information about two access points and their signal is sent to the client. Checked on two devices, the situation is the same. the problem is in the firmware.

2022-04-22T22:24:31+08:00 XiaoQiang miwifi-roam[7162]: stamonRSSIObserver(150):A4:6B:D6:3A:38:CC on APId 255 ChanId 36  ESSId 0  meet ap steering
2022-04-22T22:24:31+08:00 XiaoQiang miwifi-roam[7162]: estimatorPerform11kMeasurement(736):Initiated 11k measurement for A4:6B:D6:3A:38:CC from serving BSS APId 255 ChanId 36  ESSId 0  
2022-04-22T22:24:32+08:00 XiaoQiang miwifi-roam[7162]: wlanifEventsHandleBeaconReport(296):Beacon report from A4:6B:D6:3A:38:CC: APId 1   ChanId 36  ESSId 0   rcpi: -47 bssid: 64:64:9A:5C:BD:AC
2022-04-22T22:24:32+08:00 XiaoQiang miwifi-roam[7162]: wlanifEventsHandleBeaconReport(296):Beacon report from A4:6B:D6:3A:38:CC: APId 255 ChanId 36  ESSId 0   rcpi: -61 bssid: 64:64:9A:5C:C1:DC
2022-04-22T22:24:32+08:00 XiaoQiang miwifi-roam[7162]: steeralgAPSteerCallback(561):APId 1   ChanId 36  ESSId 0  metric b500ff00 band 1 hop 0 rate 1201 rcpi -47
2022-04-22T22:24:32+08:00 XiaoQiang miwifi-roam[7162]: steerexecStartSteer(1092):Starting new steer for A4:6B:D6:3A:38:CC(transaction 0)
2022-04-22T22:24:32+08:00 XiaoQiang miwifi-roam[7162]: steerexecStartSteer(1099):index 0 candidate bssid 64:64:9A:5C:BD:AC
2022-04-22T22:24:32+08:00 XiaoQiang miwifi-roam[7162]: wlanifEventsHandleWNMEvent(370):Received BTM Response from A4:6B:D6:3A:38:CC: Dialog Token: 0, Status: 0, Reject: 7, BSS termination delay: 0, Target BSSID 64:64:9A:5C:BD:AC
2022-04-22T22:24:32+08:00 XiaoQiang miwifi-roam[7162]: steerexecHandleResponseBSSID(675):Received successful BTM response from A4:6B:D6:3A:38:CC BSSID 64:64:9A:5C:BD:AC (transaction 0)
2022-04-22T22:24:32+08:00 XiaoQiang miwifi-roam[7162]: steerexecSteerEndBTMNotSure(1564):BTM steering A4:6B:D6:3A:38:CC is complete (transaction 0)

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2022-04-22T22:27:36+08:00 XiaoQiang miwifi-roam[7162]: stamonRSSIObserver(150):A4:6B:D6:3A:38:CC on APId 255 ChanId 1   ESSId 1  meet ap steering
2022-04-22T22:27:36+08:00 XiaoQiang miwifi-roam[7162]: estimatorPerform11kMeasurement(736):Initiated 11k measurement for A4:6B:D6:3A:38:CC from serving BSS APId 255 ChanId 1   ESSId 1  
2022-04-22T22:27:37+08:00 XiaoQiang miwifi-roam[7162]: wlanifEventsHandleBeaconReport(271):Beacon report BSSID 00:00:00:00:00:00 doesn't match any BSS
2022-04-22T22:27:37+08:00 XiaoQiang miwifi-roam[7162]: estimatorStoreBeaconReportEvent(390):Invalid beacon report for A4:6B:D6:3A:38:CC
2022-04-22T22:27:37+08:00 XiaoQiang miwifi-roam[7162]: wlanifEventsHandleBeaconReport(271):Beacon report BSSID 00:00:00:00:00:00 doesn't match any BSS
2022-04-22T22:27:37+08:00 XiaoQiang miwifi-roam[7162]: estimatorHandleBeaconReportEvent(451):Beacon report for STA A4:6B:D6:3A:38:CC in unexpected state 0
2022-04-22T22:27:41+08:00 XiaoQiang miwifi-roam[7162]: stamonRSSIObserver(150):A4:6B:D6:3A:38:CC on APId 255 ChanId 1   ESSId 1  meet ap steering
2022-04-22T22:27:41+08:00 XiaoQiang miwifi-roam[7162]: estimatorPerform11kMeasurement(736):Initiated 11k measurement for A4:6B:D6:3A:38:CC from serving BSS APId 255 ChanId 1   ESSId 1  
2022-04-22T22:27:42+08:00 XiaoQiang miwifi-roam[7162]: wlanifEventsHandleBeaconReport(271):Beacon report BSSID 00:00:00:00:00:00 doesn't match any BSS
2022-04-22T22:27:42+08:00 XiaoQiang miwifi-roam[7162]: estimatorStoreBeaconReportEvent(390):Invalid beacon report for A4:6B:D6:3A:38:CC
2 Likes

Thanks for your replay! I don't know i rechecked everything and it's looks ok!
Could be the reason of poor usb?

I got these too with latest build. Do you have same ssid or separated bands? On my side it happens suddenly, 2 android devices

I work a lot with USB-to-serial devices and they themselves were never the reason I had problems (although nothing is impossible, maybe you fryed the input, does it work with another device, like an Arduino, Raspberry, ESP, STM chips, ...). Reason #1: rx/tx lines switched (not your problem, since it works one way). Reason #2 (if on windows): driver not working properly (not your problem, same reason). Reason #3: connection bad (dupont wires or similar easily break or don't make good enough contact, since you checked: probably ok) so I'm out of options, uboot isn't my domain...

I can confirm this...
But because all visible networks around me are using other channels I never thought it was an issue.

Could be because of this:
https://openwrt.org/inbox/toh/xiaomi/xiaomi_ax3600#notes1

But now you can't ssh to xiaomi FW to type those commands.
Also you can't input/type into uboot, it looks like TX is locked.
From what I read you can TFTP recover only xiaomi fw, but that crashes because you have the wrong partition size.
Doesn't look good, you need to search if anyone got out of that situation.

EDIT:
You can test your USB TTL adapter TX and RX:
Configure 1.8V jumper, put a jumper connecting Tx to Rx, connect USB to computer but not to the router.
Use a serial terminal (putty), everything you type on it should come back to the terminal, because Tx is conencted to Rx. Just in case remove the jumper and see that you can no longer see the echo of what you type.

Another thing to try, jumper the router's RX & TX together and power up. The boot delay countdown should provide the 'any key' it's looking for. If that fails then it sounds like uart_en hasn't been enabled or has subsequently been disabled again.

When doing this, you can keep the router's TX connected to your USB RX (but leave the USB TX disconnected) to monitor the process.

2 Likes

@robimarko @Ansuel @quarky
Maybe I'm wrong, but it looks like QCA is not using the UBI cores anymore for network accelleration with the new major target IPQ95xx (Alder)

They disable NSS accelleration

They indroduced a qca-nss-ecm-nonss kernel package without the qca-nss-drv dependency, instead it's using kmod-qca-nss-sfe

Additionally there is an ecm wifi plugin:

And there are a lot of commits lately in the sfe repo:

Maybe they really want to "revive" sfe .....and maybe there is a way we can adapt this to ipq806x/ipq807x (I'm not sure if there is a hard dependency to the ipq95xx target)

3 Likes