OpenWrt for Zyxel WSM20 (Multy M1) development discussion

No, I just contribute to the project (mostly new device support), I'm not part of the developer team.

Ah, ok. But "even" as a contributor you might be able to advise me?

are they not the leds on the ethernet interface?

There are LEDs on the back of the router, integrated into the RJ45 jacks.

1 Like

how is the WiFi coverage / performance of these boxes ? Is it comparable to R7800. I'm planning to replace my three R7800 ( Dumb AP in AC mode only )

Well that will obviously depend on your deployment and lots of other factors.

I find it to be good in my extremely noisy urban environment (15-20 visible SSIDs) over a 3 floor house with brick walls using two APs and wired backhaul. Lots of devices (20+) across 2.4G and 5G. Real world WiFi transfer speeds over 300Mbps in most of the house (not just in the rooms with an AP).

Your mileage may vary. -> 69 € this dayème-AX1800-Maison/dp/B0BCWM7BBC/ref=sr_1_17_sspa?__mk_fr_FR=ÅMÅŽÕÑ&crid=1RWX14ECXWTQU&keywords=zyxel&qid=1697014134&sprefix=zyxel%2Caps%2C93&sr=8-17-spons&ufe=app_do%3Aamzn1.fos.2a4964d5-da8d-479b-a739-01ef3fadb618&sp_csd=d2lkZ2V0TmFtZT1zcF9tdGY&psc=1

1 Like

Seriously - how are they making any money on these?

My router, which works as a bridge, stops broadcasting if the main network disappears. It's normal? But this is not good for me.


1 Like

Thanks , WSM20 has 2 ranges. I've set up transmission 2.4 -> 5 GHz and after that everything works!


Sorry for the late reply: I have no clue on that. These LEDs have been added not long ago and at the moment there is no way to configure them in the .dts (which would be the appropriate place). A similar question has been asked some time ago, with no answers.

1 Like


