4 ms·
I'm ashamed to admit that I was lazy this time, just used their FriendlyWRT build and then debloated. It's easy enough to disable all the packages, but a prope
by jacob019 4y ago
I'm ashamed to admit that I was lazy this time, just used their FriendlyWRT build and then debloated. It's easy enough to disable all the packages, but a proper OpenWRT build would be preferable and you could be more confident that it is secure. You should be able to apply the patches from their github repo and build your own OpenWRT image. It was easy when I did it for the R4S (now I think it's supported upstream). The OpenWRT build system is very nice and easy.
- btgeekboy 4y agoYeah, I’ve built FriendlyWRT for the R5S. It’s reasonably doable in an afternoon, depending on skill level. FriendlyWRT, or at least the sources for it, is just a few minor configuration tweaks for performance + default packages. http://wiki.friendlyelec.com/wiki/index.php/How_to_Build_FriendlyWrt http://wiki.friendlyelec.com/wiki/index.php/How_to_Build_Fri...
- jacob019 4y agoExactly, though I would rather restore the default OpenWRT package selection and branding. Hopefully the device support will land upstream soon.
- zokier 4y ago> The OpenWRT build system is very nice and easy In general I agree, it is pretty nice. The thing I'm struggling with right now is getting kernel config right as I'm attempting to do a build with 6.0 but the configs from OpenWRT-5.15 do not work directly with that (or I'm doing something wrong...). The difficulty is that the kernel config seems to be done in layers in a way, assembling and the merging the final config from different sources and its not completely obvious where to poke to make it work. I don't think its insurmountable, but just takes some effort to figure out the build system etc. Especially as I'm trying to do things the "right" way instead of just trying to patch up something bootable.