RouterOS version 6.46.3 has been released in public "stable" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 6.46.3 (2020-Jan-28 10:46):

*) hotspot - fixed redirect to log in page (introduced in v6.45);
*) lora - added "ru-864-mid" channel plan;
*) lora - improved immediate packet delivery;
*) lte - added GPS port support for Quectel EP06 modem;
*) lte - added "psc" (Primary Scrambling Code) parameter for "cell-monitor" function on R11e-LTE6 and R11e-LTE;
*) lte - do not show invalid "phy-cellid" when it is not yet received on "R11e-LTE";
*) lte - do not show unrelated info parameters after network mode failover;
*) port - fixed multiple identical USB serial device detection (introduced in v6.46);
*) ppp - fixed connection establishment when receiving "0.0.0.0" DNS;
*) snmp - fixed "ifOperStatus" reporting for combo ports;
*) winbox - removed duplicate "counter", "chain", "size" and "payload" parameters under "LoRa/Traffic";

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 particular RouterOS release.

Any chance we could get more details about

*) hotspot - fixed redirect to log in page (introduced in v6.45)

Just wondering what was the issue and what changed to fix it ?

@emils, If I am happy with 6.46.2 is there any need to change/update for a plain vanilla setup (ie there are no security fixes in this new version and thus not mandatory??)??

@emils, If I am happy with 6.46.2 is there any need to change/update for a plain vanilla setup ...

MT wants you to believe that published change log is full story. Hence if change log doesn't mention any of your itches you're not obliged to upgrade your ROS devices.

Any chance we could get more details about

*) hotspot - fixed redirect to log in page (introduced in v6.45)

Just wondering what was the issue and what changed to fix it ?

There was an issue with the redirect to the hotspot page... i dont know more info...

Any chance we could get more details about

*) hotspot - fixed redirect to log in page (introduced in v6.45)

Just wondering what was the issue and what changed to fix it ?

There was an issue with the redirect to the hotspot page... i dont know more info...

@Zacharias Thank you so so much for the really constructive input. But maybe some more details about what the actual issue was. Were all types of host impacted(Windows,Linux,Android,iOS) or only certain hosts or browsers maybe? I'm trying to understand if this is an issue which I may be seeing somewhere in a production environment and don't want to deploy and upgrade saying it will fix issue unless I have more details.

hAP ac2, 256MB ram: With v6.46.* I get a random reboot.

hAP ac2, 256MB ram: With v6.46.* I get a random reboot.

some suggest disabling the ntp package
viewtopic.php?f=21&t=156825&sid=81b15b9 ... 47#p773118
viewtopic.php?f=21&t=156825&sid=81b15b9 ... 47#p773712

markmcn, Zacharias - On devices with low resources (for example, SMIPS) it was possible that Hotspot login page does not appear properly
anav - As always, if you do not see changes in changelog that you require, then there is no need for an upgrade
EgidijusL, td32 - You will not ever be able to determine the cause of the reboot in the forum. If your router is rebooting by itself, then contact support@mikrotik.com right away and provide supout file. Forum posts regarding a crash due to NTP service is a random guess without any reason. Only MikroTik staff can determine precise cause of the problem and if it is caused by the software, then we want to fix this problem as soon as possible. If you even manage to workaround a problem based on other user experience, then the issue is still there and others suffer from it. All bug reports are very welcome

Audience 6.46.3 / Winbox V3.20:
- in Winbox content of schedules / scripts / netwatch is completely concatenated (no line breaks)
- when doing export in terminal, line breaks are there...
- In Webfig all is shown correctly as well with line breaks

bug or feature ?

Audience 6.46.3 / Winbox V3.20:
- in Winbox content of schedules / scripts / netwatch is completely concatenated (no line breaks)
- when doing export in terminal, line breaks are there...
- In Webfig all is shown correctly as well with line breaks

bug or feature ?

Was also a feature in previous versions.

Does this include all the 6.47 test version fixes, since it's newer ?

Thx.

During startup just after upgrade 6.46.2 -> 6.46.3, there are extra two lines in the log:


Is it some new feature and we'll see this in log in future releases also or is it something forgotten from dev/test?

Observed on arm and mipsbe, haven't yet tried other archs. During subsequent reboots (without upgrade) these extra lines are not logged.

Ondrej

