When to expect 802.1x support in RouterOS?

Strong need in wired 802.1X

Code: Select all

MAJOR CHANGES IN v6.45:
---------------------- 
!) dot1x - added support for IEEE 802.1X Port-Based Network Access Control (CLI only);
---------------------- 

I didn't see it listed in the changes or reported anywhere, but it looks like 6.42.5 also adds Temperature readings for RB450Gx4 under System > Health.

For you that have this issue what guest servies have you activated? Are all activated including Dynamic Memory? I wonder if this issue goes away if you disable all services including dynamic memory. I had all guest services disabled and still experienced the issue. Leaving all production Hyper-V CH...

Hyper-V works because it does not assemble packets into 64k buffers. But this assembly happens only for traffic which source and destination is also virtual guest. If destination is physical router outside VM environment then there should be no problem with MPLS. Are there multiple issues here? Are...

Tried to upgrade Hyper-V CHR from 6.42 to 6.43rc3 - FAILED No connection via winbox mac. Hyper-V terminal froze. Restored from backup, tied again - same result. Downloaded fresh CHR VHDX image. pasted configuration and nothing worked. started fresh, and the only issue I could find was the interface...

I moved my lab to Hyper-V Core 2012 R2, and can confirm that MPLS runs fine on that.

I've been running an 8-router Mikrotik lab (on ESXI) for several weeks, and can confirm this is still broken in 6.41.3. I have not tried the latest release candidate though (6.42rc52) - I might give that a test tonight.

Any updates on this?

Does TX drops already solved on vlans?

I'm curious about this as well. Seeing this on CCR1036-12G-4S, about 30 VLANs on Ether1, and no VLANs on Ether2. Been seeing TX Drops on both Ether1 and Ether2, as well as most of the VLANs on Ether1.

I didn't when it was loaded with 2.9. 2.9 worked flawlessly. I can't get it to downgrade now... upload the packages and issue the "downgrade" command, correct?

Hi guys I'm having a problem. I upgraded a routerboard 112 (Level 4) to the new beta3. The CPU sits at 100%. It defaults with no IP address, and winbox won't connect to it. I login to it through another Routerboard (running 2.9.35) through MAC Telnet. anytime I reboot the beta3 board it resets every...