Clark Griswald
Very Senior Member
BoatloadYeah, that's a boatload of fixes... hmmm...
I wasn't concerned, until Boatload size was reached
BoatloadYeah, that's a boatload of fixes... hmmm...
I suppose ignorance is Bliss... I'm just gonna ignore everything LOLBoatload
I wasn't concerned, until Boatload size was reached
Thank you Eric. What you said makes me think that the legal issues have already been addressed by this cleanup process.Won't be a problem. I did receive a first cleaned up GPL archive a few weeks ago for one specific model, and it was fully buildable. That's part of why it's taking so long to get cleaned GPLs, Asus's engineers need to ensure that it's still buildable. That sometimes mean rewriting some Makefiles.
Some GPL-troll? Stallman devotee? Seems that this person(s) is/are doing it deliberately.all licensing issues are resolved to the satisfaction of the complainee.
I also endorse AX68 wholeheartedlywhole-hearted endorsement of the AX68
Personally, I would rather have the Merlin firmware without the Trend Micro software. The black box of Trend Micro SW is probably as or more concerning than the alleged benefits it provides.I would bet it's Trendnet getting their knickers in a twist over 3rd party firmware installs for non Asus routers and not Broadcom's fault.
The reason I say this is that most of the Broadcom stuff is already out in the wild if you know where to look and would be impossible to kill now.... Why would Broadcom complain about this leak when there are countless other leaks. If you take AsusWRT-Merlin firmware and stick it on a netgear router you are just taking broadcom software from 1 router and replacing it with nearly identical Broadcom software.
Trendnet OTOH, I don't know much about their stuff because I try to stay away from entity's like them. But it seems to me they sure do like their IP, and rightfully so. Since Trendnet is not included with Netgears, then taking it from Asus-Merlin and putting it on netgear is something that never suppose to happen. It's their IP they can dictate whatever they want. I have no problem with that.
But I do have to ask myself, did Asus pay Trendnet to let them include their stuff in Asus's firmware, or did Trendnet pay Asus to put their stuff in Asus firmware? Neither would surprise me as I can imagine both benefit from the deal.
Maybe I am wrong, maybe not. Maybe it's both of them LoL. Either way I don't fault them for trying to protect something they made
Does anyone know if you can compile the firmware without the Trendnet stuff? Obviously compiling without the Broadcom bits would not work so well. At that point you might as well install OpenWRT on it and ignore the wireless bits and use it as a wired only router (which I did on an AC68U btw and does work beautifully - you folks would not believe how much samba performance improved, hint, it tripled!!) but you lose WiFi for good.
Yeah, would love to know how they prioritize those... but I think the concern (for me) would be anything immediate/zero day that is super critical like a Meltdown or Spectre. But if I'm honest, I'm likely too lazy to revert and would just continue rolling with the Asuswrt-Merlin build.Someone expressed concern some days back about reverting back to Asus official firmware in order to be current on patches for security vulnerabilities. Well, looking at the latest RT-AX68U release from Asus, there are security patches that were released 6 years ago that Asus did not apparently provide until yesterday. The average age of the patches is about 3+ years. So if anyone is counting on the stock firmware to keep them current on security patches, that myth has been busted.
Ditto. I would also stick with the Merlin build as it has features I use not available in the stock firmware. As food for thought, many of the vulnerabilities require access or events that are unlikely to happen in real life. And in some cases the fixes for the vulnerabilities either don't work or cause unwanted side effects. Intel rolled out 3 or 4 microcode updates for Spectre before getting it just so. And that was an extremely high profile vulnerability.Yeah, would love to know how they prioritize those... but I think the concern (for me) would be anything immediate/zero day that is super critical like a Meltdown or Spectre. But if I'm honest, I'm likely too lazy to revert and would just continue rolling with the Asuswrt-Merlin build.
really sad to hear this FW might be coming to an end I've been using it from close to day one . Whatever happens thank you for the years of great solid secure FW . And good luck whatever you do in the futureAnd some of these fixes have been present in my firmware for months already, like all of those related to curl or OpenVPN.
really sad to hear this FW might be coming to an end I've been using it from close to day one . Whatever happens thank you for the years of great solid secure FW . And good luck whatever you do in the future
And some of these fixes have been present in my firmware for months already, like all of those related to
Not sure why some are inferring that the AsusWRT-Merlin project is coming to an end. I don't have any inside knowledge of the Asus situation but my understanding of the posts is that:really sad to hear this FW might be coming to an end I've been using it from close to day one . Whatever happens thank you for the years of great solid secure FW . And good luck whatever you do in the future
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!