MikroTik

Posted: **Tue Dec 17, 2019 3:38 pm**

RouterOS version 6.46.1 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.1 (2019-Dec-13 12:44):

*) capsman - fixed CAP upgrading (introduced in v6.46);
*) console - fixed "clear-history" restoring historic actions after power cycle;
*) console - removed "edit" and "set" actions from "System/History" menu;
*) defconf - fixed default configuration loading after fresh install (introduced in v6.46);
*) dhcpv6-server - use lease time from RADIUS;
*) dude - fixed image and font file accessing (introduced in v6.46);
*) gps - only adjust system time after GPS signal is established;
*) health - fixed health reporting on OmniTIK 5 PoE ac;
*) ipsec - improved system stability when processing decrypted packet on unregistered interface;
*) l2tp - improved system stability when disconnecting many clients at once;
*) log - fixed "disk-file-name" parameter validation (introduced in v6.46);
*) lora - added support for MIPSBE, PPC, TILE and x86 architectures;
*) lora - improved confirmed downlink forwarding;
*) lte - do not reset modem when setting the same SIM slot on LtAP;
*) lte - show SIM error when no card is present;
*) ppp - fixed session establishment with high amount of tunnels (introduced in v6.46);
*) ppp - prioritize "remote-ipv6-prefix-pool" from PPP secret over PPP profile;
*) qsfp - do not show "sfp-wavelength" for cables that do not support it;
*) snmp - fixed health related OID polling (introduced in v6.46);
*) supout - fixed autosupout.rif file generation (introduced in v6.46);
*) system - fixed "*.auto.rsc" file execution (introduced in v6.46);
*) user-manager - fixed "db-path" parameter validation (introduced in v6.46);
*) webfig - fixed skin folder presence (introduced in v6.46);
*) winbox - fixed "allowed-number" parameter setting invalid value in "Tool/SMS" menu;
*) winbox - show "LCD" menu only on boards that have LCD screen;
*) wireless - added "russia4" regulatory domain information;
*) wireless - improved compatibility by adding default installation mode and gain for devices with integrated antennas;
*) wireless - improved compatibility for Switzerland wireless country profile to improve compliance with ETSI regulations;

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.

Posted: **Tue Dec 17, 2019 3:49 pm**

*) wireless - added "russia4" regulatory domain information;
more info?

Posted: **Tue Dec 17, 2019 4:46 pm**

PREV: v6.46 [stable] is released!

1) After upgrade from v6.46 to v6.46.1 at RB SXTR&R11e-LTE6_v20

CellLock was disabled and I must setup it again

2) CellLock when loose signal for BOTH Band's at ~3 second then

RSRQ = -195 dB

other signal parameters are freez

fraffic is no Rx at lte1

SMS are not work any direction

lte1 is still up, Public IP is still assigned

It's not go to 3G/UMTS - modem freez and not do anything

To fix this we can:

reboot by hand/script/watchdog etc

re-enable interface

Set Cell Lock again or reset it

Try send SMS... and lte1 go down and do initialisation lte1

Try check firmware version of lte1 modem... and lte1 go down and do initialisation lte1

.
To detect it faster I setup Traffic Monitor who check lte1 rx=0 and rsrq=-195.

winbox_v3.20_64_Aan5lU4Dxk.png

.
https://help.mikrotik.com/servicedesk -> SUP-3785
BTW. Cell-Monitor in v6.46 is fix and show correctly the EARFCN column data.

Posted: **Tue Dec 17, 2019 5:36 pm**

RB850Gx2 still fails install verification post-install

Specific error: "Couldn't continue - damaged routeros-powerpc package: bade image (6)"

Router was usable in this state and I was able to backout to 6.45.7 again.

Posted: **Tue Dec 17, 2019 6:58 pm**

these random 'could not save package' errors need to stop.
/sys sup-output
failed to create supout.rif file

Posted: **Tue Dec 17, 2019 7:05 pm**

skins are still not working as expected on 6.46.1 on the RB750Gr3s i tested.

on the presence of flash/ filesystem, skins should be placed on flash/skins/filename.json. When saving new skins using Design Skin, they are saved on <root>/skins/file.json. The skin works if i choose them, however these files on <root> will always be vanished on reboot, as they should be placed on flash/ and not <root>.

