Ip address add address=PublicIP/24 interface=ether1 Now, I have no clue as to why a functioning CHR instance with a valid P unlimited license would deactivate out of the blue, but it would be extra nice if the freaking thing would throw a warning somewhere in the logs, the top bar of WInbox or even better, as a popup mesage once a user logs in Winbox. Logged in to Mikrotik to get the license and just like that, the problem was fixed! Lo and behold, the darn license was missing! Logged in to the CHR to pull the config and was lucky enough to click the License submenu by mistake. ~16 hours in, my lonely neuron was starting to crash and I thought I should disable CHR and put a RB1100AHx4. I started testing, tweaking, reinstalling and all the blah blah to no avail. Nothing imported beside the actual VMs.Īll VMs including the CHR one were imported without a problem and everything seemed to be fine.īut.while testing the various bits and pieces I dicovered I had huge packet loss as soon as any traffic over 100KB/s passed through this sever. Updated the BIOS to the latest version and procedeed to reinstall ESXI 8.ĮSXI config from scratch.

Replaced all ethernet and DAC patch cables with new ones. Took everything apart and gave it a good clean. So I decided I would do this during weekend to minimize the downtime. This server has a CHR for routing (no NAT) and some VMs inside ESXI. Have a Supermicro server that was in dire need of a good cleaning and ESXI reinstall. This post is the rambling of a pissed off user in regards to CHR license and ~16 lost hours.

Mikrotik chr free license