MediaTek might be affected by the problem and not Qualcomm. As @bluewavenet said it's specific radio hardware.
I've had similar issues both with WDS (on separate SSID) and mesh11sd. I need either one to connect one of my AP's wirelessly (I don't have the possibility to wire it at that location).
After lots of testing it seems to do with the handling of multiple SSID's (which is also needed for 802.11s). This breaks the connection after several hours/days.
I've changed to a setup where the same SSID is used for clients and for the WDS connection to my other AP. Now, my connection is completely stable for about 3 months without any hiccup.
Maybe a driver issue in the support of multiple AP's on the same band?
Just bought 2 of these as currently being driven bonkers by a Now TV 3 router. So few options. Can't even specify DNS, old hacky way was patched.
Components looking great for OpenWRT from what I can see and glad to see very healthy active work on it as a target...and with latest wifi standard etc very handy.
I can see we've got it booting etc from the site. Keen to know what is working and what isn't as my first instinct is to mod these bad boys immediately. Failing which my plan will be to use them as a mesh network, hope they will work with NowTV out of the box but swap them out with the Now TV Broadband 2 router once OpenWRT gets to a stage that it can do what I need (needs Option 61 and MPoA which I'm not sure if they support out of the box but which OpenWRT will support.
Those who've got it running - how reliable is it? What's working what isn't?
Can see it's super hopeful for getting it working perfectly and at that price worth it. Even if it does duty extending the range of my horrid router until we reach a point where I can use it!
Thanks so much all for the hard pioneering work in this thread. You rock!
I am running two of these with OpenWRT 23.05.2 since about 5 months without any problems. Once device is a dumb AP, the other one a wireless bridge. Current uptime is 69 days.
So I would recommend the WSM20, especially if you can catch them at a low price (I think I payed like 80€ for a pack of two).
I’m running two, one as a PPPoE router/WiFi AP and the other as a dumb AP. I have gigabit wired backhaul between them and hardware acceleration enabled.
I reliably get full speed from my ~70Mbps internet connection on wired or wireless. 300-400 Mbps on WiFi to my NAS, and 600ish Mbps on wired, which I think is limited by the NAS CPU doing ssh (iperf shows 900-950Mbps)
Uptime was pushing 100 days but I’ve just updated the firmware. Updating is the only reason I’ve needed to reboot - they’re pretty bomb proof.
I paid £90 for 3. Would definitely buy again.
Hi @timothyjward ,
Have you updated the WiFi AP in the same way as the router?
Perhaps it is a silly question from a beginner, but I have updated my WSM20 router to 23.05.3, but I was wondering if the current settings can be kept for a device that is not configured as a router .... I have a second WSM20 configured as wireless brigde (according to https://openwrt.org/docs/guide-user/network/wifi/connect_client_wifi#connect_to_client_wi-fi_network) : would it be able to update and keep the current settings as wireless bridge, or shall I configured it again as a wireless bridge after the update?
Thank you in advance
Yes. Both followed the normal firmware update process through my web browser, keeping existing config. I've never had a problem with the upgrade process, but I don't have anything particularly complex configured so I'm not a particularly interesting test case.
Thank you @timothyjward
I will proceed with the wireless bridge
Is it possible to repartition this device to have more space in the openwrt?
We never use the second firmware location (sysupgrade always installs to first partition) and app
partition is also not used.
I would love to have ~110MB free space especially because this device doesn't have usb and can't do extroot.
I've search, but i can't do yet.
16 posts were split to a new topic: Issue after installing OpenWrt on Zyxel Multy M1
So, my wife keeps complaining about the port LED's on the back. "They're flashing too bright"....
Does anyone know if there's a way to make them a lot brighter and annoy my wife a little more disable them? The front LEDs were quite easy to disable, but the rear LED's... I can't seem to find any reference of them.
These commands only work for the front LED's:
# Disable
# for p in `find /sys/devices/platform/leds/leds -name trigger` ; do echo none > $p ; done ; for p in `find /sys/devices/platform/leds/leds -name brightness` ; do echo 0 > $p ; done
# Enable
# for p in `find /sys/devices/platform/leds/leds -name trigger` ; do echo none > $p ; done ; for p in `find /sys/devices/platform/leds/leds -name brightness` ; do echo 1 > $p ; done
-edit-
I've also found something about the /etc/rc.button/lights_toggle
switch. It's supposed to be able to be sensed by GPIO, right? I'd love to be able to hook the switch to those LED's, without soldering.
Latest snapshot seems to have put my Multy into a boot loop. Starts , green light for about 30-40 seconds and then repeat.
Reset button doesn't seem to have an effect, nor can I trigger failsafe.
Any suggestions before I break out the ttl dongle and crack it open?
I’m afraid that there’s nothing left, other than connecting a console. It’s the only way to see what’s going on and why it’s in boot loop.
Latest SNAPSHOT has switched from opkg to apk, not building properly.
Worth switching to 24.10-SNAPSHOT while you wait for apk to fully populated.