Hello everyone. I have an Asus BT-8 I would like to set up as a wireless repeater using relayd (ideally with MLO but one step at a time). I’ve followed the guide and even submitted a bug report at github convinced it was an issue with that specific model but was cited “expected behaviour” and suggested I make a new topic related to my config so here I am.
Not sure if relevant, but as I mentioned in the bug report, at the “Test connection” phase the router wouldn’t ping the openwrt.org website until I manually changed the channel (a behaviour that seems to be trailing me and making the unit virtually unusuable).
Basically, following a reboot/power cycle the only radio that starts broadcasting is radio0 at 2.4GHz. The sta/client connection on radio1 at 5GHz is established and the internet on the 2.4GHz ap works. But the radio1 and radio2 (6GHz) won’t start broadcasting until I manually change radio 1 from “36” to “auto”, save and apply, then change it back to “36” and save and apply once again. Only then do the all three radios broadcast properly, until I reboot or power cycle/move the unit to where it’s supposed to be.
Here’s my /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
list ipaddr '127.0.0.1/8'
config globals 'globals'
option dhcp_default_duid '000435e2fd932b8c4f6b840261d71f7fb224'
option ula_prefix 'fd72:d0d7:54ee::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ip6assign '60'
list ipaddr '192.168.2.1/24'
config interface 'wwan'
option proto 'static'
option ipaddr '192.168.100.100'
option netmask '255.255.255.0'
option gateway '192.168.100.1'
list dns '192.168.100.1'
config interface 'repeater_bridge'
option proto 'relay'
option ipaddr '192.168.100.100'
list network 'lan'
list network 'wwan'
Any help? Did I mess something up? I’ve had the same config on my ancient TP Link TL-WA-830-RE working for years. No idea why this one is behaving so quirky. The sta/client connection establishes successfully, which brings the 2.4GHz ap on and gives it internet. But radios 1 and 2 won’t start broadcasting until I manually change radio 1 from “36” to “auto” and back to “36”…
Are you implying it’s impossible to pull of with this specfic unit? I thought once I put OpenWRT on it, I’d be able to use the OpenWRT’s functionalities, including the wireless repeater function. I know the official Asus firmware doesn’t support it, OpenWRT support was the sole reason I got it.
I mean it clearly works, just doesn’t work properly. Not sure what’s with the hostility.
This is because a very long time has gone by since relayd was first created to solve a problem that has long since been fixed.
Relayd is now very outdated, but as you say it does still work, but it can be very problematic.
This issue keeps coming up on this forum, so it seems you have posted before researching.
This is perhaps excusable to a degree, because you did have relayd working on your old system, but still....
@brada4 's comment was intended to point you at the up to date way of doing things, particularly if you only have your main router and a remote access point. For this a very simple "point to point" two node mesh would be simple and reliable.
If you have a number of remote access points, we can do that too, but it is more complicated as you might expect.
You could also use WDS, older but very popular. Someone might pop up here suggesting it, who knows.
So, you have an Asus BT-8 and "something else".....
Give us some details and we will try to help.
Sorry if it/I came across that way. I’ve mentioned on several occasions I’ve no idea what I’m doing. I will admit I was under the impression relayd is the only course of action when a person has just a single unit at their disposal. Saw it in the wiki over a decade ago, worked flawlessly and I just stuck to what I knew. If there are better alternatives, apologies, I must admit I fell off the game and wasn’t even aware there were/are alternatives to relayd (although I’m still reading various bug reports in the rc2/3 threads where the 5GHz radio doesn’t come up for whatever reason, so I’d still chalk it up up as a bug in the current meta but hey, if there are better ways to do things, I’m all for it). Just point me in the right direction.
The main router is a ZTE F8648P with a ZTE H3601P unit connected as an EasyMesh node (ISP gear I got recently as an upgrade, just held down a button and it paired to the main unit). They’re on the floor below and cover the area rather nicely for what they are. I’m on the floor above with my Asus rog usb be92 wifi 7 dongle and I was getting ~600ish mbit/s from the easymesh node sitting directly below the usb dongle a floor below (the easymesh node is only 2x2 so I guess that’s to be expected - although I have seen spikes up to 900mbit/s). And yes the dongle is a horrible price to performance ratio imho, only post purchase did I read/find out it’s hardware capped and can’t even deliver the full 5gbit/s the usb3 port could but caps at 2/2.5gbits or so >.>. In my defense, there were no reviews prior to purchase (and it was my only wifi7 option over here in the EU since I don’t have a new enough motherboard for Intel’s pcie BE cards). But that’s besides the point.
Mesh to mesh sounds great but I was/am under the impression I’d need at least two routers with 802.11s support to accomplish that. I only have a single BT8 unit, and as the main router is on the floor below, I am unable to run a wire to it. That’s why I’ve been using relayd all these years. I’d love to upgrade to a proper mesh system at some point in the future, but waiting for wifi7 gear to mature and become more commonplace. Don’t really want to (or can’t atm to be frank and honest) throw away any more money, especially on ‘only’ 3x3 gear.
The only reason I got the BT8 was because it was touted as the first OpenWrt wifi7 supported router (apart from the banana pi) and I actually wanted to test something called prplMesh to make it a part of my existing EasyMesh system (but that fell through entirely, I tried compiling it from scratch myself using my IT wiz sister’s help (well she did most of the work) but we just couldn’t get it working, and I was unable to find a means of reaching out to the prplMesh community, seems more like a vendors only thing). Let’s just forget that part.
But anyway, the idea now is/was to use the BT8 as a wireless repeater with an ax connection to the ISP’s router (which I can’t install OpenWRT on) and have the BT8 broadcast an MLO network to see if I can get more than 600mbit’s I was getting (the BT8 connects to the main 4x4 ax router at max 3x3 ax speeds if I put it in the hallway at ~2.4gbit/s). I’m hoping for 900-1000, but I can live without that. Just wanted to treat myself to a new toy and test things with MLO on the horizon. Hoping I don’t need a 2nd unit just to get started. Would like to get up-to-date and running stable in any case though. So what are my options?
First, not your fault, but the fault of the marketing departments of the manufacturers for misusing and misappropriating the word "mesh". An 802.11s network is an International standard defining what a mesh backhaul is. But "mesh" is just a word not a trade mark.
EasyMesh is 100% closed source "wireless extension" system roughly based on a WDS like setup.
For what it is, it is just fine and can do the job, as you have found out.
But it is also 100% incompatible with open source OpenWrt, regardless of what you might read. (I think you found this out too, with the help of your IT-Wiz sister.)
It is still in the twilight zone so don't hold your breath - yes it is coming - but expect some time to elapse before it becomes properly supported in mainstream OpenWrt. Hopefully not too long but who knows.
If you want a no-compromise solution, you will need a second unit to get started - but the horrendous price of the BT8 can only be justified if it is for personal education in my opinion.
I run my test mesh network with all sorts of hardware (it's a test network).
My current "go-to" device if I am after performance id the gl-mt6000 (wifi6). Between two of these I consistently achieve an 802.11s connection in excess of 1Gb/s on the 2.4GHz band.
I use 2.4 GHz for reasons of physics, it just works better, greater penetration and lower multipath issues because of the lower frequency. If I want more b/s I can go to 5GHz at the expense of degraded coverage.
Note: you can get 2 mt6000s for the price of one BT8.
Lots to think about. But if you want a quick and easy solution to get you going without a steep learning curve, go for the TravelMate solution . You can use the BT8 for this, overkill, but you have it... You can revisit later.
Thank you. I’m giving it all she’s got cap’n but I’ve ran into a snag It’s probably yet another problem between the keyboard and the screen but my scan is coming up empty
I’ve done another reset, joined my wifi network to get internet connectivity and installed travelmate and luci-app-travelmate packages. Ran the Interface Wizard and accepted the default values.
Next step, Wireless Stations → Scan is coming up empty for all three radios
I’ve tried setting the country codes for the master aps but to no avail.
Yeah, completely clean slate following a factory reset. I also tried the AP+STA script you linked but it hung the putty connection on “Configuring WWAN” the first time around and the router wasn’t pingable, and the second time around I tried inputting uci commands manually and it also hung at that same part. Couldn’t ping it even after changing my IP to 192.168.2.x range. Didn’t try a power cycle, went back to troubleshooting travelmate since it sounds like an upgrade of the said script. I just can’t seem to catch a break. Spinning around in circles with google Gemini right now. Something about the phy0.1-sta not getting a channel even after a bajillion uci commits.
About to try:
When you run wifi reload, the system tries to build the interfaces you defined. If the driver (likely mt76) sees a conflict—or if the 5GHz radio is locked by regulatory domain (Croatia DFS)—it simply gives up on the Station interface but keeps the AP interface alive.
1. The "Nuclear" Wireless Reset
We need to force a configuration that is impossible for the driver to ignore. We will disable the "Master" radio first, then apply the settings.
Bash
# Disable Radio 1 (5GHz) temporarily
uci set wireless.radio1.disabled='1'
uci commit wireless
wifi reload
sleep 2
# Now, force set the configuration
uci set wireless.radio1.disabled='0'
uci set wireless.radio1.country='HR'
uci set wireless.radio1.channel='36'
uci set wireless.radio1.hwmode='11a'
uci set wireless.radio1.htmode='VHT80'
# Re-create the Station interface correctly
uci delete wireless.wwan
uci set wireless.wwan=wifi-iface
uci set wireless.wwan.device='radio1'
uci set wireless.wwan.mode='sta'
uci set wireless.wwan.network='wwan'
uci set wireless.wwan.ssid='Travelmate_Scan'
uci commit wireless
wifi reload
The whole thing kinda smells of a rc2/3 bug to me, others reported radio1 sta+ap failing to come up for them as well, but idk… I’m probably the biggest noob on the forum, but I’m really trying everything I can here
You were connected via wireless, my guess. Starting a STA virtual interface will disable the AP virtual interface as the radio has to track the channel used by the remote AP you are trying to connect to, so goes down. If the STA succeeds in connecting, to the remote, the local AP virtual interface will then come up.
Take anything Gemini says with a pinch of salt. Any channel setting of the local AP is ignored, as I explained above.
I have not noticed a bug in 25.10 in this area, but I have not particularly looked either. @lleachii has though. That is why it is a release candidate - to shake out the bugs.
Maybe you should look at that pair of mt6000 routers after all...
Hah, thanks but gonna have to take a pass for now. I’ll just ascribe it to the aforementioned AP+STA bug in 25.12. Hopefully the team knows about it and is working on it. I’m okay waiting for a rc4 or the final release for that matter. Hopefully it gets fixed by then. Just trying to eliminate/minimize the possibility that I’m doing something wrong. And since both travelmate and the script are giving me errors (I tried the script connected just via ethernet with wifi turned off and preset the ip to 192.168.2.x - still hung - guessing the 5ghz interface didn’t want to come up from what google has told me).
Waiting game it is for now then. Hopefully good things do sometimes come to those that wait.
Did I mess something up? I’ve had the same config on my ancient TP Link TL-WA-830-RE working for years. No idea why this one is behaving so quirky. The sta/client connection establishes successfully, which brings the 2.4GHz ap on and gives it internet. But radios 1 and 2 won’t start broadcasting until I manually change radio 1 from “36” to “auto” and back to “36”…
It’s probably yet another problem between the keyboard and the screen but my scan is coming up empty