cmkelley
Very Senior Member
Wow.I'm really shocked - or maybe not - that there is no action with this what so ever. It's almost like the developer of the Merlin firmware is ignoring this is a problem, or he is too scared to fork his firmware off of the official Asus firmware in fear that it may actually fix stuff Asus can't. Would have thought with a custom firmware that meant that the developer would actually put forth effort into making sure it's better than the OEM stuff, but maybe not? Does the developer of the Merlin firmware even watch this forum? Can anyone reach out to him? Can he contact me so we can troubleshoot this issue in the firmware together - I know a lot about Linux I can provide some insights. I'm going to pull it off github now @ https://github.com/RMerl/asuswrt-merlin.ng - to see if I can find what's going on myself maybe.
I'm really shocked - or maybe not - that someone would have the utter audacity to complain so vociferously about something they're getting for free, and then insult the developer on top of it! If you had bothered to look around at all, you'd know that the developer is ONE person, doing this in his spare time, for no more than whatever few dollars people throw at him through his paypal link. He supports a large number of ASUS routers, which are not all the same platform, each with it's own peculiarities. He is VERY much active in these threads and is very responsive when you can provide a definitive, reproducible issue starting from a known clean state. It's clear you just came in here and started spouting off without even doing one iota of homework.
Funny how pretty much every time someone declares a bug in the firmware that isn't already well-known, if and when they finally get convinced to reset to factory default and start from fresh, the problem goes away. AFAIK, all of the known bugs are in the closed-source binary blobs provided by ASUS that Merlin has zero control over, c.f. the dcd crash in AC86 routers. By the way, that's a pretty good chunk of the router firmware, such as, but by no means limited to, all the TrendMicro stuff and the wireless that are completely closed-source. But like I said, you'd know that had you bothered to do a minimal amount of investigating.
Don't you think that if there was repeatable problem with Merlin's firmware on the AC3200 more than just you would have encountered it by now? My AC3200 currently has 72 days of uptime with 172 MB free (i.e. 30% memory "used"), and CPUs running from 0 to 5%, no signs of sluggishness nor any of the issues you've declared to be bugs in Merlin's firmware. So there's no magic 32 day bug bringing your router down. And as far as I can tell, you've blamed it on Merlin's firmware without even seeing if it's reproducible in the stock firmware.
If you're all that and a bag of chips with Linux, by all means, fork the firmware and show everyone what a great coder you are. All of Merlin's code is GPL, so you're free to do so. Good luck with that.