On System/Users/Groups, dropbox gives me the files present on flash/skins to select, but they are never applied. If i got the same filename on flash/skins/file.json and <root>skins/file.json, they are now applied. But as explained, those files on <root>/skins will vanish on the next reboot. Thus that's not a good place to have the skin files.

There's still some work to do on skins detection/usage on boards with the flash/ filesystem.

Posted: **Tue Dec 17, 2019 9:01 pm**

Looks like generally stable release to try with? Only a few reports so far

Posted: **Wed Dec 18, 2019 6:07 am**

Design Skin still not work. I upgrade one of my Router from 6.46 to 6.46.1 (RB450G) to test Design Skin but it still shown all menu for user which I assigned custom skin to show only hotspot and some menu.

Jason file save on /skins/filename.json.

Posted: **Wed Dec 18, 2019 7:19 am**

nimbo78 - Execute this command on any router with wireless package - "/interface wireless info country-info russia4".
SiB - Thank you for your report. We will look into this.
bcall - Do you mean that the "/system check-installation" feature is failing? Do you see this error on multiple devices or on a single router?
osc86 - Do you see this error on multiple devices or on a single router? What happens when you try to create a supout file?
leonardogyn, parinya1957 - The issue with the skins folder was resolved for the routers that do not have a flash directory. We will fix this problem in the next release.

Posted: **Wed Dec 18, 2019 8:19 am**

leonardogyn, parinya1957 - The issue with the skins folder was resolved for the routers that do not have a flash directory. We will fix this problem in the next release.

My router was RB450G which do not have a flash directory but problem still happen.

Posted: **Wed Dec 18, 2019 8:51 am**

This announcement does not show up under General or other sub "channels". It only shows up under Announcement. Can we make it visible in all parts of the forum?
Edit: Fixed, thanks who ever fixed it!

Posted: **Wed Dec 18, 2019 9:01 am**

updating to 6.46.1 went smooth ... from 6.46 to 6.46.1 done thru the dude

dude font problem fixed.
No problems so far

Posted: **Wed Dec 18, 2019 9:40 am**

Delete

Posted: **Wed Dec 18, 2019 10:45 am**

parinya1957 - Can you please send a supout file from this router to support@mikrotik.com? If I create a skin and set it to a specific user group, then it works for me without any problems.

Posted: **Wed Dec 18, 2019 12:01 pm**

*) wireless - added "russia4" regulatory domain information;
more info?

russia4 wireless ranges

2402-2482/b,g,gn20,gn40(20dBm)
2417-2457/g-turbo(20dBm)
5170-5250/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(20dBm)/passive
5250-5330/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(20dBm)/passive
5650-6425/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(30dBm)/outdoor
5190-5310/a-turbo(20dBm)
5180-5300/a-turbo(20dBm)

Posted: **Wed Dec 18, 2019 1:17 pm**

leonardogyn, parinya1957 - The issue with the skins folder was resolved for the routers that do not have a flash directory. We will fix this problem in the next release.

Thanks for the feedback. At least for me, for routers without the flash directory, everything is working just fine since 6.46. I don't have access to a lot of different models, but for me, without flash, 6.46 was fine. Waiting for 6.46.2 for fixing this on flash/-capable routers.

Posted: **Wed Dec 18, 2019 1:50 pm**

osc86 - Do you see this error on multiple devices or on a single router? What happens when you try to create a supout file?

I get this error quiet often but only on CHR. A simple reboot solves the problem. It seems to me that the filesystem at some point switches to read-only mode.
I'll do more tests next time I get this error. (I've already updated this instance to 6.46.1)

Posted: **Wed Dec 18, 2019 2:33 pm**

After updating CRS328-24P-4S to 6.46 Version My switch's fan starts working nonstop without a reason It even reached 2000 RPM and 6.46.1 800 RPM, In the last version most of the time it was not on and whenever it was turning the speed was below 600 RPM.
The loud noise is hurting me so much that I downgraded it to 6.45.7.

Posted: **Wed Dec 18, 2019 3:02 pm**

It is almost like with 6.46.
I am not sure if it is related only to mmips or not (network has hEX + few mipsbe devices), but after some uptime all traffic slows down to a crawl (to LAN and WAN addresses), ping goes completely erratic and packet loss is significant.

I made update at the evening and when all IP connectivity was absent at the morning, forced reboot and downgrade to 6.45.7 solved all issues.

Posted: **Wed Dec 18, 2019 4:26 pm**

Can those with Wireless issues from 6.46 report if the update to 6.46.1 resolves those issues please! I would like to update my router and capacs!
(NOTE: I didnt see anything specific in the 'whats new' list that addressed the above though?)

Posted: **Wed Dec 18, 2019 4:52 pm**

strods That is correct, /system check-installation fails after I update my RB850Gx2 to 6.46 or 6.46.1. In Winbox the error is "Couldn't continue - damaged routeros-powerpc package: bade image (6)." I think the wording is slightly different at the command line.

So far it's only been a problem with 6.46 and 6.46.1, and only on a RB850Gx2 (I only have one RB850Gx2, so I can't say if it's this particular router or not). I have a RB750GL and NetMetal5, neither of which have had a problem with 6.46 or 6.46.1.

Posted: **Wed Dec 18, 2019 9:47 pm**

After upgrade my usb modem on RB951-2n not working?
It sat it is connected but no data at all

Posted: **Wed Dec 18, 2019 11:31 pm**

Hi!
What is an "unregistered interface"?
*) ipsec - improved system stability when processing decrypted packet on unregistered interface;

Posted: **Thu Dec 19, 2019 7:17 am**

skurudo - It was not possible to upgrade CAPs from the CAPsMAN if ".npk" files were on the root folder.
leonardogyn - Will be fixed in the next release.
osc86 - Can you please try to generate supout file, while the problem is present on your device? If you manage to do so, then send this file to support@mikrotik.com. If not, then generate file after reboot and send it to us.
shahani, nmt1900, Jimmy - Please send supout file to support@mikrotik.com.
anav - What is the wireless problem that you refer to? Have you reported this to support@mikrotik.com?
bcall - This problem will be resolved in the next release.
dnordenberg - Interface which is already closed/removed/disconnected.

Posted: **Thu Dec 19, 2019 3:02 pm**

Updated 3xHap AC 6.46 -> 6.46.1 - so far without issues
Updated 3xHap AC Lite 6.46 -> 6.46.1 - No issues, I'm using CAPSMAN but this upgrade was done manually

Thanks!

Posted: **Sat Dec 21, 2019 6:42 am**

RB951Ui-2HnD was bricked after upgrade 6.45.7 -> 6.46.1.
Very sad

Posted: **Sat Dec 21, 2019 10:29 am**

HapAc,wireless is no good,ping 11,12,18,speed is poor!!!

Posted: **Sat Dec 21, 2019 4:43 pm**

Now it looks like problems are somehow related to wireless and/or CAPsMAN - at least when router is mmips and access point is mipsbe architecture. Both had to be downgraded to 6.45.7 to regain normal operation. Only switch in between works fine with 6.46.1.

Let's see what developers can dig out from these supouts...

Posted: **Sat Dec 21, 2019 6:50 pm**

anav - What is the wireless problem that you refer to? Have you reported this to support@mikrotik.com?

You are not paying attention dear Sir/Maam. I didnt upgrate to 6.46 due to the reported WiFI problems in the thread. Further, there was nothing in the update notes to .1, that indicated any work had been done to rectify the issues. Finally, and clearly I have no inclination to upgrade to 6.46.1 based on the feedback on this thread.

By the way, perhaps not an Latvian expression, but having your avatars as nothing but bird heads (big or small) only leads in one direction.
"Putnu smadzenes"

Posted: **Sat Dec 21, 2019 9:04 pm**

6.46.1 RBSXTLTE3-7 gsm and 3g are always active. Unable to disable. You cannot leave the LTE range active.

Posted: **Sat Dec 21, 2019 9:49 pm**

6.45.7 rules

Posted: **Sat Dec 21, 2019 11:32 pm**

Hello,
In versions 6.46 and 6.46.1, Omnitik and LHG series constantly began to receive the error in the photograph and often began to see this problem many times during the day reboot devices

Posted: **Sun Dec 22, 2019 12:34 am**

