I understand MikroTik does create own driver for wireless due to compatibility for Nstreme and so, but the driver from MikroTik is apparently delivers no way near to the speed offered from stock driver (normally offer 500mbps+ from most vendors who using stock driver like Netgear/TP-Link…) and having a hard time for roaming (IPQ4019 comes with Wi-Fi SON of Qualcomm which has amazing roaming capability, it’s been using in most of the mesh devices in the market) , I’m not sure how many user still using those unique wireless protocol since it seems still sruggle in Wi-Fi AC. In the past, it does earned good reputation for MikroTik in the era of Wi-Fi N, but in AC it seems only struggle, my mom always tell me if you can’t get it done, let it go. So, can we have 2 types of firmware which one for those unique protocol users and another for normal user, it will save your time to explain or suspect if any wrong with user config, since we all know most of the time it was causes by the crappy driver, you know and I know, so it’s time to face it.
+100 propietary chipset drivers are the best
Actually that is the plan for the future, yes. Can’t say when or where, but the general idea is similar.
Thrilled to hear that!! Thanks Normis
- 1
At last… Hope sooner than later.
I hope that’s in the v7 roadmap … not in v8 roadmap ![]()
Wow great news.
This will have a lot to do with moving to v7 on a 4.x kernel.
The main reason for the custom drivers with new chipsets would be likely due to backporting to fit the older 2.x kernel that ROSv6 is running on (i believe its 2.x)
Very excited for first official build of v7 with feature parity, so we can start to see development into newer features the new kernel allows.