RouterOS version 6.41.3 has been released in public “current” channel!
Before an upgrade:
Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
What’s new in 6.41.3 (2018-Mar-08 11:55):
!) tile - improved overall system performance and stability (“/system routerboard upgrade” required);
*) chr - automatically generate new system ID on first startup;
*) console - do not allow variables that start with digit to be referenced without “$” sign;
*) defconf - fixed DISC Lite5 LED default configuration;
*) export - fixed “/system routerboard mode-button” compact export;
*) filesystem - improved error correction process on RB1100AHx4 storage;
*) firewall - fixed “tls-host” firewall feature (introduced in v6.41);
*) gps - added GPS port support for Quectel EC25-E modem when used in LTE mode;
*) lte - fixed r11-LTE-US interface initialization process after reboot;
*) romon - make “secret” field sensitive in console;
*) smb - improved NetBIOS name handling and stability;
*) snmp - fixed w60g SSID value;
*) tile - fixed bogus voltage readings;
*) tr069-client - fixed TR069 service becoming unavailable when related service package is not available;
*) usb - improved packet processing over USB modems;
*) winbox - fixed “/tool e-mail send” attachment behavior;
*) winbox - fixed maximal ID for Traffic Generator stream;
*) winbox - removed “Enable” and “Disable” buttons from IPsec “mode-config” list;
*) winbox - show “D” flag under “/ip dhcp-client” menu;
*) wireless - removed unused “/interface wireless registration-table monitor” command;
To upgrade, click “Check for updates” at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download
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 some problem has appeared on device
Please keep this forum topic strictly related to this concrete RouterOS release.
I’ve asked this before on the RC forum, however I’ve had no response.
I did e-mail support, they didn’t understand the question, fingers crossed you get a better response!
if you want to know more about https://babasupport.org/routers/tp-link-customer-service/778 TP-Link comes with a massive user base, that makes it all the more difficult to provide customer services to these users. That’s where we come in as a company providing any and all customer services for your TP-Link routers.Tp-link Router is one the best router which is mainly used for internet distribute purpose. Many routers are available in the market but tp link is the best. when many people using the internet at the same time that time it works better compare to another router.
We have improved handling of operations on TILE based devices (CCRs). This fix will not affect anyone negatively, but might help in rare cases with different random problems. For example, there were users who used CCR1072 and CPU core was stuck on 100% usage due to IPsec HW encryption. This fix resolves it. Basically, CPU is now better handling assigned processes. There is no need to upgrade, if you do not have any problems with your device.
Out of sudden I found nice dialog with drop-down box named “SIM”, under System → Routerboard → SIM:
Something that I neved expected from my old (but good) CRS125-24G-1S (https://mikrotik.com/product/CRS125-24G-1S-IN, which is essentially a 24-ports switch with decent router (like 951’s) built-in, and it doesn’t feature any SIM slot for what I know. Or there is a hidden one?
On my image you can see ROS and f/w versions (6.41.3), device model and button I talk about.
What’s that? Hidden feature or another bug-not-a-feature thing?
poizzon - If you have a RB2011 model which has serial console port, then please provide serial output so we can see why router can not boot any more; docmarius - Are you referring to one of the fixes in 6.42rc version or some other problem which you have resolved/reported to support? zoombie - Please provide more information. Do you have any problems with real life traffic not with the BTest? Can you downgrade to 6.41.2, make sure that problem is gone, upgrade back to 6.41.3 and see that problem appears once more?
I had issues with the DHCP server not handing out addresses after some time of proper functioning in 6.41.2 if the interface is a bridge. This was reported by some users, and seemed it was addressed in the RC, so I assumed a ticket would not be necessary anymore (In my case I reverted my main router to 6.40.6 which solved the issue, so no emergency on this side).
zoombie > - Please provide more information. Do you have any problems with real life traffic not with the BTest? Can you downgrade to 6.41.2, make sure that problem is gone, upgrade back to 6.41.3 and see that problem appears once more?
Real traffic and Btest shows the same result, poor I can’t upgrade to 6.41.3 and also to 6.41.2 from 6.40.3
Real traffic and Btest shows the same result, poor I can’t upgrade to 6.41.3 and also to 6.41.2 from 6.40.3
And I checked upgrade from 6.41.2 to 6.41.3 on arm routerboard, not working
