Hello good folks! I have an old WD My Net N750 that I'd like to repurpose and I've read that best feature rich (WOL, USB, UPNP, DDNS etc.) builds to start with are from mk13139 but I can't seem to find live links since those builds are pretty old. Can anyone help me out?
There is no ar71xx anymore.
But the WD My Net N750 seems to be supported, https://openwrt.org/toh/western_digital/my_net_n750 (I'm not sure if the warning is still current, so check the link).
Thanks for the quick reply. I can confirm that it is supported and I've already installed it. I'm looking for a build that already has everything I want to use in it hence my asking about the mk13139 builds. I can't find one anywhere. Guess I might just have to install all of the packages myself then.
The number one priority should always be active security support, so 24.10.4 (or better). Everything else can just be added (be it at runtime via opkg/ apk or before flashing via the (online-) imagebuilder). Not merely (but also!) because of security, but just to 'fit in' (support for recent security ciphers, CIFS versions, etc.).
I have a lot of N750s in service running version 24.10.4. I do not run LuCI, because there is a bug affecting storage. I'm not sure if it's been resolved.
They work as gigabit switches and 802.11n APs.
I believe I drafted the orginal warning, if not that one. It is still current.
Thanks for the Info guys.
"Warning: 21.02, 22.03 and development snapshots do not work properly at this time. (Sep 2022)." would suggest to me that 23.05.x, 24.10.x and main snapshots would also be broken (because it mentions snapshots with a 2022 date). Great to hear that 24.10.x is working, so the warning would ideally be changed to warn only about 21.02/ 22.03 and to give green lights about (or just luci specific advice) for 24.10.x and up.
Ummmm...except this part:
The others "worked" too with the same issue. Downloading/using an official firmware without the modification causes the issue.
I can test a device at my next opportunity. Given the issue soft bricks the device, I have to wait until one is safely on my test bench.
Reviewing the thread would be helpful.
It's discussed that there are jffs errors with firmware that approximately larger than version 19. Hence using a custom OpenWrt without the web GUI would solve the size problem (this is where Slh noted the Wiki warning mentioned snapshot).
The issue could also appear after altering settings. A work around was to backup the configuration and restore it as the full archive.
Again, reviewing the thread I linked would be best.
I see you flashed version 24 with a web GUI - make sure the log doesn't show filesystem errors.
The log shows these errors.
Sat Nov 22 05:15:31 2025 kern.notice kernel: [ 34.457183] jffs2: notice: (589) check_node_data: wrong data CRC in data node at 0x0014fc40: read 0xe8f826a9, calculated 0xfa0b802e.
Sat Nov 22 05:15:31 2025 kern.err kernel: [ 34.626447] jffs2: error: (589) jffs2_do_read_inode_internal: CRC failed for read_inode of inode 916 at physical location 0xab054
Sat Nov 22 05:15:31 2025 kern.warn kernel: [ 34.641786] jffs2: Returned error for crccheck of ino #916. Expect badness...
Sat Nov 22 05:15:40 2025 kern.notice kernel: [ 46.584185] jffs2: notice: (589) jffs2_get_inode_nodes: Node header CRC failed at 0x310e30. {19ff,e002,10ff02b2,d2ff1795}
Sat Nov 22 05:15:40 2025 kern.notice kernel: [ 46.967047] jffs2: notice: (589) jffs2_get_inode_nodes: Node header CRC failed at 0x3107f0. {79cf,e002,714f0392,f17f061c}
Sat Nov 22 05:15:43 2025 kern.notice kernel: [ 49.758822] jffs2: notice: (589) jffs2_get_inode_nodes: Node header CRC failed at 0x717f88. {3def,e002,346f05b2,bd6f8152}
Sat Nov 22 05:16:08 2025 kern.notice kernel: [ 75.078944] jffs2: notice: (589) jffs2_get_inode_nodes: Node header CRC failed at 0x70b5d4. {6f6c,ffff,0000003e,539fc0cc}
Sat Nov 22 05:18:28 2025 kern.notice kernel: [ 94.455612] jffs2: notice: (589) jffs2_get_inode_nodes: Node header CRC failed at 0x718690. {3def,e002,346f0308,f4ef7c46}
Sat Nov 22 05:18:28 2025 kern.notice kernel: [ 94.556492] jffs2: notice: (589) jffs2_get_inode_nodes: Node header CRC failed at 0x71853c. {3def,e002,346f0152,7d6fa62e}
Sat Nov 22 05:18:28 2025 kern.notice kernel: [ 94.706207] jffs2: notice: (589) check_node_data: wrong data CRC in data node at 0x0028e724: read 0x136afd5b, calculated 0x7644a8d4.
Sat Nov 22 05:18:28 2025 user.notice firewall: Reloading firewall due to ifup of wan (eth0.2)
Sat Nov 22 05:18:29 2025 kern.err kernel: [ 95.824874] jffs2: error: (589) jffs2_do_read_inode_internal: CRC failed for read_inode of inode 1395 at physical location 0x558d38
Sat Nov 22 05:18:29 2025 kern.warn kernel: [ 96.226460] jffs2: Returned error for crccheck of ino #1395. Expect badness...
Your device is experiencing the issue. Ensure you backup your configuration if you've made any.
BTW, in the future when posting output, please paste the output using the "Preformatted text </> " button:
