By any chance do you still have the snapshot? I got my DL-WRX36 last week and I have the same wifi disconnect/performance issues as well on the latest snapshots
it's long time gone, sorry.
Am I the only one facing issues with mesh and wifi configuration?
I am getting "Wireless is not associated" in the wireless page on some configuration changes. and after upgrading to a recent snapshot (r24929-5485d27f4d)
Haven't dug too deep or checked the logs but just checking if anyone else faced the same issues.
Maybe is like this? https://github.com/openwrt/openwrt/issues/14575 there is a patch to fix the issue.
1 Like
That seems to describe the same issue and configuration I have.
Thank you for reporting the issue. 
Great to know that I'm not the only one!! If you test the patch (is only change one line in one file) please report at the issue.
I can confirm that changing the following file fixed the issue. 
/usr/share/hostap/common.uc
It's on master, so simply building latest master fixes the issue 
If I was to order this from US, what plugs are included? This router was sold in UK up until start of 2023 but it seemed to have completety vanished. Been out of stock since what appears March 2023. Almost a full year.
I bought the device from Amazon USA a year ago, and it had the just US power plug included (as warned on the device page). I had to buy locally a 12Vx3A power adapter with a DC plug suitable for the device (possibly a 5.5/2.1 mm or 5.5/2.5mm DC plug)
I also bought from Amazon US and got the US power plug but the power brick itself can operate at 240V so the only thing I needed was a 50 cent adapter from the flat pin US to the round pin Europe style
1 Like
I'm waiting for my new WRX36 from Amazon, getting ready to install OpenWRT.
I usually only install the latest release (23.05.2 in this case), but the WRX36 page says "Due to this device being under development, users may want to install main snapshot images built daily instead"
Considering I want a stable build more than performance or cutting edge features, should I install stable or snapshot?
I recently installed using the stable build of 23.05.02. It has been running solid with no major issues for over 2 weeks now. The only thing I have noticed is that when plugging in via wired connection ( laptop for management ) DHCP seems to take a little bit longer than expected on this device. ( Specifically, compared to when plugging in to other model devices running OpenWRT. )
There are a couple of things you might run into during the install. I detailed my install experience here:
2 Likes
23.05.x is the first stable release sporting ipq807x support, so that advice probably hasn't been updated yet. However, due to the ipq807x --> qualcommax/ipq807x target rename, if you already are on snapshots (using that target name), it might be more sensible to stick to that and switch to 24.xx.0 once that becomes available (forcing the target rename isn't difficult, but contains some risk).
3 Likes
Thanks! I have not installed anything yet, and I'm inclined to install stable (23.05.2).
Are you saying that if I install stable with the "old" ipq807x/generic naming, it's going to be more difficult to update to 24.xx in the future? Worst case I can always back up the configuration, install from scratch, and manually recreate the same settings (I assume)
Or am I missing something? I'm still very new to OpenWRT
In that case, go with your gut feeling and 23.05.x.
"Difficult", as in "hard", no - you 'just' have to force the sysupgrade (-F), but as that does require some attention to details (and redoing the configs) - and most of all, as it bypasses sysupgrade's sanity checks, this does contain a non-zero risk of things going south (if you don't flash the correct firmware image, but -e.g- a photo of your pet hamster via sysupgrade). This procedure will come to the radar of anyone upgrading their ipq807x devices from 23.05.x to 24.xy.z (or snapshots), so it's to be expected, but it does need some attention to detail. That's why the risk averse part of me suggests those who already are on qualcommax/ipq807x snapshots to stay on (updated-) snapshots, rather than to go back and forth (snapshots --> 23.05.x --> 24.xy.0) between the two differently named targets.
If flashing 'untested' snapshots regularly or forcing the sysupgrade twice is a bigger risk in the long term, would be a matter of perspective (and the optional USB recovery of this device certainly also helps).
The decision is yours, both 23.05.x and main snapshots should work fine.
2 Likes
Got it, thanks. I think I'll go with 23.05.2, then, and enable USB recovery to prevent bricking when updating to 24.xx
Note that it is the USB recovery which needs another filename as the initramfs file is also renamed.
But implementing USB recovery is highly recommended, saved me once 
Yes, I noticed that, thanks!
I'm assuming you are talking about this
fw_setenv openwrtusb 'usb start && fatload usb 0:1 0x44000000 openwrt-ipq807x-generic-dynalink_dl-wrx36-initramfs-uImage.itb && bootm 0x44000000'
If the update to 24.xx fails, I can either reuse the old 23.05.2 USB (which I plan to keep) or copy the new 24.xx initramfs to the USB and rename as the old. Either way, I should be able to get back from a mistake in the 23.05 -> 24.xx update
1 Like
I finally got my WRX36 and easily updated to OpenWRT, thanks everyone who helped create clear, easy to follow instructions.
I also enabled the USB recovery option, and I wanted to test if USB recovery worked. Using logread, I found this when booting from USB
kern.notice kernel: [ 0.000000] Kernel command line: root=/dev/ubiblock0_1
and this when booting from flash
kern.notice kernel: [ 0.000000] Kernel command line: console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait root=/dev/ubiblock0_1
Please note that the Wiki says
fw_setenv bootcmd 'run openwrtusb; run openwrtboot'
fw_setenv openwrtboot 'setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm 0x44000000#config@rt5010w-d350-rev0'
fw_setenv openwrtusb 'usb start && fatload usb 0:1 0x44000000 openwrt-ipq807x-generic-dynalink_dl-wrx36-initramfs-uImage.itb && bootm 0x44000000'
But that is valid only for the snapshot image, if using stable 23.05.2 the USB initramfs filename is different (I missed that originally, and USB recovery didn't work, obviously)
1 Like