Users needed to test Wi-Fi stability on Linksys WRT3200ACM & WRT32X on OpenWrt 21.02

I changed regdb to disable DFS for FR (France) and I added a new country code 98 a copy of FR, to satisfy the third radio requirements. This solves many of the issues with unusable channels.

I found this in my old notes. It was once told by divined bit wizards that the radio 0 and 1 go best with default country code settings and that radio 2 needs a custom command line executed, to set the country, to be behave best in combination with radio 0 and 1.
But I just kept the notes, I have never experimented with radio 2 (maybe you find some more in the forum, this never seemed to have made it into the wiki)

echo "mwifiex reg_alpha2=FR" > /etc/modules.d/mwifiex

1 Like

Maybe you can reconfigure the nft rules to fix the offloading problem.
You can start from here: https://github.com/openwrt/openwrt/issues/10224#issuecomment-1449417359

See this: https://github.com/openwrt/openwrt/issues/10224#issuecomment-1449417359

So, there's a workaround for people, even if this doesn't get fixed before 23.05 stable?

Just joining this conversation to say I have a wrt3200ac that has a damaged switch only a single lan port works but WiFi all works fine. I'd be willing to commit it to testing potentially damaging driver builds I'm happy with compiling openwrt and kernels but I don't have driver and kernel level dev skills.

Or I could donate it to the developer working on the driver

Should probably mention my home network consists of 1x wrt3200 main router using mwan3 with 2x4g mobile data channels as 2.4g channel WPA clients to mobile hotspots. and 2x wrt32 as dumb aps but with vlans so the 2x 4g lines can move round the house with fast transistion. They are on the 2.4ghz radio2 as clients to mine and my wife's android hotspots.

All devices at home operate on the 5ghz radio1 and allow us to have house internet while we're in the house then when we leave no net or only one leaves net still works. Android hotspots are permanently on.

I have this setup as I don't have a copper line

I'm currently running wrt32x on

Firmware Version OpenWrt 22.03.2 r19803-9a599fee93 / LuCI openwrt-22.03 branch git-23.119.80898-65ef406
Kernel Version 5.10.146

And running the wrt3200 on

Firmware Version
OpenWrt 22.03.2 r19803-9a599fee93 / LuCI openwrt-22.03 branch git-22.288.45147-96ec0cd
Kernel Version
5.10.146

My only problem at the minute is I'm stuck on 80mhz and and 5ghz stuck on ch36

All very stable

id like to be a part of this, especially since Im facing an issue with this

Im a long time user of openwrt, and have a wrt3200acm (previously had a wrt1900)
for the longest time I used DavidC builds and they worked great

However they are EOL effectively, afaik
yesterday I upgraded from 19 to latest for my device 23.05 and have serious network performance degradation

I see others mention the mwlwifi drivers and i remember that being an issue in the past but im not sure what or how to change these

I have also used a few options in the network config, namely:

option disassoc_low_ack '0'
option hwmode '11g'

but they no longer fix anything, maybe made it a bit better

How to make this work, via cli?

yes, you need to run some commands or edit configuration files.

I put the following commands: nft flowtable inet fw4 ft { devices = { pppoe-wan, br-lan };} nft insert rule inet fw4 forward meta l4proto { tcp, udp } flow add @ft, I really didn't feel any difference, do I need to do something else? I'm using a wrt3200acm

Got no idea of what your network setup is, but are you actually experiencing flow-offloading problem since version 22.03.0-rc2 ?

Btw, may be you should post your questions to the github issue page, and get more feedback.

im on 23.05 full release for 2 days now, wifi just crapped out today.
went to 1kbps, completely unusable.

Seems all quite good

