There are now several people just in this thread wanting Mikrotik to support the i225-v directly. We don't I don't understand why you seem to be against it. It could 10 years again before a newer kernel is used, or this time it could be a little sooner.
Apparently the current kernel is from (just) before the i225-V support, and now the users of that card are out of luck. I do not know if it is much easier now, and how often they are going to do it now. It took like 10 years between v6 and v7 to change kernel version once. It would not be that unrealistic when they just get the "default kernel" with all included drivers compiled as modules and replace that once or twice a year.īut apparently they do a lot of other kernel patches for RouterOS and it is a lot of work to re-do those every time. Also, nowadays the virtualisation has become so effective the difference in speed for I/O barely is measurable compared to a regular installation.īottom line, make use of CHR since it makes all much easer, both for the end user and MT as a developer. However If you instead virtualise it all, you put the entire responsibility on the hardware manufacturers for operation and maintenance of device drivers. It means a huge undertaking to constantly sort out what public available hardware to support and commit to long time maintenance of related device drivers which is unrealistic for a company like MT. What I'm trying to say is that if you need to support "bare metal" installation for a ROS Appliance it's like any regular installation of Windows or Linux direkt on hardware. I'm not against anything but maybe we just talk past each other. We are just asking Mikrotik to support the i225-v directly, don't put more into it than that. Also to me it still seems that Mikrotik are actively developing the x86 version, just see latest stable release with support for new NICs, fixes, etc.
I don't understand why you seem to be against it.
0 kommentar(er)
