How to WiFi Mesh on OpenWRT (Multy M1)
Вставка
- Опубліковано 27 вер 2024
- How to setup WiFi Mesh repeating on OpenWRT running on a Zyxel Multy M1.
IMPORTANT: Only the main point can be ethernet to the central network. Using ethernet on more than one into the same "backbone" will cause a network loop.
Using the "BATMAN" addon for OpenWRT may allow you to auto select the backhaul and prevent network loops but I looked into the config and it seemed.... super unintelligible (for me, at least) so gave up.
E.g. This setup can only work as "wireless backhaul", not ethernet.
If you needed more than one to be ethernet you can probably manage it using two different Mesh IDs and making sure only one on each ID is connected via ethernet.
How to install OpenWRT on a WSM20: • How to install OpenWRT...
Since I am very lazy person I configure my mesh nodes in a way that I install all necessary additional/replacing packages, save configuration of the node, go to the other node, install/remove packages again and restore configuration. It will save you a lot of clicks and time in case you have same devices. BTW consider also using B.A.T.M.A.N coz it is able handle VLANs which mesh cant so you cannot have for example guest network over wifi. Also go to the System/startup and disable dnsmasq, firewall and odhcpd. I also remove wan network and bridge wan interface to the lan to have more ports. Keep posting such perfect videos bro! I appreciate your work! :)
Some good advice. Will pin the comment :)
I second this...I just finished my setup with a GL.iNet GL-MT6000 as the main router and 3 Zyxel Multy M1 as wireless APs with 3 WIFIs (Private, Guest, IoT) and it works like a charm. Once you get the point regarding B.A.T.M.A.N, setup is fairly simple. I followed the B.A.T.M.A.N video by OneMarcFifty and had to jump a bit back and forth to get everything lined up but it all works in the end and that's what counts! :)
@@gil_grissom9669 yes there are batman packages and luci batman packages in openwrt 23.05.4 and there is also videotutorial at youtube see OneMarcFifty channel
Thanks for the video. Did you remove or install any other wpad package? The instructions on the OpenWrt wiki say that the basic wpad package needs to be removed and another wpad package installed for the mesh network.
N.B. As you have identical devices, it would be quicker to save the configuration from one configured device and deploy it to the other two, and then change the IP addresses.
I did not change anything to do with the wpad packages.
@@freename would you mind taking a look which wpad package is installed by default?
@@gig-0 Entire package list...
base-files 1550-r23630-842932a63d - -
busybox 1.36.1-1 - -
ca-bundle 20230311-1 - -
cgi-io 2022-08-10-901b0f04-21 - -
dnsmasq 2.89-4 - -
dropbear 2022.82-5 - -
firewall4 2023-09-01-598d9fbb-1 - -
fstools 2023-02-28-bfe882d5-1 - -
fwtool 2019-11-12-8f7fe925-1 - -
getrandom 2022-08-13-4c7b720b-2 - -
hostapd-common 2023-09-08-e5ccbfc6-6 - -
iw 5.19-1 - -
iwinfo 2023-07-01-ca79f641-1 - -
jansson4 2.14-3 - -
jshn 2023-05-23-75a3b870-1 - -
jsonfilter 2018-02-04-c7e938d6-1 - -
kernel 5.15.137-1-9c242f35… - -
kmod-cfg80211 5.15.137+6.1.24-3 - -
kmod-crypto-acompress 5.15.137-1 - -
kmod-crypto-aead 5.15.137-1 - -
kmod-crypto-ccm 5.15.137-1 - -
kmod-crypto-cmac 5.15.137-1 - -
kmod-crypto-crc32c 5.15.137-1 - -
kmod-crypto-ctr 5.15.137-1 - -
kmod-crypto-gcm 5.15.137-1 - -
kmod-crypto-gf128 5.15.137-1 - -
kmod-crypto-ghash 5.15.137-1 - -
kmod-crypto-hash 5.15.137-1 - -
kmod-crypto-hmac 5.15.137-1 - -
kmod-crypto-manager 5.15.137-1 - -
kmod-crypto-null 5.15.137-1 - -
kmod-crypto-rng 5.15.137-1 - -
kmod-crypto-seqiv 5.15.137-1 - -
kmod-crypto-sha512 5.15.137-1 - -
kmod-gpio-button-hotplug 5.15.137-3 - -
kmod-hwmon-core 5.15.137-1 - -
kmod-leds-gpio 5.15.137-1 - -
kmod-lib-crc-ccitt 5.15.137-1 - -
kmod-lib-crc32c 5.15.137-1 - -
kmod-lib-lzo 5.15.137-1 - -
kmod-mac80211 5.15.137+6.1.24-3 - -
kmod-mt76-connac 5.15.137+2023-08-14-b14c2351-1 - -
kmod-mt76-core 5.15.137+2023-08-14-b14c2351-1 - -
kmod-mt7915-firmware 5.15.137+2023-08-14-b14c2351-1 - -
kmod-mt7915e 5.15.137+2023-08-14-b14c2351-1 - -
kmod-nf-conntrack 5.15.137-1 - -
kmod-nf-conntrack6 5.15.137-1 - -
kmod-nf-flow 5.15.137-1 - -
kmod-nf-log 5.15.137-1 - -
kmod-nf-log6 5.15.137-1 - -
kmod-nf-nat 5.15.137-1 - -
kmod-nf-reject 5.15.137-1 - -
kmod-nf-reject6 5.15.137-1 - -
kmod-nfnetlink 5.15.137-1 - -
kmod-nft-core 5.15.137-1 - -
kmod-nft-fib 5.15.137-1 - -
kmod-nft-nat 5.15.137-1 - -
kmod-nft-offload 5.15.137-1 - -
kmod-ppp 5.15.137-1 - -
kmod-pppoe 5.15.137-1 - -
kmod-pppox 5.15.137-1 - -
kmod-slhc 5.15.137-1 - -
kmod-thermal 5.15.137-1 - -
libblobmsg-json20230523 2023-05-23-75a3b870-1 - -
libc 1.2.4-4 - -
libgcc1 12.3.0-4 - -
libiwinfo-data 2023-07-01-ca79f641-1 - -
libiwinfo20230701 2023-07-01-ca79f641-1 - -
libjson-c5 0.16-3 - -
libjson-script20230523 2023-05-23-75a3b870-1 - -
liblucihttp-ucode 2023-03-15-9b5b683f-1 - -
liblucihttp0 2023-03-15-9b5b683f-1 - -
libmbedtls12 2.28.5-2 - -
libmnl0 1.0.5-1 - -
libnftnl11 1.2.6-1 - -
libnl-tiny1 2023-07-27-bc92a280-1 - -
libpthread 1.2.4-4 - -
libubox20230523 2023-05-23-75a3b870-1 - -
libubus20230605 2023-06-05-f787c97b-1 - -
libuci20130104 2023-08-10-5781664d-1 - -
libuclient20201210 2023-04-13-007d9454-1 - -
libucode20230711 2023-11-07-a6e75e02-1 - -
libustream-mbedtls20201210 2023-02-25-498f6e26-1 - -
logd 2022-08-13-4c7b720b-2 - -
luci git-23.051.66410-a505bb1 - -
luci-app-firewall git-23.306.38853-a0466cd - -
luci-app-opkg git-23.311.75635-769b30c - -
luci-base git-23.306.39416-c86c256 - -
luci-light git-23.024.33244-34dee82 - -
luci-mod-admin-full git-19.253.48496-3f93650 - -
luci-mod-network git-23.313.56166-6da284d - -
luci-mod-status git-23.306.52197-bdcd3e0 - -
luci-mod-system git-23.306.39416-7d3abf8 - -
luci-proto-ipv6 git-21.148.48881-79947af - -
luci-proto-ppp git-21.158.38888-88b9d84 - -
luci-ssl git-23.035.26083-7550ad6 - -
luci-theme-bootstrap git-23.306.39416-c86c256 - -
mtd 26 - -
netifd 2023-11-10-35facc83-1.1 - -
nftables-json 1.0.8-1
odhcp6c 2023-05-12-bcd28363-20 - -
odhcpd-ipv6only 2023-10-24-d8118f6e-1 - -
openwrt-keyring 2022-03-25-62471e69-2 - -
opkg 2022-02-24-d038e5b6-2 - -
ppp 2.4.9.git-2021-01-04-4 - -
ppp-mod-pppoe 2.4.9.git-2021-01-04-4 - -
procd 2023-06-25-2db83655-2 - -
procd-seccomp 2023-06-25-2db83655-2 - -
procd-ujail 2023-06-25-2db83655-2 - -
px5g-mbedtls 10 - -
rpcd 2023-07-01-c07ab2f9-1 - -
rpcd-mod-file 2023-07-01-c07ab2f9-1 - -
rpcd-mod-iwinfo 2023-07-01-c07ab2f9-1 - -
rpcd-mod-luci 20230123-1 - -
rpcd-mod-rrdns 20170710 - -
rpcd-mod-ucode 2023-07-01-c07ab2f9-1 - -
ubi-utils 2.1.5-1 - -
uboot-envtools 2023.04-1 - -
ubox 2022-08-13-4c7b720b-2 - -
ubus 2023-06-05-f787c97b-1 - -
ubusd 2023-06-05-f787c97b-1 - -
uci 2023-08-10-5781664d-1 - -
uclient-fetch 2023-04-13-007d9454-1 - -
ucode 2023-11-07-a6e75e02-1 - -
ucode-mod-fs 2023-11-07-a6e75e02-1 - -
ucode-mod-html 1 - -
ucode-mod-math 2023-11-07-a6e75e02-1 - -
ucode-mod-nl80211 2023-11-07-a6e75e02-1 - -
ucode-mod-rtnl 2023-11-07-a6e75e02-1 - -
ucode-mod-ubus 2023-11-07-a6e75e02-1 - -
ucode-mod-uci 2023-11-07-a6e75e02-1 - -
ucode-mod-uloop 2023-11-07-a6e75e02-1 - -
uhttpd 2023-06-25-34a8a74d-1 - -
uhttpd-mod-ubus 2023-06-25-34a8a74d-1 - -
urandom-seed 3 - -
urngd 2023-11-01-44365eb1-1 - -
usign 2020-05-23-f1f65026-1 - -
wireless-regdb 2023.09.01-1 - -
wpad-basic-mbedtls 2023-09-08-e5ccbfc6-6
Very nice video, i am tempded to buy the 2 pack for 50€
Did you experience any disconnection?
You have band steering enabled right?
It should be great if you can provide a .sh or the configuration of the router and the satellite
From the video the one on the far left keeps doing strange things. I lose connectivity to it from my wired LAN.. yet the LAN can reach the other two.
A laptop connected to the left mesh unit can ping the middle mesh unit but not the main node or the main network.
I do wonder if it is a faulty Multy which might explain some of the unreliability I had been having with the Multy when deployed in stock firmware too.
The other two have been reliable.
Though this is just on the test bench and I am yet to deploy them at a customer (which is where the complaints really kick in if something is unreliable).
Thank you for your time, I got a set of three of these last black friday for cheap, they worked fine for a few weeks and then they kept disconnecting over and over again. I reset and retried until I gave up and kept using only the main one for months until I got tired and started looking into alternatives, and found they supported openwrt.
I work in IT so I started doing it on my own but for some reason it did not work. Then after watching your videos I set them all to the same channels and they worked fine!
I don't really get why everything needs to be on one channel as it is counter intuitive (at least to my experience only using ethernet backhaul in deployments) for every wifi installation, but I don't have any other 5ghz networks around so at least now I have a working mesh network...
If they are ethernet backhaul you shouldn't need them on the same channel as long as you've got the ethernet wifi bridges configured in each router correctly.
If they are wifi backhauled they need to be on the same channel to be able to talk to eachother.
is it necessary to turn on the wifi fast roaming 802.11r on every access point?
Yes. And this post might be helpful.. www.reddit.com/r/openwrt/comments/515oea/finally_got_80211r_roaming_working/
Can you run a iperf3 test between two of the nodes?
Maybe but until then.. this is a librespeed test across the two (to a local server in my LAN)...
OpenWRT in 802.11s mode:
444mbps down 700mbps up on wifi to main node.
330mbps down 260mbps up on the first satellite (right next to main node).
430mbps down 300mbps up on laptop ethernet into first satellite.
Without autosetup Mesh11sd, full speed will not be achievable
Why do you think that?
@@freename I had problems that 4 ax3600 were jamming eachother. From 200Mb/s dropped to 40. When I red to run autosetup mesh11ds via console and then works like a charm with minimal drops of speed!
Hi, I have a set of 3 Multy's and for 2 months, I have had issue after issue with them. I wish I could speak "network" so that I could understand what you are doing, and fix mine. Zyxel customer care does respond once a day, on average, but does not answer basic questions asked - My biggest problem is regular dropping of the internet, but the satellite stays green. Apparently I have to look at the main/router to see if there is an internet issue, as that would be red (but at the other side of the house). Is it too much to ask that the LED tells you there is a problem! And the app... let's not go there.
Thanks for your content, I'm trying to learn!
M
I've definitely experienced it, when the Multy is in routing mode, a drop of ability to load web pages but during that time I can still ping the internet OK.
I gave up. Now testing these devices with the OpenWRT Mesh instead. I need to arrange to install one at a customer and see if their complaints continue.
Hi, How did you get on with OpenWRT? I am losing the will to live with these Multys and the tech support is absolute crap. Is this upgrade easy enough for a novice to do, and would I do it to all three Multys? Thanks again.
@@freename
I only can install openwrt on the main M1. When i change the ip and subnet my connection is lost and i can not enter the M1 anymore. I do everything exactly as you say. Maybe it is the 10.0.0.40 but when i change it, onnection to the main is loat and i have to reset it again to 192.168.1.1. So i can nog use the mesh. What can be the problem?
10.0.0.x is my internal LAN range. You need to be using whatever your normal routers IP range is. Only use 10.0.0.x if your LAN is that IP range.
Thanks for the video. Everything went great following the first one and flashing openwrt on all the nodes.
Following this video however, I’m stuck.
I’ve changed the IP to 10.0.0.40 and now I’m unable go access the first node. It’s IP was 192.168.1.2 before this. It still provides me with a wifi signal, but I really don’t know how to access it. When typing ipconfig in the command it shows a regular 192.168.1.1 IP which just logs me in my regular modem.
Could I just factory reset by pressing the back button or would that completely brick my node? I really don’t know how to access it again as I’ve tread much options and haven’t figured out a way yet…
Sorry I did not reply sooner. UA-cam spammed your comment so I didn't see it until checking the moderation folder just now.
Best option.. set the IP of your computer temporarily to 10.0.0.50 (or anything in 10.0.0.) and then you can access the OpenWRT and set it back to the IP within your normal 192.168.1.X IP range.
Then set your computer back to DHCP/automatic.
Or.. you can factory reset the node, it won't brick it .. but it will go back to being DHCP server and on 192.168.1.1 which might collide with your main router until you fix it.
I'm fighting with my multy's all day to get them to behave. They won't allow me to change the static IP in openwrt as it crashes the unit. I'm currently at my 10th factory reset of the day. At this point I'm not looking for a solution, just a comforting "I hear you" from a fellow struggler with these units will do..
So openwrt dont solve the problem.
it can be a problem of used module
Seems very unusual that setting a static IP breaks it. You can see in my video it works ok for all 3.
The IP is the only thing you are changing?
Are you sure the IP you are using isn't already in use on your network?
Once changed are you then making sure your computer is on the right IP range to still be able to access the new IP of the Multy?
Dude I hear you! I’ve been having the same issue. I forget the name of the option I used but it’s the one under the dropdown of “sace and apply” that basically applies the settings without waiting for you to reconnect. Let me know if you got it solved