schindler@t495s:~$ iperf3 -c openwrt
Connecting to host openwrt, port 5201
[  5] local fd4d:1094:7c67::1cc port 42526 connected to fd4d:1094:7c67::1 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  56.6 MBytes   475 Mbits/sec    0   1.27 MBytes       
[  5]   1.00-2.00   sec  53.8 MBytes   451 Mbits/sec    0   1.33 MBytes       
[  5]   2.00-3.00   sec  56.2 MBytes   472 Mbits/sec    0   1.63 MBytes       
[  5]   3.00-4.00   sec  55.0 MBytes   461 Mbits/sec    0   2.01 MBytes       
[  5]   4.00-5.00   sec  56.2 MBytes   472 Mbits/sec    0   2.01 MBytes       
[  5]   5.00-6.00   sec  56.2 MBytes   471 Mbits/sec    0   2.01 MBytes       
[  5]   6.00-7.00   sec  52.5 MBytes   441 Mbits/sec    0   2.01 MBytes       
[  5]   7.00-8.00   sec  55.0 MBytes   461 Mbits/sec    0   2.01 MBytes       
[  5]   8.00-9.00   sec  55.0 MBytes   461 Mbits/sec    0   2.01 MBytes       
[  5]   9.00-10.00  sec  56.2 MBytes   472 Mbits/sec    0   2.01 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   553 MBytes   464 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   552 MBytes   463 Mbits/sec                  receiver

iperf Done.
schindler@t495s:~$ iperf3 -c openwrt -R
Connecting to host openwrt, port 5201
Reverse mode, remote host openwrt is sending
[  5] local fd4d:1094:7c67::1cc port 44456 connected to fd4d:1094:7c67::1 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  50.4 MBytes   422 Mbits/sec                  
[  5]   1.00-2.00   sec  49.4 MBytes   414 Mbits/sec                  
[  5]   2.00-3.00   sec  54.2 MBytes   456 Mbits/sec                  
[  5]   3.00-4.00   sec  48.8 MBytes   409 Mbits/sec                  
[  5]   4.00-5.00   sec  47.9 MBytes   401 Mbits/sec                  
[  5]   5.00-6.00   sec  47.4 MBytes   398 Mbits/sec                  
[  5]   6.00-7.00   sec  45.8 MBytes   383 Mbits/sec                  
[  5]   7.00-8.00   sec  43.2 MBytes   363 Mbits/sec                  
[  5]   8.00-9.00   sec  49.6 MBytes   416 Mbits/sec                  
[  5]   9.00-10.00  sec  50.8 MBytes   427 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.03  sec   491 MBytes   411 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   487 MBytes   409 Mbits/sec                  receiver

iperf Done.

I've read this entire thread after struggling with OpenWRT on my WRT3200ACM router. I believe I had 22.03.2 installed, but reverted back to factory firmware because I screwed up the OpenWRT settings trying to configure it correctly and got frustrated with it.

I bought this router a few years ago knowing nothing about OpenWRT. I installed OpenWRT as a way to try to get rid of ads and spam and to improve security. I've not inspected the router logs very closely so couldn't tell you if it was dropping connections constantly. The wireless broadcasting has always been weird/intermittent.

Is there a link to davidc502's build somewhere - the last really good one? I would like to start there and then completely lock the thing down. Is there a public facing github repository with the commit history available to WRT3200ACM owners?

You should try 23.05.2 to see if it works for your needs before resorting to davidc502's builds, which are out of date from a security perspective. Not everyone is going to run into problems with the latest release.

1 Like

Owengerig mentioned:

"" yesterday I upgraded from 19 to latest for my device 23.05 and have serious network performance degradation

I see others mention the mwlwifi drivers and i remember that being an issue in the past but im not sure what or how to change these

I have also used a few options in the network config, namely:

option disassoc_low_ack '0'
option hwmode '11g'

