I have same problem.
The Wiki said, that somen models do not have full SFP support relative to the production date.
https://wiki.mikrotik.com/wiki/MikroTik ... patibility
How can I find this out for my devices?

I've got same behavoir when I was updated my switches from 6.49.8 to 7.11.2. Fortunately it was solved in 7.12 firmware: *) poe-out - fixed rare CRS328 poe-out menu and poe-out port config loss after reboot; And I confirm that 7.12.1 successfully restores all PoE tabs for 9-24 ports of CRS328-24P-4S...

I found a workaround. I inserted the dongle into a Windows PC, opened http://192.168.8.1, enabled Bridge mode, and voila! The dongle works in the router. I have an lte1 interface without any settings, but it it detects dhcp updates and pings 8.8.8.8.

Very disapointed with this behavior... All external devices can freely connect to CAP-Manager, but internal WiFi-interface must done workaround prior to connect to own CAPsMan. I'm using 6.49.7 with internal LAN bridge (br-lan, 192.168.30.1) and none of above advices does not help me. Here are two r...

Enabling tkip in security profile helped me with the same problem.

This is a bug in the latest firmwares that caused if you have admin defined mac address for bridge. In this case you need to manually define the ID RoMON parameter, which must be equal to the MAC address of any ethernet port (even if not connected). I got this idea from https://forum.mikrotik.com/vi...

You can inject custom headers in the "subject" parameter:
/tool e-mail send to="test@test.test" subject="Subject text\r\nContent-type: text/plain;charset=windows-1251" body="Body text";

Same here. Just upgraded routeros to the new 6.44 firmware and got the same "ready to send" status for the one of my L2TP/IPSec connections. This connection based on Ubuntu Strongswan+xl2tpd service. All other Routers that work on old 6.43.12 firmware connecting to this L2TP-server without...