It is legit. Both of mine and many others had some sort of oil on the heatsink. Just part of the manufacturing process from all I’ve seen and heard. As for the firmware, this is normal too. The lower one is what comes installed by default and 7.6 was the latest stable at the time your router was produced. No issues. It’s not fake. Have fun with your new RB5009.
5009 really is a great device. I just wish it had at least 2 if not even 4 GB of RAM. I added Unbound with Adguard with 890.000 adresses to block and i only have 400 MiB of RAM left. Not sure if i can add transmission on top of that without causing problems.
It’s a router with a low power ARM SoC. Adding ram to use it to run multiple servers won’t make it a better/more secure router. I really don’t get why these posts keep appearing - a humble Pi can do this much more efficiently and without risking issues with a critical network component that most people can’t replace at this point if something goes wrong. And if you need power, a cheap Intel based appliance will do so much more for your money.
The Pi was my recommendation for the DNS sinkhole, not for torrents. However, that seems low bandwidth for a Pi 4 over USB, which is reported to reach around 500-600 MB/s. Maybe it’s the adapter you’re using - try another external drive if you have one ? Regardless, having dedicated devices is the way to go for best performance, safety and longevity of everything in a 24/7 scenario.
As i read, it’s the encryption problem, because RPI CPU doesn’t support encryption(not realy sure if that is real reason). It simply won’t DL faster than that.
For DNS everything works, i’m realy satisfied with 5009 performance in that aspect.
There’s definitely a limit to how much “non-router” software you should be running on your Mikrotik router, but without containerisation there would be so much lost potential with routers being Linux-based… Especially on CHR/x86 & SOHO deployments where you need to run something simple on site while maintaining simplicity/minimal footprint, and working within low budget constraints etc. As weird as it can seem seeing all these exotic and ambitious container experiments being done on what technically should just be a “router”, going without containers is definitely a regress in my opinion. I know I for one would be be mortified if the feature got revoked. I’ve already spent a lot of time building exciting new infrastructure around this welcome new feature and it feels like it’s only the beginning! For sure Mikrotik have unlocked a world of potential & opportunity for us with this one for which we can only be grateful