"""

I sounds like it may not work well for my device WRT3200ACM.

What security patches were applied between Davidc's builds and the latest OpenWrt?

What was the need to include a new custom linux kernel after the last successful build of (Davidc502) 19.07.10 ?

https://firmware-selector.openwrt.org/?version=19.07.10&target=mvebu%2Fcortexa9&id=linksys_wrt3200acm

If you are going to provide a OpenWRT automated builder - Can "the OpenWRT Community" be a bit more open regarding the build process and what is being installed and executed in the process of generating builds?

The script settings are:


# Beware! This script will be in /rom/etc/uci-defaults/ as part of the image.
# Uncomment lines to apply:
#
# wlan_name="OpenWrt"
# wlan_password="12345678"
#
# root_password=""
# lan_ip_address="192.168.1.1"
#
# pppoe_username=""
# pppoe_password=""

# log potential errors
exec >/tmp/setup.log 2>&1

if [ -n "$root_password" ]; then
  (echo "$root_password"; sleep 1; echo "$root_password") | passwd > /dev/null
fi

# Configure LAN
# More options: https://openwrt.org/docs/guide-user/base-system/basic-networking
if [ -n "$lan_ip_address" ]; then
  uci set network.lan.ipaddr="$lan_ip_address"
  uci commit network
fi

# Configure WLAN
# More options: https://openwrt.org/docs/guide-user/network/wifi/basic#wi-fi_interfaces
if [ -n "$wlan_name" -a -n "$wlan_password" -a ${#wlan_password} -ge 8 ]; then
  uci set wireless.@wifi-device[0].disabled='0'
  uci set wireless.@wifi-iface[0].disabled='0'
  uci set wireless.@wifi-iface[0].encryption='psk2'
  uci set wireless.@wifi-iface[0].ssid="$wlan_name"
  uci set wireless.@wifi-iface[0].key="$wlan_password"
  uci commit wireless
fi

# Configure PPPoE
# More options: https://openwrt.org/docs/guide-user/network/wan/wan_interface_protocols#protocol_pppoe_ppp_over_ethernet
if [ -n "$pppoe_username" -a "$pppoe_password" ]; then
  uci set network.wan.proto=pppoe
  uci set network.wan.username="$pppoe_username"
  uci set network.wan.password="$pppoe_password"
  uci commit network
fi

echo "All done!"

what are all the packages installed along with the firmware? what is "dropbear" for example?

Do I really need that for a basic plain vanilla home network configuration?

@mmortal03 yes they are.

https://archive.openwrt.org/releases/23.05.1/targets/mvebu/cortexa9/packages/

there are several wifi firmaware packages of the same name and different sizes.

mwlwifi-firmware-88w8864_2023-04-29-6a436714-1_arm_cortex-a9_vfpv3-d16.ipk 86.5 KB Mon Nov 13 13:17:47 2023
mwlwifi-firmware-88w8897_2023-04-29-6a436714-1_arm_cortex-a9_vfpv3-d16.ipk 331.9 KB Mon Nov 13 13:17:48 2023
mwlwifi-firmware-88w8964_2023-04-29-6a436714-1_arm_cortex-a9_vfpv3-d16.ipk 218.9 KB Mon Nov 13 13:17:49 2023
mwlwifi-firmware-88w8997_2023-04-29-6a436714-1_arm_cortex-a9_vfpv3-d16.ipk 113.2 KB Mon Nov 13 13:17:51 2023

no they aren't

every name is different

And if your interest is actually in the thread topic, you should probably run master due to recent mwlwifi commits.

1 Like

A long list. It's been a few years.

There have even been bugs fixed between 23.05.0 and 23.05.2. Again, you may not even be affected.

I wouldn't modify the default packages unless you understand what you are doing. As you can see, the default packages show up on the firmware selector page by clicking on the arrow to the left of the line "Customize installed packages and/or first boot script".

I believe the only additional package on top of that, sometimes not included in test releases, is luci (the GUI) (which you also probably need), but it looks like it's at least included in the firmware selector for an official release. Again, I wouldn't remove stuff unless you know what you are doing.

It was to move OpenWRT forward to new bug fixes and features, just as every new major release.

I don't know what you're asking. I also don't work for OpenWRT, I simply keep tabs on this thread because it has had some relevance to my WRT1200AC.

This is not something you're going to be able to easily change. You really should just test the latest 23.05.2 vanilla build for your WRT3200ACM, and if you run into problems with that, try the latest master, like what @anomeome suggested.