Does OpenWrt firmware support Beamforming + MU-MIMO- just for the record?

There are a number of WiFi issues currently with OpenWrt:

  1. Beamforming
  2. MU-MIMU
  3. Single network login for 2.4/5/6 GHz (great feature to simplify wifi login on newer routers)
  4. Airtime Fairness
  5. Better standards for Mesh, MFP, etc: 802.11r, 802.11w, etc. (driver related)
  6. WiFi 6 aka 802.11ax (support beeing added in master branch but we still need open source drivers)
  7. Overall performance: optimizations with better WiFi settings for each target on default installation, OpenWrt could improve in this area.

Some of the open source driver deficiencies, not OpenWrt's fault, sadly may not improve.

2 Likes

All the mistakes you mention is a lie.

All of this works without problems in OpenWrt on the Belkin RT3200 router:

  1. Beamforming :white_check_mark:
  2. MU-MIMO :white_check_mark:
  3. Band Steering :white_check_mark:
  4. Airtime Fairness :white_check_mark:
  5. Mesh :white_check_mark:
  6. WiFi 6 aka 802.11ax :white_check_mark:
  7. Overall performance: Perfect :white_check_mark:

Photo of the 3 Belkin RT3200 routers.

2 Likes

Would you able to share your experience in regards to your OpenWRT based Belkin RT3200 routers?
How did you come into the conclusion that all the following 7 items mentioned above work?

Could you elaborate what the actual issues are?
1-5 are technologies or features, but you don't mention any issue related to them.
6&7 could be described as issues, although I think with 6 you're mixing up things. Whenever OpenWrt adds support for anything, it is based on open source drivers. ath11k is, for example, an open source driver for 802.11ax wireless devices. You probably mean that these open source drivers still rely on closed firmware, just like ath10k does.

Regarding 7: The idea is nice. But I don't think it's realistic or even technically the best way to go for three reasons:
First, in order to do this kind of target-specific optimization work, the developers would have to own or have access to all those supported devices and then, of course, spend time on testing and optimizing them. Second, whether you achieve 400Mbps with OpenWrt and 500Mbps with the vendor-firmware may not be all that important for some or even many users as long as it works and offers reasoable security. Third, OpenWrt tries to simplify and abstract wireless configuration quite a bit. If you ever have manually configured hostapd, you should be aware that this is far from intuitive. And it's sometime hard to impossible to find good, understandable information or documentation for all the configuration options. This is, I think, where OpenWrt shines. It takes away a lot of the complexity. If you ever have looked at the code that put's all these bits together (see e.g. /lib/netifd/hostapd.sh), you know that there is already some effort and magic going on in the backgroud to make it all work. Adding logic to make this really optimized for each device would make this code much, much more complex and hard to maintain. I actually think, it makes sense to not want to change this. For those who want optimal performance, I suggest to actually document the configuration or setup that you found for your device so that others can use that as a baseline for their own customization and optimization efforts.

2 Likes

@O_o All of that works in OpenWrt well or are you talkin the OEM firmware? That's very impressive if it's OpenWrt, had no idea support was that far along on this target. I'd get one if there was a USB 3.0 port, I use that daily with samba4 (get about 120 MB/s read-write which is fantastic) on my WRT32X.

@silentcreek I just meant in very general terms a lot of devices have issues with a mixture of those items, not being target specific although mvebu comes to mind (very high performance target, one of the fastest on OpenWrt, but certainly wifi is not ideal). I understand what you're saying about #7 but it would still be great to have optimizations on the top few target people use.

My experience is one of the best purchases I made this year.

The MediaTek drivers have the best support to date and above explains how to know if those features work, although it was already known that the MediaTek drivers in OpenWrt support that.

The only "problem" (not a real problem) is that I had to use a new WiFi name and reconnect all the devices, when I switched from my old router to the new one, because that is recommended to avoid strange problems that happen when you use the OLD WiFi name and password when switching to different routers, firmwares or WiFi drivers.

WiFi drivers sources:

@phinn OpenWrt firmware.

1 Like

yes i have belkin rt3200 and is the best wifi router i playing to video games with and it work very well i waiting a luci 21.02 stable if he out he will a good news

1 Like

Where is the Amazon :star::star::star::star::star: affiliate link ;- )

1 Like

Yes. We know. Judging from the way and frequency you're gushing about them one could be forgiven to believe you're a teenage girl and RT3200 is a Korean boy band. The only thing that's missing is you posing them for group pictures and creating Belkin RT3200 memes ... oh wait.

15 Likes

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.