Changes since previous version:
!) www - fixed http server vulnerability;
*) capsman - improved CAP status querying;
*) defconf - fixed default configuration generation when wireless package is disabled;
*) ike2 - check child state before allowing rekey;
*) ike2 - send EAP identity as user-name RADIUS attribute;
*) lte - added LTE signal level reading for Cinterion modems;
*) queue - fixed reboot loop when queues were used (introduced in 6.39rc42);
*) rb3011 - added partitioning support;
*) tr069-client - added “Device.Hosts.Host.{i}.” support;
*) userman - fixed rare crash when User Manager requested file does not exist on router;
*) wireless - fixed RBSXT5HacD2nr2 small channel support;
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
setup: gw = rb750gr3 ↔ sw = crs125 ↔ LAN & ap = wap ac / hap ac
Things have been operational in 6.37.1 750g3,crs125 and 1x wap ac. I have 3 vlans, 1 for management, 2 for lan. I bought another few wap ac and hap ac to add to the network.
First, I upgraded from 6.37.1 to 6.38.5. (some weird stuff happened upgrading CRS125.. more on this in another thread post later that led me to believe that the CRS had become faulty). Anwyay, found that the CRS lost connectivity to the hex although I wasn’t yet aware it was a version issue. Hex couldn’t mac ping CRS. It was intermittent, after several configuration resets on the CRS, I could get the hex to ping/mac ping the CRS. Thought I had stablized it after that. After solving that, I went on to plug in and out devices. Plugged in the HAP AC to the CRS resulted in the CRS losing connectivity to the hex. SPENT 8 HOURS straight thinking its my configuration issue since its a production environment. Finally, for some reason, I realized it could be a version issue and so I went on to downgrade all the mikrotik devices to the old working version – 6.37.1. Voila, things seem to be stable again. Also, related or not, while i was on 6.38.5, HAP AC had difficult time (intermittent) picking up a dhcp client ip from the hex.. whether or not its due to the CRS being in between. After downgrading, it picked up the dhcp client ip pretty much immediately. WAP AC was fine though, had always picked up a dhcp address without any issues. So of course it also misled me from thinking theres a version issue.
Alright, I’m very furious. So much wasted time and no profit. What’s going on here? is 6.37.x = stable ; 6.38 = beta while 6.39 = alpha? Does Mikrotik warrant their users for such trouble? ALSO Lost a lot of credibility by my client here. I still look forward to IKEv2 so staying on 6.37 is really no solution.
Edit: Do move this post to the 6.38.5 thread, my mistake for posting here.