can we get confirmation that the current (final 23.05.0, not yet officially released) release ( works here, so that we can update ?


Two devices are running fine for me with 23.05.0 (and since the fixed MT76 WiFi driver was merged into the RCs of 23.05)


I can confirm now as well that installing the new 23.05.0 release worked. However, contrary to information on, no cloud registration is strictly necessary to access the initial firmware upload page Reports about this is already in this thread: OpenWrt for Zyxel WSM20 (Multy M1) development discussion - #630 by ghen. I could access it even without long-pressing reset, like this: I unpacked the fresh unit from its box and attached it only to my laptop via lan-port. That laptop was not connected to the Internet as well, so there was no Internet connection at all. As described, shows a page that essentially tells you to wait until connection with the Internet would be established and trying redirected to the main page. I left the unit in this state for a while. I do not know for how long exactly, but probably about on hour or so. Some time in that timeframe, the unit must have hit a timeout, because after that time, while http:/ stills showed the waiting info, the direct link worked, without ever connecting to the Internet. Using this and the procedure described at I could first flash the openwrt initramfs image and later the full image - without any need for an Internet connection. If there will be no objections here, I will describe this procedure on later as well.

Something else that I found curious is: do we know what system the the OEM firmware actually is? I read here that the GPL source is supposed to be available (OpenWrt for Zyxel WSM20 (Multy M1) development discussion - #659 by Annick), but I could not find a repo or download of said code. Could it please be made available? There should not be any reason against it if it is GPL.

The reason I am asking is that I noticed that with still the OEM firmware running as it came out of the box, the unit redirects https traffic to the http port, and for that it uses a certificate that looks like this (note the common name (CN) "Openwrt"):

        Version: 3 (0x2)
        Serial Number:
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C = DE, ST = Berlin, L = Berlin, CN = OpenWrt
            Not Before: Nov  5 03:55:29 2021 GMT
            Not After : Nov  5 03:55:29 2023 GMT
        Subject: C = DE, ST = Berlin, L = Berlin, CN = OpenWrt
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Subject Key Identifier: 
            X509v3 Authority Key Identifier: 
            X509v3 Basic Constraints: 
    Signature Algorithm: sha256WithRSAEncryption
    Signature Value:

Of course, this being a self-signed certificate, anyone could create a certificate with that CN, but why would Zyxel use a ssl-certificate with a common name "Openwrt", unless their stock firmware is/was some variation of Openwrt?

You can request the GPL drop from ZyXEL and they will send you a download link.

Yes, it's some variation of OpenWrt, just scroll to the beginning of this thread and read the first few hundred posts where we tried to get into the stock firmware.

When setting up my first WSM20 (of a 3-pack, great deal btw, tks for the links!), I have mistakenly accepted the suggestion to update the firmware. Now it seems impossible to access the firmware upgrade link, as it always redirects to the login page. With the other two devices this was not an issue. Waiting for over 1 hour, disconnecting from WAN or any other attempts also did not work.

Anyone faced a similar issue and would know what to do in this case?

The attempt after making the post did work.

  1. Reset the router (I pressed the button for pretty long). This brings the wifi setup back to factory default
  2. Connect to the factory default wifi (I was previously connected over LAN cable, this did not work)
  3. Open the setup page of the router, which asks for connecting the WAN. Connect the WAN and let it finish the initial setup
  4. After this, the firmware page could be accessed again.

Here some information I came across (V1.00(ABZF.5)C0.pdf), concerning differences between OEM firmware versions. I am not sure if it ever might come in handy. The only interesting thing I see so far is the the firmware upgrade page we use to flash OpenWRT was only added in version V1.00(ABZF.1)C0. For me, that was the version my devices came with. But it would mean also that there might be devices with older firmware (ABZF.0), for which this might not work, at least not before upgrading the stock FW.

(The rest ist copy & paste from the PDF file. Note that the given date for V1.00(ABZF.5)C0: 07/03/2022 might be a typo and actually mean 07/03/2023, given that the file date is 07/10/2023 (a week later, but in 2023) and Zyxel itself currently shows a 100ABZF5C0 "End-User License Agreement" file from the exact same date in 2023 on - but with a broken link.)

V1.00(ABZF.0)C0: 08/31/2021
[Initial Version]

V1.00(ABZF.1)C0: 11/15/2021


  1. Update DUT's root password process for root access of the device.
  2. Add debug firmware upgrade page and remove SSH remote.

Bugs fixed:

  1. Notifications cannot work fine.
  2. In Diagnose/Mesh page, Multy name should show user-defined name
  3. Home > Multy Router > enable IPv6, then IPv6 page not display WAN IP and
    LAN IP
  4. Install as stand alone, the wireless clients not show in Parental control page
  5. If Controller is in bridge mode. then Agent not show detail information in GUI
  6. After Device reboot, New client notification will inform to APP again.

V1.00(ABZF.2)C0: 02/21/2022

Bugs fixed:

  1. Fix Power LED and Wireless LED non reason blinking.
  2. Change System Name and Domain Name, agent LED is blinking and cannot
    connect controller.
  3. Change WiFi setting and agent sometimes cannot connect to controller.
  4. After Agent associate to Controller via WPS, Agent reboot without log
  5. DUAL Stack+IPv6 LAN End number less than Start number "Apply" should not
    be accepted
  6. Use GUI install M1 then Multy Android APP open IPv6 that LAN address will
  7. Parental Control add same profile name and fail to change profile
  8. APP can not delete "off-line" client from client list
  9. If Agent uplink is down, then Agent LED is not blinking for WPS downlink

V1.00(ABZF.3)C0: 03/31/2022


  1. Support IGMPv3

V1.00(ABZF.4)C0: 05/12/2022


  1. Support Mesh uplink information
  2. Support External Guest function
  3. OpenSSL vulnerability update 1.1.1n patch

Bugs fixed:

  1. Remove UPnP Network device detail information with serial number
  2. Force FW upgrade tap cancel direct to wrong page

V1.00(ABZF.5)C0: 07/03/2022

Known Issues

  1. With IPv6 enabled, pictures, files, etc. on Line cannot be sent and received


  1. Modify agent online check & fix update bssid.
  2. support “Digitalisierungsbox PREMIUM 2” and “Digitalisierungsbox SMART 2”
    follow uMeshController db.
  3. Add patch to remove mtk mesh send arping.
  4. Add HLD to send reload mesh req.

Bugs fixed:

  1. Fix uMeshController daemon failed.
  2. Fix Write /tmp/ApplicationData/map.cfg failed.
  3. When set traffic_separation data, to check old value.
  4. If controller mesh daemon failed, send request to reload agent mesh.
  5. When change backhaul type [Ethernet->WiFi], send request to reload agent
1 Like

Concerning that version: I got a message by Zyxel that "RD team found some code issue on ABZF5C0.Therefore, the internal decided to remove ABZF5C0 from the Website. Right not, only ABZF4C0 is available."