hi
i already set 00, why i still missing channel list?
21.02 release uses a DSA driver that no longer uses the swconfig. You bind interfaces if you want to use VLANs i.e. eth0.1 = Vlan 1, eth0.2 = Vlan 2 etc
So the luci interface will no longer show the switch setting.
In the shell of the router, type 'iw list'
If you are seeing
- 5260 MHz [52] (20.0 dBm) (radar detection)
Possible the DFS is kicking in and avoiding those channels.
Remember its a regulatory standard, so even if you want a certain channel, the chipset will prevent it from the EEPROM reading it has established.
This (luci being incompatible with DSA) might be the reason for Spotify no longer finding my Echo devices to cast to or for not seeing my Sonos devices after upgrading to 21.02.0-rc4.
Maybe it is blocking Broadcast or Multicast.
How can I fix it on CLI?
When will luci be working again?
UPDATE: rebooting fixes the problem for a few minutes, then my Echos are gone again 
How long does it take? Your issue could be this, Xiaomi Wifi R3P pro - 19.07.x / Permanent Wifi clients unreachable after 1 day - Installing and Using OpenWrt / Network and Wireless Configuration - OpenWrt Forum
Same with vanilla openwrt and @db260179 builds. I can't reach my local devices after sometime, contantly pinging the ip's brings them back up for some reason. I don't have this issue with official firmware.
Echo devices most likely use SSDP for discovery. You will need to use avahi and or udp-proxy for discovery to work reliably. A wireless network will block multicast traffic - look at the openwrt docs on this subject.
luci is just a web interface language, nothing to do with your issues. And by design for the new version of openwrt 21.02 that the DSA driver no longer has a switch config area in luci.
Look at the official docs explains the change.
Why would I need avahi or udp-proxy when all devices are on the same LAN-bridge. Some are conneced on lan and some on wlan, yes - but I expect the device to bridge and convert mutlicast automatically.
With the snapshots earliert than 21.02. RC3 discovering the echo-devices from spotify did work just fine. What has changed?
I remember that there was a bug with igmp-forwarding in the mt76xx-switch-chip from one lan port to another and one had to put each of them in a separate vlan and bridge them together. Could the problem be related to this issue?
All you can do is set the wireless to auto channel (give a few minutes to find a good channel), country to your country code and leave at that.
if your wireless disconnects, use wireless-schedule in the repo to start and stop the wireless when not needed or a custom script to monitor connection and restart if need be.
I would report this issue to the openwrt github repo, as its RC release there will be issue or mistakes from the dev team, im just a contributer nothing more.
1 Like
Ok noted
Now is showing all channel
Thanks
Problem does not occur on TL-WPA8630Pv1 which is QCA-based running 21.02.0RC4, so the problem seems to be MT7xxx related.
Maybe it is due to the lack of igmp-snopping support in hardware of the MT7530-switch? See (1) and (2)]
1 Like
have you already tried?
option disassoc_low_ack '0'
(option is also available in Luci, in the wifi advanced tab)
As explained at IGMP Snooping and DSA - #4 by LGA1150 , IGMP-snooping now works with DSA on MT7530 aka Mi Router 4G's Switch.
The question remains: why is the discovery of Alexa devices now broken?
UPDATE:
The problem was related to a broken umdns-daemon in connection with seccomp.
I discovered the root cause when my dawn-daemon couldn't see other dawn-nodes on the same network.
Errormessage was: daemon.err dawn[x]: Failed to look up test object for umdns
The workaround listed on https://bugs.openwrt.org/index.php?do=details&task_id=3355 works:
cd /etc/seccomp
mv umdns.json umdns1.json
sync
/etc/init.d/umdns restart
After applying the fix to my Mi Router 4a Gigabit Edition and rebooting the router, my Echo-speakers were visible in Spotify again and the Sonos-app found the Sonos-speakers again.
Can I update to [Updated to v19.07.8 stable release upstream] https://gitlab.com/db260179/xiaomi-m4a/-/releases from version snapshot acecilia?
You can downgrade from snapshot versions, but config will not be preserved and will get a warning when attempting to upgrade - you will need to force upgrade, but take a note of config you have, as you will need to manually change again.
Hi guys,
is wireguard working fine for you on v19.07.8? For me it's not working - it cannot send back packets, handshake cannot complete. Previously it was fine...
It seems this is fixed in RC3, I saw another user mention it. Currently happy with it.