If I understand the current state of the txpower issue, it is a known issue without a fix in sight.
I'll keep on debugging ath11k on my end, but I'm not sure if the issue is fixable/identifiable without binary (ath11k firmware / bdwlan) intervention, which as I understand, requires closed sourced tools.
If anyone can contribture to this discussion, I would appriciate it, as currently this is a blocker for me, and perhaps others.
I now need to update from my initial install of r22497-f25abdf144 (135 days, and not missed a beat) and I'm concerned that I don't understand what affect the rename of the target from ipq807x-generic to qualcommax-ipq807x will have on running an Attended Sysupgrade. I'm a couple of hours drive away from the router, so I'm understandably reluctant to just give it a go!
Will it still work, or do I need to upgrade in some other way?
and the working USB drive containing the initramfs file you used when originally installing OpenWrt
system backup
As your using an older snapshot, you'll end up getting an updated snapshot using the ipq807x/generic platform. FYI:
1/ if you want to continue using the latest snapshot (ipq807x/generic):
use Attended Sysupgrade (ticked: Keep settings and retain the current configuration)
2/ if you want to get onto 23.05.0-rc3 (ipq807x/generic) or latest snapshot (qualcommax/ipq807x):
use the firmware selector to create an image, adding your packages manually by selecting: Customize installed packages and/or first boot script >paste packages under Installed Packages > REQUEST BUILD
(An easy way to find the minimal packages required to meet your current setup, copy the packages listed in the Packages column within Attended Sysupgrade GUI, then paste into relative section above)
once complete choose SYSUPGRADE button to save the image
use the standard GUI sysupgrade path (ticked: Keep settings and retain the current configuration)
I’m fairly certain using ASU will not retrieve the qualcommax updates since the target has switched. The rest of the guidance using the firmware generator is sound however - and I would advise using that to migrate to either the newest stable RC or Master images. Once there and on qualcommax, then you may resume ASU if desired.
To my knowledge 23.05 will remain as ipq807x/generic while in master it is renamed as qualcomm/ipq807x.
So, jumping between master and 23.05 builds will not be possible via ASU.
@rmappleby's using a snapshot so will continue to do so while using the Attended Sysupgrade GUI.
Current snapshots use the qualcommax/ipq807x platform.
Yes - they do - but ASU is simply running down the same tree looking for an upgrade (meaning the generic tree). Since it has moved to qualcommax, it won’t find any and report running the latest firmware. Once migrated to the qualcommax tree, it will then continue working as intended as it is now looking down that path.
So, 23.05 remains as ipq807x/generic, and Master becomes qualcomm/ipq807x. So I guess the question is, when doing an ASU on an existing SNAPSHOT build where does the build come from? It would seem logical (to me anyway) that it come from Master, which would imply I get switched to the new target.
... so I would still be on target ipq807x/generic. But look at the Build Date - 14th June 2023. Is r23375 current for a snapshot or was that what was being produced on the date that the changes to the target were made?
So I'm starting to think an ASU is NOT going to give me the result that any of us expected, and I may need to do the firmware generator thing.
I think it will offer me an upgrade to the last snapshot for ipq807x/generic, which will be around the day the changes to the target were made. I wont be able to ASU past that. See my "other" post, in reply to hnyman, which seems to corroborate that. I think I'm going to have to do the firmware generator.
Its things like this that remind me how good OpenWRT is compared to proprietary offerings
I merged the "standard" set of modules that the Firmware Selector suggested with the set of modules I was actually running, and built my new firmware. I decided to go with the qualcommax/ipq807x target and stay on snapshots for now. The Sysupgrade image built without error, so I transferred it to the router, crossed my fingers and pressed update...
I just set up my new DL-WRX36 a few days ago and I used it as a drop-in replacement for the Netgear WAX206 with OpenWrt that we used as our main router before.
Since then I regularly faced issues with my Samsung S21 mobile that it showed that there is full WiFi but without Internet. I'm using 23.05.0-rc3 with the default firmware, package steering is off, Multi To Unicast is on.
After switching back to the WAX206 everything works smooth again and I also recognized that the WiFi signal of the WAX206 seems to be stronger than the one of the DL-WRX36.
Does anyone have any ideas what the problem could be? I didn't have much time to investigate it further so far because I was quite busy installing our new photovoltaik grid on our roof during the last days.
Poor internal antenna design and/or an immature WiFi driver?
Used as an AP for mid to long WiFi ranges, my Belkin RT3200 outperforms the DL-WRX36 I've stored in a closet as a spare. If I needed a gateway router for Gbps+ ISP service and close in WiFi coverage, the RT3200 would be in storage instead.
Okay, thank you, I will switch to the same firmware and check what happens. At the moment I am not even sure if the issue is limited to my mobile or not.
I tested 802.11ax WiFi throughput using iperf3 on a stationary linux thin client with an ax200 2x2 card, but I too used WPA2 CCMP (AES). I also used an R4S as an iperf3 server and swapped each AP into the same location with the same configuration to keep things as comparable as possible.
, however I'd make sure you have a backup plan, just in case things go pear shaped!