962UiGS-5HacT2HnT => The new release pissed me off more then the law allow...
Just to resume:
after upgrade from 6.45.7
- NONE of devices could connect on 5g interface
- performance of 2.4G was mediocre,
- got intermittent disconnect of a direct cable connection between the hap-ac and computer.
- after restart of the hap-ac I was able to see 5g interface but only for a few seconds
-so the device was close to be bricked.

To overcome this "featured" release I had to try previous releases: 6.45.7 and 6.44 LTS both behaving as expected.

Posted: **Sun Dec 22, 2019 3:42 am**

system->auto-upgrade was broke starting 6.46 til 6.46.1 please fix it

Posted: **Sun Dec 22, 2019 1:31 pm**

Yesterday my RB4011iGS freeze without any reason.
Log did not capture anything.
All eth led are on but i cant login with any method (IP, mac).
The only solution was to restart with power supply.
Is this relative with that.

Posted: **Sun Dec 22, 2019 3:10 pm**

The issue with the skins folder was resolved for the routers that do not have a flash directory. We will fix this problem in the next release.

When can we expect this fix to be released? It's for us an important issue.

Posted: **Sun Dec 22, 2019 6:29 pm**

Yesterday my RB4011iGS freeze without any reason.
Log did not capture anything.
All eth led are on but i cant login with any method (IP, mac).
The only solution was to restart with power supply.
Is this relative with that.

I had the same problem and had to unplugged the power supply . 6.46 is perfect for me. I downgraded.

Posted: **Mon Dec 23, 2019 4:21 am**

RB1100ahx2
6.45.7->6.46.1

Upgrade via winbox (system-packages)
Upgrade went seemingly ok, rebooted fine and all packages were displayed as 6.46.1
But clicking on "check installation", got message "system package damaged".

Reverted back to 6.45.7 -> "check installation" ok again.
Tried upgrading several times, 100% reproducible.
Tested on multiple rb1100AHX2's, it's no hardware defect.

This error was already present in 6.46, but is still not fixed!!!
Also people with other ppc Rb's are reporting this, and reported it at 6.46 already too.
Apparently nobody at MT cares about simply testing ppc packages/functionality anymore, now that they retired the last ppc-RB recently from their sales-catalog.
Seems that as soon as they stop shipping a particular type, they also stop properly supporting it too.....
Maybe a good idea to put less focus on Ros7, and make the current one work properly first???
New features are nice, but I would settle for properly working 'current' feature-set.

Getting pretty annoyed by those very simple and avoidable errors lately....
(Rb1100-series) Ppc-devices were high-end and sold until pretty recently.
Not being able to trust even the simplest download package anymore is not a vote of confidence for companies buying more new high-end MT devices.

Or... rename bugfix/longterm in stable, stable into rc, rc into beta, and beta into alpha, and create a new PROPER long-term stream
(longer then the current "long-term" of barely a year, which is actually "short-term" for most professional companies)

Posted: **Mon Dec 23, 2019 4:38 am**

@ Strods and Bcall:

This is NOT a rb850-only issue, also on RB1100AHX2.
This points to a PPC issue....

Or better said: a poorly tested 2 releases (6.46 and 6.46.1) for ppc.
If they bothered to even test it, they noticed it themselves.

Posted: **Mon Dec 23, 2019 3:17 pm**

upgrading my RB1100 (PPC) went flawlessly ...

Posted: **Mon Dec 23, 2019 4:24 pm**

This is NOT a rb850-only issue, also on RB1100AHX2.
This points to a PPC issue....

I have a single RB1100AHX2 and it's running 6.46.1 just fine. However, funny enough, "Check Installation" is really failing with "damaged routeros-powerpc package: bad image".

Despite of that failure on check installation, the box is running just fine and i haven't noticed any problem at all with 6.46 and now 6.46.1.

Posted: **Mon Dec 23, 2019 4:39 pm**

I'll have to admit ...
I just checked the "Check installation" and it also fails with "damaged routeros-powerpc package: bad image".
... no problems while running ...,

Posted: **Mon Dec 23, 2019 10:33 pm**

I know it SEEMS to update and run just fine. That;s what was reported by me and others.
But if the system package is really damaged, it's just waiting for it to crash/fail on some little used function.

Apart from that, this is such a basic test, they (MT) should have tested that themselves before releasing 2 successive versions with this error.
Moreover, the error was reported in 6.46 by more people, but they didn't even bother to check it before releasing 6.46.1-"so called-stable".

