not entirely normal. Mine looked like this in the beginning (chinese firmware) as well. But now (after installing robimarkos firmware) it looks like this (not that I did anything about it willingly...):
I recompiled my firmware with ath10k small buffer and manually cut ath11k buffers in half (4096->2048).
Only two days, but so far running stable with 80-160MB free RAM.
I have opened this topic about a roaming issue I have: moving clients hang with no apparent reason when roaming.
Maybe it is not a config issue but a "not implemented in this firmware" yet issue?
I managed to get OpenWRT on the device after having some minor difficulties. But now I can't get WiFi to bridge with LAN if my life depends on it.
I can connect to the AP, but I can't get any traffic in or out. I do have VLAN enabled on the bridged interface, is that supported or is bridging WLAN to LAN in general unsupported?
root@ap2:/etc/config# cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd61:056e:c75a::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1'
list ports 'eth2'
list ports 'eth3'
option igmp_snooping '1'
config interface 'lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option device 'br-lan.1'
option metric '1'
option ipaddr '10.0.0.7'
option gateway '10.0.0.3'
list dns '10.0.0.4'
list dns_search 'xxx'
config device
option name 'eth0'
config bridge-vlan
option device 'br-lan'
option vlan '1'
list ports 'eth1'
list ports 'eth2'
list ports 'eth3'
config bridge-vlan
option device 'br-lan'
option vlan '10'
list ports 'eth1:t'
config interface 'IOT'
option proto 'static'
option device 'br-lan.10'
option ipaddr '10.0.10.4'
option netmask '255.255.255.0'
option gateway '10.0.10.2'
option metric '2'
option type 'bridge'
config device
option name 'br-lan.1'
option type '8021q'
option ifname 'br-lan'
option vid '1'
option ipv6 '0'
config device
option name 'br-lan.10'
option type '8021q'
option ifname 'br-lan'
option vid '10'
option ipv6 '0'
I dont know how to configure vlan in openwrt, but you can see a mostly working config of bridged lan/wlan without vlan in the link in my previous post. Maybe it helps?
I hooked it up to my network, and made a connection to the AP. Not getting a lease from my DHCP... Manually set my IP allowed me to connect to the AP directly via both the webUI and SSH. The AP itself is able to connect to the rest of the world:
root@OpenWrt:/etc/config# traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 46 byte packets
1 router.home.cannonfodder.nl (10.0.0.3) 0.522 ms 0.475 ms 0.410 ms
2 192.168.1.1 (192.168.1.1) 1.321 ms 1.159 ms 1.042 ms
3 1-200-201-31.ftth.glasoperator.nl (31.201.200.1) 5.949 ms 6.320 ms 8.158 ms
4 one.one.one.one (1.1.1.1) 6.541 ms 6.722 ms 7.066 ms
Restarting the lan-interface using the webUI makes it magically work... Disconnecting and re-connecting to the WiFi AP breaks it again, until restarting the lan-interface... Once it does work it also at random breaks again.
❯ ping 10.0.0.3
PING 10.0.0.3 (10.0.0.3): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
# Restart of lan-interface
ping: sendto: No route to host
Request timeout for icmp_seq 4
ping: sendto: Host is down
Request timeout for icmp_seq 5
ping: sendto: Host is down
[...]
Request timeout for icmp_seq 21
ping: sendto: Host is down
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
64 bytes from 10.0.0.3: icmp_seq=24 ttl=64 time=3.227 ms
64 bytes from 10.0.0.3: icmp_seq=25 ttl=64 time=3.292 ms
ping: sendto: No route to host
ping: sendto: No route to host
Request timeout for icmp_seq 26
ping: sendto: No route to host
Yup, DHCP is provided by an OpenWRT instance running inside a container on my edge node.
The most frustrating part is, I'm not new to OpenWRT. I have 1 containerized instance, another Xiaomi AC2100 AP, and two Netgear switches with OpenWRT. Why can't I get this to work, ugh
after first compile (to have a build_dir) ...
* menuconfig -> kernel modules -> wireless -> ath10k small buffers
* build_dir/toolchain-aarch64_cortex-a53_gcc-8.4.0_musl/linux-5.10.46/drivers/net/wireless/ath/ath11k/hw.h(67): #define ATH11K_QUEUE_LEN 2048 (from 4096)
do you know (could you tell me) how to make a proper patch out of this #define?
FYI: I did not exactly verify in source what difference changing ATH11K_QUEUE_LEN makes for memory allocation. It just looked promising at first and second glance and my (not so statistically relevant) test on two devices looked promising.
Strange enough, the AP that does not run the DHCP/DNS and has less attached stations uses a bit more memory on average. Go figure...
It could... it appears to be relatively stable now all of a sudden, but especially:
the AX3600 configured as a dumb AP where sometimes WLAN clients can't get any access to LAN for the first few minutes after they associate
Sounds highly plausible. Once I experience it again, I'll use my Android phone with ever changing MAC-address to connect to the AP and check if it's able to connect right away.
Guys i have an importand question, i have this Router and i am totally dissapointed by its firmware which seems to have been stucked for 10 months in this 3.0.22 buggy as hell version (no port forwarding on lan, pihole is not working at all with it i, FTL service shut down due to huge trafic caused by the buggy xiaomi factory firmware!) and i am sure Xiaomi will not ever fix them, especially the pihole issues (i am sure they want eliminate pihole usability) So i am asking : will it ever get a custom firmware like any other Router loaded by the web interface without all those downgrades and extreme dangerous solutions? or to sell it to someone who want it for just simple jobs? Thank you
I've seen some odd temporary blockages too, but didn't imagine they were AX3600-specific - rather maybe a bug in SNAPSHOT, my setup, or ath11k driver snapshot in general.
I have AX3600 #1 in a cupboard acting as a WAN router, DHCP server, plugged into a wired NAS and having a 5GHz (ath11k) WDS master linking to AX3600 #2 in the living area with all the actual wireless clients. This setup worked OK on Archer C7s for years.
All LAN & WLAN segments are simply bridged in br-lan.
I've definitely seen situations where a wireless client on AP #2 can't ping the NAS, but can ping the AP #1 and access the WAN OK. In this situation, remaining connected to AP #2, I've ssh'd to AP #1, then ssh'd to the NAS and the instant I ping the wireless client from the NAS everything starts working and remains good. I'm no expert, but it seems that ARP broadcast/response is failing.
Most of the time it all works OK even from cold boot. This doesn't seem to be a static trunking/bridge configuration issue.
