CHR re-enabling DHCP client on each reboot

RouterOS Virtualization
1

I’m testing with CHR deployed on ESXi 6.0. I acquired the image 2 weeks ago. I THINK it was 6.40.1 at the time.
I have static IPs configured on ether1 for management. I’ve tried disabing the DHCP client or removing it. Upon reboot, there’s a new instance of DHCP Client on ether1.
If i disable it, that stays out there but a new instance shows up. If i remove it, a new instance shows up.

The static IP is present and working, either way.

any thoughts on keeping DHCP client disabled?

I just upgraded to 6.40.3 and the issue is still present.

Thanks!
Ryan

2

Did you properly convert the CHR image from IDE to SCSI before deploying it?

3

I followed the ESXi directions here:
https://wiki.mikrotik.com/wiki/Manual:CHR_VMWare_installation#How_to_Install_Cloud_Hosted_Router_on_VMWare_ESXi_6.5

It’s not SCSI, It’s setup as IDE.

Just to make sure I wasn’t missing any steps or something hadn’t glitched in the conversion, I did the whole process again with identical results.

4

In my experience this does not work. There is a procedure somewhere on the forum how to convert it to
a SCSI disk, when you don’t do that the disk will fail after some time and you get problems like you encountered.
(and random crashes when writes to disk are done)
Unfortunately MikroTik do not distribute a .OVF file that you can simply import into ESXi, that would solve a lot of trouble.

5

I will look into that. They’re testing with a OVA file (seen in this thread here: https://forum.mikrotik.com/viewtopic.php?f=15&t=124905&start=50 )

6

The new ova should be right have not tested it. but with my earlier chr’s it was a must to convert to scsi to get config written to disc survive reboots.

7

I have installed the OVA as a test and it appears to work OK until now.
So that is a much easier way to get this sorted.
(have been asking MikroTik for over a year to do this but finally they did it)