Posted: **Mon Dec 23, 2019 11:20 pm**

reading your comment throws up a few questions ...
- DID anyone actually report this to support@mikrotik.com ?
Just shouting here is useless, this is a userforum and not an official support channel ...

And I totally disagree on your statement about testing, the guys at MT perform countless tests on countless problems. After that they release everything in a test channel.
If NOBODY noticed this, it is NOT because MT doesn't care ... It is just because nobody noticed it.

Posted: **Tue Dec 24, 2019 4:49 am**

Oh... They (MT) read along.... If you follow the "released version" threads a little, you will notice the comments from official MT moderators.
Time and again it's have been proven that user-comments in the forum are picked up by MT in the next release. And that is great!

The way I saw it here is that I did not need any support from them, they just released a product with a (potentially) corrupt package.
That issue should have definitely been noticed prior to release, since they themselves provide a function to test packages after install.
In winbox it's a simple button.... 3 seconds of work! (In a CLI-script, it's a simple command, been there for years)
Apparently they didn't bother...

The forumusers are defacto being used as betatesters of the -so called- stable stream. (that why "Stable", as a name, makes no sense imho)
So in a way... they are the ones that need support from us for this debug-mechanism to work.
Therefore that is why I report in the forum, not via the support-mail. (but in this case I did anyway, after your comment)

A simple click after installing the packages in winbox would have shown them that there is something seriously wrong. That is the most basic test one can do after installing packages.
If that test is not even done by them, then in my eyes they do not test anywhere near enough before releasing a "stable" version, especially for the now recently retired ppc's.
This is an avoidable issue, and I should not need to report it at all... Therefore I can only conclude there is insufficient testing being done.

Anyway.... I may seem overly critical on this, but I mean well. It's intended like a wake-up call to make Ros better in future. I really do feel MT screwed things up here.
As far as I'm concerned.... enough said about this.... I'm sure they picked the issue up by now.

There are a ton of other issues being reported in the (pretty premature) 6.46.x release so far..... So they (MT) have their hands more than full after the holidays.
So please discuss those...

Merry Christmas everyone !!!!

Posted: **Tue Dec 24, 2019 6:14 am**

Hello, something really weird with 6.46.1
I have all my IPv6 advertisements off, DHCPv6 off, yet my machines are getting IPv6 addresses. This behavior started after the upgrade.

Posted: **Tue Dec 24, 2019 10:42 am**

@eddieb, @ozone,

FWIW: Just checked my RB4011, RB2011, PL7411 and RB750U and none of them have this issue. All devices run 6.46.1 [Stable]

Posted: **Tue Dec 24, 2019 10:45 am**

@complex1 I also did check all my other devices, no problems on other architectures.
AND,
I just filed a ticket on this issue as it should be done ...

Posted: **Tue Dec 24, 2019 5:05 pm**

@complex1

Thank you for checking and confirming.... I didn't see it on misbe- or arm-arch either.... just on our ppc-1100's.
(and Bcall reported it on a ppc-RB850 as well)

@eddieb

Good!!
Now they have at least 2 of those reports in their mailbox after the holidays.

Posted: **Tue Dec 24, 2019 6:19 pm**

Hello, something really weird with 6.46.1
I have all my IPv6 advertisements off, DHCPv6 off, yet my machines are getting IPv6 addresses. This behavior started after the upgrade.

Make sure your "bridge" Interface is also turned off in IPv6/ND. Clients receive their address configuration through SLAAC.

Posted: **Wed Dec 25, 2019 8:01 am**

my hapac is broken,red light wont flash,and I can not connect with adress 192.168.88.1,only with mac adress,and does not occur home ap dual!!!
What could I do?

Posted: **Wed Dec 25, 2019 3:44 pm**

my hapac is broken,red light wont flash,and I can not connect with adress 192.168.88.1,only with mac adress,and does not occur home ap dual!!!
What could I do?

revert to 6.44.6 (Long-term) or 6.45.7

Posted: **Wed Dec 25, 2019 5:58 pm**

I was tormented that her fool was from the provider
but ping however, it is large,12,20!!!
for whatever reason, I use 6.45.7

Posted: **Sat Dec 28, 2019 6:13 pm**

