The easiest solution for irritating LEDs: apply black tape. I have done that “forever” on MikroTik equipment, e.g. because of the blue powerled (torch).
Installed beta9 on my CCR2004-1G-2XS-PCIe this morning without success. After powering the system on the two red leds turn off and the Mgmt Ethernet Ports comes up but the Router is not reachable and under my Linux host the interface isn’t able to obtain an IP address anymore. I tried to use the reset button but it doesn’t do anything. Netinstall failes. 192.168.88.1 isn´t reachable. Tried to pull up the link using an old Hub and a newer Gigabit Switch, as well as connecting it directly to my Laptop without success.
Any advice?
Solved: Solution → Mac-telnet → set boot to Ethernet → netinstall → back to the latest stable!
I think that means.. no 
Is there anything known about a “wifi-mediatek” package?
I don’t think MikroTik uses any MediaTek wifi chips?
Just found this string inside the “wifi-qcom” npk. We’ll see whats coming. 
I found a setting on AX Lite LTE related to esim.
I think that’s been there (at least on other models)… But it’s not usable AFAIK & nothing about it in docs.
It maybe related to DW5821e-eSIM modems, but IDK.
maybe an upcoming wifi7 device.
What’s new in 7.14beta10 (2024-Feb-06 15:47):
!) rose-storage - moved SMB service in the RouterOS bundle;
!) smb - removed legacy SMB service (replaced with newer and faster ROSE SMB service);
*) arp - added ARP status;
*) console - improved stability when using autocomplete with “export”;
*) defconf - fixed configuration script on KNOT devices if “ppp-out” interface is removed;
*) defconf - fixed firewall rule for IPv6 UDP traceroute;
*) dhcpv6-client - updated error logging when multiple prefixes received on renew;
*) disk - added global disk “settings” menu (CLI only);
*) l3hw - fixed IPv6 host offloading in certain cases;
*) package - added “size” property;
*) poe-out - improved 802.3at classification and measurement accuracy;
*) poe-out - improved cable test for hAP ac3 and hAP ax3 devices;
*) ptp - added “aes67” and “smpte” profiles;
*) ptp - added configurable “domain” and “priority2” parameters;
*) ptp - added support for Management message forwarding in BC;
*) route - fixed gateways of locally imported vpnv4 routes;
*) route-filter - fixed AS path matchers when input and output chains are used;
*) sfp - fixed corrupted Tx traffic at 10Gbps rate on CCR2004-16G-2S+ in rare cases;
*) smb - added option to specify SMB service mode as “auto”;
*) supout - added PTP section;
*) system - expose “lo” and “vrf” interfaces;
Beta 10? What is happening? 
This will be the long therm ?
!) rose-storage - moved SMB service in the RouterOS bundle;
!) smb - removed legacy SMB service (replaced with newer and faster ROSE SMB service);
Build-in SMB still doesn’t work with macOS and Windows clients
Maybe I don’t understand how it should be used… can you explain it to us?
Thanks
Correction, old SMB did not work with macOS.
New v7.14 SMB works with all Operating Systems now. And is fast too.
There is a different config now, so you may need to adjust first.
You are right (Thanks for listening to us 
)
So after the update from 7.13.3 is better to delete old SMB share and make a new one?
When 7.14 is not in beta, config should be migrated normally. During beta all kind of bugs can be possible, so be careful.
*) sfp - fixed corrupted Tx traffic at 10Gbps rate on CCR2004-16G-2S+ in rare cases;
Could we have more details on this issue?
That will be for Mikrotik’s coming WiFi 7 devices
or potentially for WiFi 6 AP’s. The MediaTek chips are more energy efficient and output less heat so as long as they can match the Qualcomm driver stability and feature support would be a great option.
Just informing incase it isn’t known. Adding wireguard peers is broken on webfig in the 7.14betaX series. The wireguard/peer page is messed up and the add new button doesn’t work.
Tested on CCR2216.
I tested this again. And does seem to work, from RB1100AHx4 with previously existing ROSE+RAID1 to a macOS Sonoma(Intel). ⌘K in Finder, smb://<routeros_ip> then it prompts for share. Both the “dynamic” user from smb-user= and new ones added & new shares. MacOS cache credentials, somewhere/sometime… so maybe that’s why I thought it didn’t work before. Over 1G ethernet direct to router, 53MB/sec or 420Mb/sec if my math is right (e.g. 1G file transfers in 19 seconds:
time cp /tmp/1gsample.txt /Volumes/raid1-part1
cp /tmp/1gsample.txt /Volumes/raid1-part1 0.00s user 0.86s system 4% cpu 19.227 total
While useful to have users with ROSE shares on RB1100… my poor little 16MB LTE devices didn’t need SMB server.
Now if there were only DNS-SD (e.g. mDNS) support, in an extra-package… SMB server/shares WOULD just “magically” appear in “Network” section, and not require a less friendly ⌘K with URL
Hi Amm0, does it also work without the ROSE package and without RAID?