After flashing latest divested on both boot partitions and no issues, i tried again to install OEM and still no cigar!
I just get a local 169 address with the power light and lan light on. To me it seems like the firmware is not loading and its "stuck in limbo" of sorts. It wont respond to holding the reset button for 10sec and switching it on and off it just blinks on light a few times then lan light comes up but thats it.
Maybe try going backwards (21.x, 19.x) and from there to OEM; I presume you will have to use a factory image due to the partition sizing change on that device.
1 Like
I gave up on it last night and tried again today
isn't the factory image:
?
or have I missed something. Also I just tried it on the second wrt32x router and the same result.
Download 19.07 factory.img from https://downloads.openwrt.org/releases/19.07.7/targets/mvebu/cortexa9/openwrt-19.07.7-mvebu-cortexa9-linksys_wrt32x-squashfs-factory.img
This should revert the partition sizing change on the device. From that partition you should be able to restore OEM firmware.
1 Like
OMG man you're a champ
thanks heaps for that. Just got it back to stock now after patching to 19.x firmware you pointed 
Don’t forget to flash the alternate partition with the OEM firmware to make it fully stock.
1 Like
@SkewedZeppelin You use some script for your compilations?
I tried to use all the packages used by you and plus other packages and I get two errors every time in the Snapshot version:
[1]: failed to create listening socket for fe80::1%pppoe-wan: Address not available
Tue Mar 29 09:20:10 2022 daemon.warn dnsmasq[1]: failed to create listening socket for fe80::1%pppoe-wan: Address not available and `daemon.err nlbwmon[21812]: Netlink receive failure: Out of memory`
`daemon.err nlbwmon[21812]: Unable to dump conntrack: No buffer space available`....
All your versions firmware work without these errors, what should I do to get rid of these errors, how are they not solved?
Hi all guys
Firstly, thanks to Skewed and all contributors for keeping the wrt devices alive.
I just discovered this thread and i'm reading it with lot of interest
I'm going to enable soon a 1G/200M ftth line, and they should provide me an ONT for it
I was wondering if my wrt1900acs will be good enough to serve my needs, and trying to figure out the best way to flash & configure my device, as soon as i'll lbe able to get my wrt back from the relocation boxes 
Thanks again
Soon
Having an issue with the latest builds, I did a clean install recently and noticed that upnp is not working on any of the provided builds.
I did a clean install with wiped configs, enabled upnp via the web gui and nothing happens, the list that use to populate remains empty and the ports remained closed. I checked /var/run/miniupnpd.leases and see it getting populated.
Any ideas on what to do?
First of all, thank you so much @SkewedZeppelin for your hard work, I want to test your builds and I've been taken a look to your instructions and your tutorial in video about how to compile and update the builds, but I have a few questions (because my listening isn't the best and without subtitles...):
Why do you change the order of the commands ("make download -j4" and "make nconfig"), and you change in your video the last command make download -j16 for -j14, why???
Other question, it's about the patches, I know that I don't need to use all of them, but before use them, I need to know which is the purpose of each of them, is there a way for a newbie like me to know this?? or is there some place or link where can I consult their purpose, I can imagine this is a newbie question, but I want to learn to compile images by myself.
Again, thank you so much for your hard work, tutorial and help, this is a great community, regards.
EDIT: One more question, why there are patches for kernel 5.10 and 5.15??, I've understood that the default kernel is 5.10, maybe, for people that want to use 5.15??
download and nconfig can be run in either order as long as the config isn't really changed.
For the threads (-jX) it can be faster to use fewer threads for downloads, and is best to use as many as you have for the compile.
For the kernel tweaks, I applied it to 5.4 and 5.10, and when 5.4 was replaced with 5.15 I just applied the changes there. As of recently you can compile 5.15 for these devices, but it isn't default yet. I think there is still an issue with vlan handling? I need to double check.
1 Like
You have to go back to 19.07 before going back to stock.
Its due to the kernel resize
The 20220917-00 update adds support for many mt7621 devices as I recently learned of the WAX202 and its very appealing price.
https://divested.dev/unofficial-openwrt-builds/mvebu-linksys/20220917-00/ramips_mt7621/
Question:
I give up on upgrading from the Davidc502 r13342 snapshot on my WRT3200. Seems like Linux kernel 5.4.42 is the EOL for this router as far as stable WiFi connections. I've tried every suggested WiFi settings.
I also have a WRT1200 and 1900 stored away. Both ACS v2.
Would I have any better luck upgrading either of those routers? Thanks
My 1900ACSv2 and 1900ACv1 are largely stable for Wi-Fi as configured like the template: https://divested.dev/unofficial-openwrt-builds/mvebu-linksys/templates/etc/config/wireless
r13342
I can't actually imagine using something that old from a security standpoint.
2 Likes
Does wrt32x support multi_cpu with dsa yet? I find my routers max DL is much slower with DSA in v21.02 branch. Before I could hit 980MB now I get mid 650MB (assuming its due to single CPU support).
@dk4dk4
I haven't followed it closely, but I don't think it was ever merged/enabled for these devices.
My 1900ACS is a v2. I think I'll dig it out and give it a try tomorrow.
Security standpoint? What would be the biggest threat? If it's WiFi...I'm out in in a rural area with one close neighbor who uses ISP equipment and not very tech savvy. Not much of a threat.
I use Linux for my computer and it's locked down privacy-wise.
r13342 is https://github.com/openwrt/openwrt/commit/e35e40ad82 from May 23, 2020
That is likely at least vulnerable to these
- https://openwrt.org/advisory/2020-12-09-1
- https://openwrt.org/advisory/2020-12-09-2
- https://openwrt.org/advisory/2021-01-19-1
- https://openwrt.org/advisory/2021-02-02-1
- https://openwrt.org/advisory/2021-02-02-2
- https://openwrt.org/advisory/2021-08-01-1
- https://openwrt.org/advisory/2021-08-01-2
And likely many others, like these
2 Likes
Short answer - NO. Nothing to my knowledge has been accepted upstream.