I have had both omnitik and powerbox pro go into a hard lockup state. Watchdog did not reboot. No romon access. Nothing works until I power cycle it. Too bad they are on top of a mountain. I'll be downgrading for now and testing further stable releases in a lab from now on.

Posted: **Sun Dec 29, 2019 12:14 pm**

Has anyone else been seeing performance degrading throughput after about 7-14 days of uptime with ROS 6.46 & 6.46.1 with the RB4011 ?? After reboot everything would be fine for a while..

Since downgrading to ROS 6.44.6 i don't seem to have any issues..

Posted: **Wed Jan 01, 2020 12:57 pm**

Hello,

Two days ago upgraded to 6.46.1...

Since then, cannot connect to Huawei MA5608T OLT using /system telnet. When I press <ENTER> console is behaving like I double press <ENTER>.
So, during the authentication process, I type the username, and when I press <ENTER> console add second <ENTER> so I cannot type the password.

UPDATE: Same problem while trying to connect via telnet to CTC FRM220 NMC & Cards.
UPDATE2: Same problem while trying to connect via telnet to switch DCN S5750E-28X-SI-24F-D (ssh works fine).

With other devices, like some ZyXEL and Huawei managed switches there is no such problem.
I can still use /system ssh to connect to same Huawei MA5608T OLT.

Posted: **Thu Jan 02, 2020 9:54 pm**

ok i took the chance and upgraded my RB4011 to 6.46.1 and it did not go well

I know I tested my speed over wireless as I have other non mikrotik WDS to run. It should be said that my 4011 is RB4011iGS + but after upgrading to 6.46.1 I had a download speed of about 37 Mbit and upload of 0.24. My internet speed is 1000/1000 and usually on the wireless I am at 200 to 300 both up and down. I have downgraded to 6.45.6 as it was and everything seems normal again.

Posted: **Fri Jan 03, 2020 12:29 pm**

I can not connect with adress 192.168.88.1,only with mac adress
Damm even I am having a similar kind of issue