When trying to update my RB3011, I get "kernel failure in previous boot" in log, and it didn't update.
Same thing happened when going from 6.46.1 to 6.46.2. Eventually succeeded in update but it took some tries.
And this never happened before.

I did upgrade a bunch of devices without major issues: hAP AC2 (Qty 2), hEX S (Qty 4), CRS312 (Qty 1), RB2011 (Qty 1), CRS326 (Qty 1).

Related to the hAP AC2 I got a very weird issue. The 2 units that I manage both did the upgrade without any issues and reported no issues at all. One of them 2 days later reported zero Wi-Fi Clients. Checking Winbox I noticed on Wireless Association that clients were trying to connect associating at 1 Mbps and after few seconds gets disconnected. None of the Wi-Fi clients were able to get IP connectivity.

I did rollback that hAP AC2 to the version 6.46.2 and the problem persisted. I did check online on several founds related with this specific issue (only is that there are a lot of complains of poor performance on Wi-Fi on this unit.

I did try to put the long term version ( ver 6.45.8 ) and after I rebooted the router to downgrade it never came back.

Aside that I need to get onsite and check what's going on (if it's hang or simple is brick it) what else can I do to: (1) Avoid this problem in my other hAP AC2 if it shows up. and (2) What can I do to correct this problem after I manually recover my brick it hAP AC2 device?

Thanks!

With my cAP ac (same chipset as hap ac2), I had to downgrad to 6.44.6 from 6.46.x in order to have normal wifi connections with my clients again.

I have upgraded my RB951G-2HnD (mipsbe) from 6.46.2 to the lastest version 6.46.3 and it never come back.

I tried to restart it several times but it doesn't come back.

Checking the router, I saw that the LED on which I have the network cable plugged in did not blink, I proceeded to plug it in again and it started to flash again, but the router still does not work


Has something similar happened to anyone? Have you been able to fix it in any way?

I have enough configuration and I would not like to have to reset it.

Thanks.

Thank you for this Update
Hotspot Login page now opens on huawei P10 Android 8

markmcn, Zacharias - On devices with low resources (for example, SMIPS) it was possible that Hotspot login page does not appear properly

Ruh roh that's not very reassuring. I was encountering this on my fleet of hundreds of CCR1036s. Wouldn't those be considered relatively high resource devices?

Audience v6.46.3 [stable]
Auto-connecting to the second Audience does not work
You must manually link the two Audiences.

After installing v6. 45. 8 [long-term]
When the second audience is enabled, it automatically connects to the first one.

I will try to repeat.

hAP AC2. Update - from 6.45.7 to 6.46 with WinBOX 6.20. Result - crash, device is not available from Winbox and reboot after about 1 min. Restored the device through netinstall to 6.45.7. The device is able to work. I tried to flash 6.46 through netinstall - crash, the analog result and ...

Exactly the same situation with Update - from 6.45.7 to 6.46.3. The only way to recover is netinstall.

Is it really just my problem?

Did you upgrade routerboard firmware (System -> Routerboard)?

I am seeing some issues with routes over a /29 gre interface.
This has been observed since I went to v6.46.

viewtopic.php?f=2&t=157756&p=775916#p775705

Bug?

what has changed after the update. In general, the router is good, but I see many have problems. in the end, how is he at work?

Mac server broken? hAP ac lite

Hello!
The Dude (4.0 beta 3, 6.46.2, 6.46.3) stopped connecting to CCR, CRS and RB1100 on versions 6.46.2, 6.46.3 and 6.45.8 long term. The logs do not write the correct username and password. It connects to other devices (RB750, SXT, QRT, DISC) on these firmware without problems.

Did you upgrade routerboard firmware (System -> Routerboard)?

Yes, up to 6.45.8 - last work ver
All 6.46 - crash

just had a case on a Hap AC2 where the 2,4 GHz wlan1 stopped running, nothing in the log file.

Created supout file but when I restarted device to see if it solves the problem, the supout file created during the problem was deleted. (Supout file should be created in "/flash" if it exists by default)

None of the wifi devices could see the wifi, i.e. iPad tablets, Samsung phones and tablets

Disable / Enable wlan1 did not solve, restart did.

Will do supout file should it occur again

New version 6.46.4 has been released in stable RouterOS channel:

viewtopic.php?f=21&t=158100