Proper file to easily install it in VMware ESXi without having to fiddle with VMware workstation or other tools.
(either the correct .vmdk file or a .ovf file)
The whole “hack” needed to get ESXi compatible image is just a single command, that’s not so bad. But yeah, I don’t understand, why MikroTik doesn’t use it and release images that would work for everyone without fiddling with anything.
1st - an ISO install boot image (just like the x86 32-bit ROS).
Where the installer can then select their own size of hard disk.
On a prior CHR I was testing, I ran out of hard disk space when testing packages.
2nd - licensing similar to all other Mikrotik ROS products - instead of a subscription based license.
I would like to license and forget instead of having to track a subscription license.
I hesitate to install any products that use a subscription based license.
I suspect these two feature request could drive up the popularity and install base for all physical and virtual environments and make it much more easy to install/configure.
You can set the system disk capacity before first run.
You can buy perpetual license that is even transferable to other chr if you need it in the future.
Fix the P10 License, vlans over bonding has a lot of TX drops when use more than 1Mb (unresolved ticket: #2016062166000118). This problem does not affect PUnlimited license.
specific to CHR I’d ask for a way to automate deployment, be it to do a dhcp-client-request on the first interface found and get a config file specific for this box by eg requesting a tftp-file based on the mac# of this interface.
and for an easy system-reset a specific reboot-flag with “load default config” would also be nice (doing an autobackup before rebooting just in case).
disk-image-resize-support inside CHR would also be nice, in case one needs to increase the bootdisk.
I’d love DNS Request routing. This means that the DNS-Service of RouterOS shall redirect its DNS-Request upon a certain rule set (eg. DNS prefix or suffix) to another DNS Server
I second the notion of being able to automate the deployment. The CHR documentation doesn’t say a lot about how the initial spin-up process works. What I’d like to see, from a documentation perspective, is how to customize this process. For instance, I want to run CHR in OpenStack/KVM environment. One of the cool features of this environment is the ability to provide a “configuration drive” that the VM can use during the spin-up process. Ideally, the document would say what file the CHR would be expecting on the drive. Do you realize how cool that would be? =) Right now, it would appear that CHR, by default, has DHCP client configured on ether1; this is well and good, but it’s not documented.
Lots of ideas here. Better documentation = better users. =)
For now, the thing missing is a 100M licence.
I have 5 pfSense systems I’d like to migrate to CHR, but $45 / VM is a bit too much, especially since VMs are 5EUR / VM and are capable of forwarding <100Mbit/s.
So, say a $10 for 100M would be great. I could be called “p0.1”…