Similar or same? Create a dedicated topic (if you haven't yet) and give a link to it here. This topic is dedicated to version related issues.

Posted: **Fri Jan 03, 2020 3:59 pm**

Hello,

Two days ago upgraded to 6.46.1...

Since then, cannot connect to Huawei MA5608T OLT using /system telnet. When I press <ENTER> console is behaving like I double press <ENTER>.
So, during the authentication process, I type the username, and when I press <ENTER> console add second <ENTER> so I cannot type the password.

UPDATE: Same problem while trying to connect via telnet to CTC FRM220 NMC & Cards.

With other devices, like some ZyXEL and Huawei managed switches there is no such problem.
I can still use /system ssh to connect to same Huawei MA5608T OLT.

I have the exact same issue here

Posted: **Fri Jan 03, 2020 5:10 pm**

Anyone running hotspots and encounter the issue with the redirect and/or splash page randomly stopping being served? In my bug report response I was asked to run 6.46.1, however I see nothing in the change notes to address this. Considering it wasn't happening all the time I can't just test it in a lab and say it works. The problem didn't seem to surface until days or a week after upgrading. It's almost required to run it in production and wait for users to report issues, so I may be able to upgrade just one of my locations to test it for a while. Even then, I have 30+ locations and less than 5 reported the issue, so no guarantee I even see the problem at one site over a month after.

Posted: **Fri Jan 03, 2020 9:32 pm**

Has anyone else been seeing performance degrading throughput after about 7-14 days of uptime with ROS 6.46 & 6.46.1 with the RB4011 ?? After reboot everything would be fine for a while..

Since downgrading to ROS 6.44.6 i don't seem to have any issues..

Yes I also noticed this behavior. A reboot helped. Got locked out as well two times since using 6.46 while forwarding traffic was not affected. Also downgraded to LTS 6.44.6 lets see if this keeps things stable. FYI not using SFP, bridge or switch functions on the RB4011; only pure routing on 3 ports.
Could be related to viewtopic.php?f=2&t=149062

Posted: **Fri Jan 03, 2020 11:58 pm**

system->auto-upgrade was broke starting 6.46 til 6.46.1 please fix it

Same problem. I have about 15 devices so I need this feature soooooooooo much

Posted: **Sat Jan 04, 2020 5:33 pm**

Hello!

The following problem is not specific to this version of the router and has been around for a while now on multiple routers ...

When I look (in WinBox) at the interface status window for the contents of the "Last Link Down Time" and "Last Link Up Time" cells, I regularly get overwhelmed with a lot of nonsense of interface type and router type ...

I also attach a picture to give you a better view of what I mean exactly ...
The picture shows that if we check the interface log, it returns seemingly correct values, but in the interface status window it is stupid ...

The routers I have experienced:
2pcs - RB433AH,
2pcs - RB450G,
3pcs - cAP Lite,
3pcs - cAP AC,
4pcs - RB750Gr3,
2pcs - RB3011UiAS,
1pcs - RB1100AHx4 Dude Edition

I'd like to ask the developers if they can, so please kindly fix the bug, according to their natural priority ...

Thanks Slys!

Sorry for my linguistic correctness, i use google translator ...

Posted: **Sat Jan 04, 2020 6:59 pm**

The following problem is not specific to this version of the router and has been around for a while now on multiple routers ...

A good reason not to post it here.

Posted: **Mon Jan 06, 2020 7:25 pm**

I'd like to ask the developers if they can, so please kindly fix the bug, according to their natural priority ...

It appears that Mikrotik's priority on cosmetic bugs is very very low.
This bug has been reported many many times for many many months now and it has been thoroughly ignored by MikroTik.

It is that kind of feature which you were happy when it was introduced and then quickly learned to ignore it's even there, since it has been useless for so long now.

And btw, you are offtopic here. The bug seems to be related to Winbox actually and not related to some specific ROS version.

Posted: **Tue Jan 07, 2020 12:18 am**

From 6.46. x does not work on the 5 GHz network. Does not show at all

Posted: **Wed Jan 08, 2020 11:31 am**

Can you disable DHCP package? When I disable DHCP package, after restart it is enable again.

Posted: **Wed Jan 08, 2020 11:46 am**

Can you disable DHCP package? When I disable DHCP package, after restart it is enable again.

I read a while ago that DHCP package is now a prerequisite for the security package, so maybe that is reason it enables when restart

Posted: **Thu Jan 09, 2020 1:10 am**

From 6.46. x does not work on the 5 GHz network. Does not show at all

Same here with any frequency exept
5240.

Posted: **Sun Jan 12, 2020 8:40 pm**

My CCR1072 did not boot i.e. is not reachable after upgrade from 6.46. As it is in DC, I have no clue what happened. I had the same problem with RB4011 in our office - had to disconnect it from power source.

Posted: **Mon Jan 13, 2020 7:46 pm**

Not sure if my problem started after last update, but I found this.

Mikrotik: RB760iGS
Version: 6.46.1
Problem: Connected 2 UPS over USB hub, but I can monitor only one because only one USB port available.

 /system resource usb print
# DEVICE VENDOR                                           NAME                                         SPEED                                        
 0 1-0    Linux 3.3.5 xhci-hcd                             xHCI Host Controller                         480                                          
 1 2-0    Linux 3.3.5 xhci-hcd                             xHCI Host Controller                         5000                                         
 2 1-1                                                                                                  12                                           
 3 1-1.1  Prolific Technology Inc.                         USB-Serial Controller                        12                                           
 4 1-1.4  Prolific Technology Inc.                         USB-Serial Controller                        12                                           

/port print
Flags: I - inactive 
 #   DEVICE NAME                                                   CHANNELS USED-BY                                              BAUD-RATE
 0          serial0                                                       1                                                      auto     
 1   1-1.4  usb1                                                          2 UPS                                                  9600

As you can see, only 1 USB port is created, but is using 2 channels. I was using this setup earlier and for every connected device to my USB HUB, separate USB port was created. Not now

Any fix? Thanks

Edit: I changed one of USB-SERIAL Controllers (still Prolific Technology Inc.), but now I have 2 USB ports with 1 channel per port so it's working OK again. Have no clue whats wrong... Both previous adapters working without errors when used separately.

Posted: **Thu Jan 16, 2020 2:55 pm**

New version 6.46.2 has been released in stable RouterOS channel:

viewtopic.php?f=21&t=156315

MikroTik

v6.46.1 [stable] is released!

v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!

Re: v6.46.1 [stable] is released!