I was hit by this bug, which led to my sysupgrade from 24.10.3 to 24.10.4 failing to keep my config, even though I checked the “keep config” checkbox. Router resetted itself to default. With my backup corrupted (the bug affected both LuCI backups as well as manual backups via sysupgrade on the terminal - so all my config backups were unreadable!), I therefore had nothing to lose anymore and did a fresh reinstall to get rid of the bug. Which is bad for me, but good for you!
I can confim the following for 24.10.4 (latest stable):
- one network per radio (2.4 GHz / 5 GHz / 6 GHz) works fine
- two networks per radio works fine
- three networks per radio leads to radio 2 (6 GHz) disabling all of its networks
My workaround is to use a 3 networks / 3 networks / 1 network configuration, but that’s a workaround not a proper solution. 3 / 3 / 2 does not work.
Observations with workaround:
- After reboot and/or restarting of radios, it can take up to 60s for all networks to leave "disabled" status.
- After reboot, in around 80% of cases, radio0 sets all networks to disabled permanently; so radio0 needs to be manually restarted after every reboot. In around 20% of reboots, everything works fine.
On a different topic, I can also confirm the defaults for the following settings:
Default for /sys/module/pcie_aspm/parameters/policy is "performance".
Default for /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor is "userspace".
So my rc.local config posted here works in 24.10.4 stable as well. There was a substantial improvement from -68/-75 dBm to -66/-79 dBm, so my SNR went from 7 dBm to 13 dBm. If I’ve got my math right, this means an improvement factor of x4, due to the logarithmic nature of the unit.
The culprit is /sys/module/pcie_aspm/parameters/policy is "performance" –> set to “powersave”.