Thoughts on the possibility of a port to the RBK20 ("Orbi Mini")? about orbi-rbk50 HOT 3 OPEN

On Sat, Mar 28, 2020 at 4:54 AM Geoff Nixon ***@***.***> wrote: Hey there! So, I got myself an Orbi "Mini" at Costco last week, and while the hardware seems solid, well, lets just say there's a lot left to be desired with regards to usability (i.e., a functional dual stack IPv6 implementation would be a GREAT start...). A bit of digging on what could be done brought your work to my attention; it looks like you've put a lot of time and effort into putting together this lovely alternate firmware package. So I thought I'd ask if you'd be so kind as to give me your thoughts on how feasible (in terms of time and effort) to fork and port your RBK50 firmware to the RBK20. My initial (probably naively optimistic) thought is that it might not be too much of a slog—while I'm not sure they use the *exact* same chipset, grepping around the libtool .la files in the filesystem leads me to believe they're at least both Cortex-A7 based, and they have the same amount of RAM storage. I dumped (in the crudest tar c - / | nc ... sense) the filesystem of my device <https://github.com/geoff-nixon/RBK20> (stock firmware V2.3.5.30), in case poking around there might be helpful. (I do realize there may be some semi-sensitive data there as well as perhaps some gray-areas in re: copyright, so I don't leave that repo up for very long). To be clear, I'm not asking you—unless, of course, you want to, in which case, fantastic ;) —to create and maintain support for yet another device, just for me—I'm more than willing to set up the build system and toolchain and do as much of the grunt work of producing and testing builds, etc. Its been a few years since I've done the Linux From Scratch thing, and it might be nice get a bit familiarized with today's embedded systems. Of course What I *would* need help with most likely, would a bit of handholding/pointers on which scripts and config files I'd need to look at, problematic packages that might need a deeper dive/patching, etc. , f you'd be willing. To tell the truth, it seems I'm jumping the gun again... my only *real* question at this point is whether a port is, in your opinion, workable and feasible. By which I mean, something that you think this could be something done in a matter of weeks, not months or years, and not a fools errand entirely, for some obvious reason I have missed). Thank you for your hard work, and I appreciate your time and knowledge! · Geoff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGASXWXFMTJF6OJY6ZMTNITRJVKGRANCNFSM4LVMXFYA> .

On Sun, Mar 29, 2020 at 2:35 AM Geoff Nixon ***@***.***> wrote: Thanks for the advice Voxel. I definitely hear you. Can you point to a tag or commit that best represented your "reconstructed" source (prior to subsequent tweaks), and a link to the correspondent version of the Netgear source/build to diff it against? Having said that I'm probably leaning towards simply cutting my losses and getting a better device. Of the devices you do support, do you have a favorite (preferably one that's not absurdly expensive)? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGASXWXSWDYDJLT6STA6Q3DRJ2CVTANCNFSM4LVMXFYA> .