Recent content by xyzzy

I think what you want is called OpenWRT. The problem is without the support of the manufacturer and chip vendors, it doesn't have as good of hardware support. Like the NSS acceleration.

I did include ubiformat and ubiupdatevol from mtd-utils. It's not useful unless you want to try to manually recover from a broken ubi partition. Which can be done.

It is of course not always easy to disable something. Remove the link in /etc/rc.d so it doesn't start at boot, but then something calls the init script directly. Delete the init script. Something starts the daemon directly. Remove execute permission. Something adds is back. Delete every...

I would like it to not even be in the firmware in the first place. Nuke it from orbit as they say, it's the only the way to be sure. The sames goes for the AWS code. I don't need code that contacts Amazon on my router at all. Or that funjsq thing. That one looked like it downloaded a vpn...

If you were to read the next paragraph under the one you quoted, you would see I already noticed this mistake and corrected it. That's what I said. Netgear's fbwifi is compiled by gcc 4.6. I don't see a reference to gcc 4.6 in your firmware's version of fbwifi. Just gcc 3.0, 3.3, and 3.5...

Netgear uses openssl 1.0.2h for everything, of which I found 27 libraries and programs. One is libcurl, version 7.70.0, which is used by 4 additional programs. Actually, that's wrong. The fbwifi program is linked against 0.9.8, which isn't present as a file in the image. So it probably...

It's on github, so all changes are visible as commits. The difference is, it actually builds.

While 2.94.4 does contain OpenSSL 1.1.1n there are also two other copies of openssl in the firmware. It also contains 1.0.2u and 0.9.8p. So anything using those copies of openssl would still be vulnerable to the various exploits that apply to them. What's more openssl 0.9.8p that is included...

It turns out it's necessary to get the Atheros wifi firmware to make a working image. This is something that's been stripped from Netgear's firmware source release. But they left behind some references to a file with the firmware and some package names. Voxel also stripped this from his...

Jumbo frames were a thing when gigabit ethernet first came out. CPUs weren't fast enough to handle the packets/sec at gigabit with 1500 byte packets in their TCP/IP stacks and ethernet cards didn't have features like interrupt coalescing to reduce IRQ load. But that was only for a bit. Nobody...

I've adjusted the docs to correctly describe the NSS firmware. I also wrote a program to extract it from a R7800 firmware image and automatically made a "source" tarball for building with. This is pushed onto the repo described in the OP. It's still on .93SF because Voxel hasn't released...

Languages look like they are saved into /dev/mtd10. It's raw flash with no filesystem. It looks like it has a 2-3 letter language code, a new line, and then a tar file with one file inside, named language_table.tar.gz. My flash has six of these, Eng, SP, PR, FR, GR, and IT. The...

I wanted to build Voxel's R7800 firmware myself, so I could include a couple extra utilities to help recover the flash. But it didn't build without quite a bit of work. So I put everything I did here, on a github fork, https://github.com/xyzzy42/R7800 This should be able to build with just...

Thinking about this more, I don't think it's the switch, or at least not the switch the way I was thinking. It looks like there is only a problem with WAN performance. I don't think the switch connects the LAN ports and the WAN port. The traffic between the two has to go though the SoC since...

No I did not. I said the "software you used to look at the image", that would be 7zip, might have managed to find the squashfs partition. But that does not change the fact that the firmware image is not "just a zip file". It is a 128 byte header that's text, then a uboot image containing a...