MikroTik

Posted: **Tue May 15, 2018 11:47 pm**

After update to 6.43rc11 My Kodi player on Raspberry could't connect to Synology NAS via NFS or SMB!
Please provide more information about this issue to support@mikrotik.com

This was bug with hEX bridge! Now all works ok!

Posted: **Wed May 16, 2018 12:54 am**

*) wireless - improved Nv2 PtMP performance;
is it further improvement from 6.42.1?

I'd like to know what kind of NV2 performance improvement we can expect from version 6.43? I did notice improvements in version 6.42 but heard of people saying the new 6.43rc is worse then 6.42...

Posted: **Wed May 16, 2018 6:04 am**

DHCP Client seems to be sorted out and working now!

Posted: **Wed May 16, 2018 11:56 am**

DHCP Client seems to be sorted out and working now!

Agreed, I've upgraded my production routers to 6.43rc7 and they are working very well.

Posted: **Wed May 16, 2018 12:51 pm**

We had an issue with a CHR running 6.42.1 restarting 3 times in a day and subsequently downgraded to 6.41.4. Both of these versions yielded high latency, which has been fixed with the multi-queue driver in 6.43.rc12.

Steps:

Upgraded RouterOS to v6.43rc12
Set KVM VirtIO network driver on Hypervisor to support multi-queue
Disabled RPS on CHR instance

Router was upgraded at approximately 22:45 on the 15th of May.

Latency:

Throughput:

CPU:

Looks like IRQs are not balanced evenly, this may be on the hypervisor though...

PS: Nice to see that IRQ rx/tx queue pairs are mapped to the same CPU. Herewith a snippet from the router:

Posted: **Thu May 17, 2018 3:01 am**

strods,

When I tried to install the ntp package (downloaded zip file for rc12, extracted the ntp package and put it to the files folder) and found it did not work.

The problem has been fixed because the main system package is rc11 and I installed rc12 ntp package. After upgrading the main package to rc12 version, I could able to install the ntp package.

YH

Posted: **Thu May 17, 2018 12:12 pm**

Yes, and that was described in the Log after reboot. That's how it works - all packages should be of the same version.

Posted: **Fri May 18, 2018 3:45 pm**

Version 6.43rc14 has been released.

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.

Changes since previous rc release:

*) bridge - add dynamic CAP interface to tagged ports if "vlan-mode=use-tag" is enabled;
*) bridge - added ingress filtering options to bridge interface (CLI only);
*) bridge - added initial Q-in-Q support (CLI only);
*) bridge - allow to make changes for bridge port when it is interface list;
*) crs3xx - added initial Q-in-Q hardware offloading support (CLI only);
*) crs3xx - fixed ACL rate rules (introduced in v6.41rc27);
*) defconf - fixed missing bridge ports after configuration reset;
*) ipsec - improved reliability on generated policy addition when IKEv1 or IKEv2 used;
*) led - fixed CCR1016-12S-1S+ LED behaviour after Netinstall (introduced in v6.41rc58);
*) lte - added support for Novatel USB730LN modem with new ID;
*) routerboard - fixed "protected-routerboot" feature (introduced in v6.42);
*) wireless - improved Nv2 stability for 802.11n interfaces on RB953, hAP ac and wAP ac devices;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.

Posted: **Fri May 18, 2018 5:56 pm**

I like: "crs3xx - added initial Q-in-Q hardware offloading support (CLI only);"
could someone please point me to the correct manual/wiki entry on this one?

Posted: **Fri May 18, 2018 6:36 pm**

You can find an example here:
https://wiki.mikrotik.com/wiki/Manual:I ... 8Q-in-Q.29

Note that the same principles can be applied as for regular VLAN filtering (trunk, access, management port and so on).
Do note that QinQ with RSTP is not supposed to work with bridges that use 802.1Q (this is by standard IEEE 802.1ad), but there is a bug in 6.43rc14 that prevents RSTP from working properly, this is fixed in 6.43rc15.

Also the wiki for CRS3xx is updated with more examples with ACL rules:
https://wiki.mikrotik.com/wiki/Manual:C ... s_switches

Starting from 6.43rc14 "protocol-mode=none" disables compliance with IEEE 802.1Q and allows to forward 01:80:C2:XX:XX:XX MAC addresses, most noticeable protocols that use these MAC addresses are LACP and dot1x. By setting the protocol-mode to none you can achieve a true transparent bridge. Use with caution though.

Posted: **Fri May 18, 2018 6:54 pm**

Is there work in progress or planned to make a bridge with protocol-mode=none and simple VLAN filtering (a couple of VLANs defined on the bridge and the ports being untagged or tagged members) to support hardware offload on the common switch chips in the routers?
As it is now, it is not hardware offloaded when configured this way, but when the bridge is configured without VLAN filtering and the VLANs are defined in the switch config, it is.

Posted: **Fri May 18, 2018 10:02 pm**

Please add SOCKS5 to RouterOS! Many people want it!

Posted: **Sat May 19, 2018 3:53 am**

Im seeing a disc space leak over time. Im seeing it on TILE, MIPSBE and PPC. Im seeing it on all the devices I manage.

This because obvious when I could not upgrade or downgrade firmware because there was not enough space. I dont see what is taking up space on the NAND. I saw one device go from 27.9 free space out of 64 down to 14MB when I tried to downgrade. I also saw a device go from 16MB free space to 27.9MB free space WHEN I UPGRADED from RC12 to RC14..

This issue seems to take time to develop. 6.41.4 is stable and does not do this. 42.x seems to and 43RC14 also seems to.

The only way around this is Netinstall. I erased NAND to be sure. I wanted to bring this up on the forum as it can lead to having to go onsite and Netinstall and restore the device. This also seems to be present in 42.x

Ive sent a email to support.

Posted: **Sat May 19, 2018 11:29 am**

Im seeing a disc space leak over time. Im seeing it on TILE, MIPSBE and PPC. Im seeing it on all the devices I manage.

Then it must be related to something you do on all the devices you manage. What are you doing that could consume diskspace and that could be nonstandard?
For example, enabled graphing with storage to disk. I had that in the past but I removed storage to disk to reduce the number of disk writes, so I cannot check if that could be it.
(in the past it did not cause a disk leak, of course it consumes space but it is trimmed over time)

Posted: **Sat May 19, 2018 11:41 am**

[mistake]

Posted: **Mon May 21, 2018 10:48 am**

Version 6.43rc14 has been released.
*) bridge - added initial Q-in-Q support (CLI only);

what about selective qinq?

Posted: **Mon May 21, 2018 11:07 am**

Currently it is not possible to select which frames are going to be tagged with an outer tag and which not.
It is possible to use CRS3xx ACL rules to achieve a similar result though.

/interface bridge
add name=bridge vlan-filtering=yes vlan-protocol=802.1ad
/interface bridge port
add bridge=bridge interface=ether1
add bridge=bridge interface=ether2
/interface bridge vlan
add bridge=bridge untagged=ether1,ether2 vlan-ids=1
add bridge=bridge tagged=ether1,ether2 vlan-ids=200
/interface ethernet switch rule
add mac-protocol=ipx new-vlan-id=200 ports=ether1 switch=switch1

Posted: **Tue May 22, 2018 9:42 am**

Version 6.43rc14 has been released.

*) routerboard - fixed "protected-routerboot" feature (introduced in v6.42);

what exactly is fixed in protected routerboard?

Posted: **Tue May 22, 2018 2:46 pm**

Please fix this probleem . My screenshot

My attachment . Frenquensy probleem!!!

Posted: **Tue May 22, 2018 3:07 pm**

change frequency to default and this error will disappear

Posted: **Wed May 23, 2018 3:27 am**

Frenquensy probleem!!!

That's just a warning that you are running overclocked CPU. If it's stable and not overheating, you can just ignore it (That is if you need this higher speed. If not, just lower it to default value). Same message is also output in the log every time router starts.

Posted: **Wed May 23, 2018 5:00 pm**

In order to access router running this version by Winbox, please download v3.14rc Winbox loader from here:
https://www.mikrotik.com/download/share/winbox.exe

Please read the changelog before an update since version introduces major fixes and improvements

Version 6.43rc17 has been released.

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.

Changes since previous rc release:

*) backup - do not encrypt backup file unless password is provided;
*) bridge - add dynamic CAP interface to tagged ports if "vlan-mode=use-tag" is enabled;
*) bridge - added initial Q-in-Q support (CLI only);
*) btest - requires at least v6.43 Bandwidth Test client when connecting to v6.43 or later version server except when authentication is not required;
*) crs3xx - fixed VLAN filtering when there is no tagged interface specified;
*) lte - added ICCID reading for info command R11e-LTE (CLI only);
*) lte - added roaming status reading for info command (CLI only);
*) lte - improved r11e-LTE configuration exchange process;
*) lte - renamed LTE scan tool field "scan-code" to "mcc-mnc" (CLI only);
*) lte - use alphanumeric operator format in info command;
*) mac-telnet - require at least v6.43 MAC Telnet client when connecting to v6.43 or later version server;
*) radius - use MS-CHAPv2 for "login" service authentication;
*) romon - require at least v6.43 RoMON agent when connecting to v6.43 or later RoMON client device;
*) smb - fixed valid request handling when additional options are used;
*) user - all passwords are now hashed and encrypted, plaintext passwords are kept for downgrade (will be removed in later upgrades);
*) w60g - added 4th 802.11ad channel (CLI only);
*) w60g - general stability and performance improvements;
*) w60g - improved maximal achievable distance;
*) w60g - removed distance lock for wAP 60G devices;
*) webfig - improved authentication process;
*) winbox - improved authentication process excluding man-in-the-middle possibility (Winbox v3.14 required );
*) wireless - fixed wireless interface lockup after period of inactivity;
*) wireless - increased stability on hAP ac^2 and cAP ac with legacy data rates;
*) wireless - improved client "channel-width" detection;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.

In order to access router running this version by Winbox, please download v3.14rc Winbox loader from here:
https://www.mikrotik.com/download/share/winbox.exe

Posted: **Wed May 23, 2018 5:14 pm**

Version 6.43rc17 has been released.

after upgrading, do not accept passwords, two different routers!

and why did not you write in What's new that we need to use the new WinBox?

Posted: **Wed May 23, 2018 5:17 pm**

Version 6.43rc17 has been released.
after upgrading, do not accept passwords, two different routers!

from where? did you read above post, that you need other Winbox version?

Posted: **Wed May 23, 2018 5:19 pm**

Where is the new topic about 3.14?

Sent from my XT1580 using Tapatalk

Posted: **Wed May 23, 2018 5:21 pm**

Where is the new topic about 3.14?

same answer. please read the post until bottom

Posted: **Wed May 23, 2018 5:24 pm**

Version 6.43rc17 has been released.
after upgrading, do not accept passwords, two different routers!
from where? did you read above post, that you need other Winbox version?

it is simple way - in whats new you can allways write some notes, about changes

Posted: **Wed May 23, 2018 5:25 pm**

it is simple way - in whats new you can allways write some notes, about changes

I'm sorry, but have you read them? It is in the notes

Posted: **Wed May 23, 2018 5:32 pm**

When use WBOX 3.14rc to connect CHR 6.42.2 - get license error after login, winbox think this is x86 machine )

Posted: **Wed May 23, 2018 5:42 pm**

I have installed the new 3.14rc winbox, then connected a router I use for testing, it is now on the current channel.
It is not possible to change the channel to install the release candidate.

Posted: **Wed May 23, 2018 6:15 pm**

deleted

Posted: **Wed May 23, 2018 6:17 pm**

License error on prior chr versions with winbox 3.14rc1.
No issues with winbox 3.13

Posted: **Wed May 23, 2018 6:57 pm**

what is the new password for a fresh install of chr.
admin- blank no longer works

Posted: **Wed May 23, 2018 7:09 pm**

*) w60g - added 4th 802.11ad channel (CLI only);
*) w60g - general stability and performance improvements;
*) w60g - improved maximal achievable distance;
*) w60g - removed distance lock for wAP 60G devices;

Love it! Wireless Wire keeps getting better.
What's "distance lock" though?

Posted: **Wed May 23, 2018 8:33 pm**

However I cannot login, even after a configuration reset, neither with "old" winbox, nor with the proposed one, nor with telnet or MAC telnet or ssh. admin with blank password still doesn't work...
Any suggestion will be greatly appreciated!

Posted: **Wed May 23, 2018 9:19 pm**

However I cannot login, even after a configuration reset, neither with "old" winbox, nor with the proposed one, nor with telnet or MAC telnet or ssh. admin with blank password still doesn't work...
Any suggestion will be greatly appreciated!

I have the same problem. I was trying to install a new wAP, and the upgrade pushed it to 6.43rc17 so I triggered the upgrade on my router as well and now I'm locked out of winbox with a username/password incorrect failure. CLI is unaffected.

For the record, the admin user doesn't exist here, I'm using my own creds (though that didn't stop me from trying, anyway.)

14:12:14 system,error,critical login failure for user matthew from D4:BE:D9:9E:B4:E3 via winbox 
14:12:19 system,error,critical login failure for user matthew from D4:BE:D9:9E:B4:E3 via winbox 
14:13:23 system,error,critical login failure for user admin from 10.1.20.253 via winbox 
14:13:28 system,error,critical login failure for user admin from 10.1.20.253 via winbox 
14:13:32 system,error,critical login failure for user admin from 10.1.20.253 via winbox 
14:13:37 system,error,critical login failure for user admin from 10.1.20.253 via winbox 
14:13:44 system,error,critical login failure for user matthew from 10.1.20.253 via winbox 
14:13:54 system,error,critical login failure for user matthew from 10.1.20.253 to romon network

Any help is appreciated
Matt

Posted: **Wed May 23, 2018 9:57 pm**

Login problems with 6.43rc17, admin login does not work even with the beta winbox version.

Posted: **Wed May 23, 2018 10:05 pm**

Same problem with login on 6.43rc17. After update all works fine, but after I reset to default, I was no longer able to login with admin user without a password, neither with winbox, nor with web interface.

Posted: **Wed May 23, 2018 10:42 pm**

*) backup - do not encrypt backup file unless password is provided;

I will wait till the next release because of the possible pitfalls when having to clear the configuration.

Posted: **Wed May 23, 2018 10:57 pm**

*) w60g - general stability and performance improvements;
*) w60g - improved maximal achievable distance;
*) w60g - removed distance lock for wAP 60G devices;

Hello MikroTik team,
could you please provide more details - what performance improvements have been done, what is the new maximal achievable distance and what exactly is distance lock?

Thank you in advance.

Posted: **Wed May 23, 2018 10:58 pm**

*) backup - do not encrypt backup file unless password is provided;

I like the current way it works the backup is encrypted with admin password.
Please make an option to encrypt using current admin password like before, I don't want to have my backup unencrypted neither want to put a password in a script to make the backup.

Posted: **Wed May 23, 2018 11:06 pm**

*) backup - do not encrypt backup file unless password is provided;

I like the current way it works the backup is encrypted with admin password.
Please make an option to encrypt using current admin password like before, I don't want to have my backup unencrypted neither want to put a password in a script to make the backup.

The point is that system passwords are hashed and no longer available in plain text. This is not possible.

Posted: **Wed May 23, 2018 11:51 pm**

Bug with WB 3.14rc
https://photos.app.goo.gl/oO8NPV2w1yiGKqUH2
And TickApp on Android need to update too....

Posted: **Thu May 24, 2018 12:52 am**

Where I can download winbox 3.14 rc ? thanks

Posted: **Thu May 24, 2018 1:07 am**

Where I can download winbox 3.14 rc ? thanks

In order to access router running this version by Winbox, please download v3.14rc Winbox loader from here:
https://www.mikrotik.com/download/share/winbox.exe

Posted: **Thu May 24, 2018 1:21 am**

Where I can download winbox 3.14 rc ? thanks

In order to access router running this version by Winbox, please download v3.14rc Winbox loader from here:
https://www.mikrotik.com/download/share/winbox.exe

Thanks. This solved my issue. Would it be helpful for the router / winbox to do a version match check before authentication to avoid the erroneous User/Password errors?

Posted: **Thu May 24, 2018 1:30 am**

Thanks. This solved my issue. Would it be helpful for the router / winbox to do a version match check before authentication to avoid the erroneous User/Password errors?

You should not install RC versions when you don't or cannot read the release notes and the announcements here on the forum!

Posted: **Thu May 24, 2018 2:55 am**

I made a hard reset after login error, right now with version 3.14rc1 I still receive user or password error. What should I do?

Posted: **Thu May 24, 2018 3:15 am**

I made a hard reset after login error, right now with version 3.14rc1 I still receive user or password error. What should I do?

You can install a previous version of RouterOS using the Netinstall.

Posted: **Thu May 24, 2018 3:22 am**

I made a hard reset after login error, right now with version 3.14rc1 I still receive user or password error. What should I do?
You can install a previous version of RouterOS using the Netinstall.

Can you tell me where I find the procedure?

Posted: **Thu May 24, 2018 3:33 am**

Can you tell me where I find the procedure?

http://www.mikrotik.com.my/reinstalling ... rial-port/

This is better explained than the MikroTik's wiki.

Posted: **Thu May 24, 2018 4:54 am**

Loving the priority on security improvements. Keep it coming!

Posted: **Thu May 24, 2018 4:57 am**

Unfortunately I did not succeed, mikrotik is bricked, it was not possible to use netinstall

Posted: **Thu May 24, 2018 6:02 am**

strods,

After having upgraded to rc17, I was no longer to login in the hAP ac^2 via WinBox 3.13. When I use the alternative way "using Webfig", after several trails, I could be able to login in.

However I can login the router using the old WinBox software of version 2.2.18.

Using the new WinBox 3.14rc version, I am able to login the system.

YH

Posted: **Thu May 24, 2018 6:23 am**

Thanks. This solved my issue. Would it be helpful for the router / winbox to do a version match check before authentication to avoid the erroneous User/Password errors?
You should not install RC versions when you don't or cannot read the release notes and the announcements here on the forum!

Normally I would have been more careful, but only an rc version higher than what I already had - I was careless. Glad it was easily rectified. That said, I'm just giving a user experience improvement suggestion. Don't bite, we're all professionals here.

Posted: **Thu May 24, 2018 7:53 am**

Really Mikrotik ?!?!? RC17 lost user/password ?? Im locked out.. Netinstall ?? REALLY ?!?!

After all the 42.1 mess and now this.. What happened to the super stable trustworthy Mikrotik I knew ?

Luckily I have 41.4 in a separate partition and I believe I can make that partition active using the boot menu..

Plus there is all this talk of VPNFilter.. Plus ive had some really weird disk space issues across all hardware platforms.
http://www.theregister.co.uk/2018/05/23 ... worldwide/

Doing Mikrotik has gotten seriously perilous over the last few months.

Posted: **Thu May 24, 2018 8:06 am**

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.

This quote says it all ...
rc releases are BETA releases, don't use it if you can't lose it !

Posted: **Thu May 24, 2018 8:26 am**

Hello MikroTik team,
could you please provide more details - what performance improvements have been done, what is the new maximal achievable distance and what exactly is distance lock?

Thank you in advance.

Love it! Wireless Wire keeps getting better.
What's "distance lock" though?

Distance was limited with frame lifetime, this limitation now is removed. We reworked RX pattern part to utilize it more efficiently. In some channels link can be established over 2km distance.

Posted: **Thu May 24, 2018 8:52 am**

I can confirm old versions of Winbox work if you are locked out..

I have attached a Winbox from 2010 that works..

Posted: **Thu May 24, 2018 8:58 am**

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.
This quote says it all ...
rc releases are BETA releases, don't use it if you can't lose it !

Its not a issue for me. I can Netinstall in my sleep and I always keep a stable in a partition.. Thats not my point.. A Release Candidate should at least be checked that it does not lock out users. Ive been doing Mikrotik RCs for 8 years and the severity of the errors recently is way off the charts VS the last 8 years.

Posted: **Thu May 24, 2018 11:04 am**

same issue here that couldn't login after upgrade... I also used the old winbox and it worked. I don't know where to download winbox 3.14 rc

Posted: **Thu May 24, 2018 11:07 am**

Link to Winbox rc is in the above post, where RC is announced. Please all read the posts. It is not that hard.

Posted: **Thu May 24, 2018 11:15 am**

Also got enticed to install rc17 because of features and fixes but then couldn't login. Old Winbox did work though. Thanks for the tip!

Posted: **Thu May 24, 2018 11:17 am**

Link to Winbox rc is in the above post, where RC is announced. Please all read the posts. It is not that hard.

It would be better to move that link (and the text) to the changelog so people who update from their router without reading this thread will also see it.

Posted: **Thu May 24, 2018 11:20 am**

Unfortunately I did not succeed, mikrotik is bricked, it was not possible to use netinstall

Usually when people claim "router is bricked, netinstall does not work" it simply means they do not do the netinstall correctly as they have never done it before and thus do not know what to expect.
It is not a good idea to install an RC version when you don't have experience with using netinstall.

Posted: **Thu May 24, 2018 11:31 am**

Link to Winbox rc is in the above post, where RC is announced. Please all read the posts. It is not that hard.

Indeed it was there, it does work... Thank you
It is indeed not that hard but some times we are not given the "gift of time" to read all pages of all posts. I would try to edit and stick it to the first post or some place "sticky" since 20 people asked the same think to help us (not having too much time always)

Thank you again

Posted: **Thu May 24, 2018 11:32 am**

Link to Winbox rc is in the above post, where RC is announced. Please all read the posts. It is not that hard.
Indeed it was there, it does work... Thank you
It is indeed not that hard but some times we are not given the "gift of time" to read all pages of all posts. I would try to edit and stick it to the first post or some place "sticky" since 20 people asked the same think to help us (not having too much time always)

Thank you again

At least read the RC announcement post by MikroTik staff. RC versions CAN and often DO break things. RC is for testing, so reading notes is important.

Posted: **Thu May 24, 2018 12:40 pm**

I have a feeling that the API calls cannot authenticate now!

Posted: **Thu May 24, 2018 3:22 pm**

Hello

I have installed V6.43rc 17 in RB750 but It show message "Wrong user or password" using diferents Winbox Versions, I write user admin and password empty. I reset RB750 several times but It does not work.

Could you help me?

Thanks in advance.

Posted: **Thu May 24, 2018 5:13 pm**

Link to Winbox rc is in the above post, where RC is announced. Please all read the posts. It is not that hard.
Indeed it was there, it does work... Thank you
It is indeed not that hard but some times we are not given the "gift of time" to read all pages of all posts. I would try to edit and stick it to the first post or some place "sticky" since 20 people asked the same think to help us (not having too much time always)

Thank you again
At least read the RC announcement post by MikroTik staff. RC versions CAN and often DO break things. RC is for testing, so reading notes is important.

Hi Normis.

Mikrotik must implement automated tests ASAP. You must stop breaking things even in rc versions. The only way to make high quality software is doing a lot of test...since unit test, integration test, UI test, E2E test, etc. Launch a new version (even a RC) whitout automated testing is an irresponsability, at least in 2018. You are wasting time and energy, on this forum discussing bugs with your end users when you must use this forum to talk about improvements and new features.

BR,
Diego.

Posted: **Thu May 24, 2018 5:37 pm**

You are wasting time and energy, on this forum discussing bugs with your end users when you must use this forum to talk about improvements and new features.

These are two different forums

Posted: **Thu May 24, 2018 8:03 pm**

I have been trying to get better Transmit speeds on our cAP AC's, the v6.43rc17 dose not improve anything, or stabilize the connection. When doing a speed test I should see 200+Mbps U/D but only getting 12-25Mbps Download and 120-160Mbps Upload. When looking at the TX Rate of in Wireless Registration jumps all over the place from 6Mbps-200Mbps-40MHz, the RX is normally much higher around 300-650Mbps consistently. I have done testing with both my phone and laptop, the phone a Google Pixel 2X will be stationary on my desk 15-20FT from the access point with only open air between it. I have seen a lot of other posts talking about pore performance on multiple APs recently and no real solutions. I have also tried iperf3 tests with a little better numbers in the past but nothing close to what is the expected numbers.

Also for those too lazy to read where to get the new winbox.exe here you go: https://www.mikrotik.com/download/share/winbox.exe that link was not in the update text of the package manager, but was in the post about the latest release.

Posted: **Thu May 24, 2018 8:04 pm**

Did anyone manage to use api calls with this version? My php api fails to login (similar to the winbox problem)

Posted: **Thu May 24, 2018 8:14 pm**

.
.
Also for those too lazy to read where to get the new winbox.exe here you go: https://www.mikrotik.com/download/share/winbox.exe that link was not in the update text of the package manager, but was in the post about the latest release.

Is now mentioned at the top of the posting. The original communication was sub par.

I skip this version(s) till I feel confident that the risk to loose my device is low enough.

Posted: **Thu May 24, 2018 8:23 pm**

Hi Normis.

Mikrotik must implement automated tests ASAP. You must stop breaking things even in rc versions. The only way to make high quality software is doing a lot of test...since unit test, integration test, UI test, E2E test, etc. Launch a new version (even a RC) whitout automated testing is an irresponsability, at least in 2018.

BR,
Diego.

Honestly, I dont understand what has happened. Something really changed at Mikrotik. Ive been doing RCs for 8+ years. For 7+ years the RCs were as stable as the stable version. ALMOST NO BUGS OR ISSUES. Suddenly in the last like 3-4 months things have really taken a turn in a bad direction. So much so im now buying Ubiquity. The 42.1 "stable" release was abhorrent and bug ridden in ways that were inexplicable. DHCP client did not work in a "stable" release for example. The change log from 42.1 to 42.2 is stunning. They took away a feature that was critical to me and had been in RouterOS for more then 8 years, Netwatch. For me Mikrotik seems to have become untrustworthy as almost anything could break, even in "stable" releases. Features might be taken away with no notice or explanation. Mikrotik is not addressing any of this in the forums. They need to post a apology for causing so much money loss for on site visits to Netinstall "Stable" 42.2 updates. Ive got a reproducable issue now im dealing with support on where disc space is lost during a update. If you upgrade or downgrade this can occur and if you do it twice you can no longer upgrade or downgrade and your only way is to then go on site and netinstall. This occurs on Tile, MIPSBE and PPC so far that I know of and occurs in the "stable" 42.x and when upgrading from RC14 to 17. 10MB is lost in disc space with each upgrade/downgrade. It appears some file or files is not being deleted in a update. OR. Some file is being generated. Ive given Mikrotik remote access to the router to look at it. It should be simple, log in, and with thier special access go look at files and see whats taking up too much space.

Things are a huge mess.

Ive ALWAYS used and LOVED Mikrotik products. So I keep hoping it will get worked out and we will get back to super stable. Locking out all users updating to RC17 does not look good. It really appears zero testing was done. Did no one at Mikrotik upgrade and login ?

Sorry for my rant. I love Mikrotik, but, we gotta get things back to super stable again. Till then I have all my production routers on 6.41.4 as that was really the last truly STABLE STABLE.

Posted: **Thu May 24, 2018 11:26 pm**

Ive been doing RCs for 8+ years. For 7+ years the RCs were as stable as the stable version.

You are exaggerating "a bit". Mikrotik started releasing public RCs since mid-2015 (since v6.32 or 6.31, but definitely not earlier), which means you could not have been using RCs for more then 3 years. And final versions before that time were just horrible. Introduction of the release channels was a huge improvement in their release management, bugfix channel brought stability that had never been seen before. And RCs... well, their main purpose (as with any beta software) is to break early.

The 42.1 "stable" release was abhorrent and bug ridden in ways that were inexplicable.

The current stable version is 6.40.8 (the latest one in the BugFix release channel). The version 6.42.2 (and 6.42.1 before that) has been release in the Current release channel, which means it is not yet considered stable enough.

Posted: **Fri May 25, 2018 1:49 am**

Hi Normis.

Mikrotik must implement automated tests ASAP. You must stop breaking things even in rc versions. The only way to make high quality software is doing a lot of test...since unit test, integration test, UI test, E2E test, etc. Launch a new version (even a RC) whitout automated testing is an irresponsability, at least in 2018.

BR,
Diego.
Honestly, I dont understand what has happened. Something really changed at Mikrotik. Ive been doing RCs for 8+ years. For 7+ years the RCs were as stable as the stable version. ALMOST NO BUGS OR ISSUES. Suddenly in the last like 3-4 months things have really taken a turn in a bad direction. So much so im now buying Ubiquity. The 42.1 "stable" release was abhorrent and bug ridden in ways that were inexplicable. DHCP client did not work in a "stable" release for example. The change log from 42.1 to 42.2 is stunning. They took away a feature that was critical to me and had been in RouterOS for more then 8 years, Netwatch. For me Mikrotik seems to have become untrustworthy as almost anything could break, even in "stable" releases. Features might be taken away with no notice or explanation. Mikrotik is not addressing any of this in the forums. They need to post a apology for causing so much money loss for on site visits to Netinstall "Stable" 42.2 updates. Ive got a reproducable issue now im dealing with support on where disc space is lost during a update. If you upgrade or downgrade this can occur and if you do it twice you can no longer upgrade or downgrade and your only way is to then go on site and netinstall. This occurs on Tile, MIPSBE and PPC so far that I know of and occurs in the "stable" 42.x and when upgrading from RC14 to 17. 10MB is lost in disc space with each upgrade/downgrade. It appears some file or files is not being deleted in a update. OR. Some file is being generated. Ive given Mikrotik remote access to the router to look at it. It should be simple, log in, and with thier special access go look at files and see whats taking up too much space.

Things are a huge mess.

Ive ALWAYS used and LOVED Mikrotik products. So I keep hoping it will get worked out and we will get back to super stable. Locking out all users updating to RC17 does not look good. It really appears zero testing was done. Did no one at Mikrotik upgrade and login ?

Sorry for my rant. I love Mikrotik, but, we gotta get things back to super stable again. Till then I have all my production routers on 6.41.4 as that was really the last truly STABLE STABLE.

To both: If you want stability, stick to Bugfix channel. If you want the latest features (which very possibly will have bugs), follow the Current channel. And if you want the bleeding edge, go for RC versions. But if you go for either Current or -and especially- RC, please do NOT complain about things breaking. You have been warned.

Since you mentioned UBNT, they run a very closed alpha testing train, a partially open beta testing train and public stable releases. These correspond to RC, Current and Bugfix, even though it is not a perfect analogy. Also, have you seen a recent UBNT changelog? Have you seen its length? How can this compare to the length of last two years' Mikrotik changelogs? You cannot have it all - many new features and perfect stability.

This comes from a guy who have criticised MT for aspects of their software development. But some of their decisions, like introducing different channels and speeding up development, were right and have brought tangible results.

Posted: **Fri May 25, 2018 9:13 am**

Ive been doing RCs for 8+ years. For 7+ years the RCs were as stable as the stable version.
You are exaggerating "a bit". Mikrotik started releasing public RCs since mid-2015 (since v6.32 or 6.31, but definitely not earlier), which means you could not have been using RCs for more then 3 years. And final versions before that time were just horrible. Introduction of the release channels was a huge improvement in their release management, bugfix channel brought stability that had never been seen before. And RCs... well, their main purpose (as with any beta software) is to break early.

I agree with you. I've been playing with rc versions since they introduced the release channels. I have shot myself in the balls several times with them requiring a netinstall and some voodoo.

And indeed, since they introduced the release channels the situation has improved a lot.

If you agree to play in the bleeding edge go for the rc versions. Otherwise stay with the safest ones. But be aware that rc versions, despite working well most of the time, can still break stuff!

Posted: **Fri May 25, 2018 1:00 pm**

In order to access router running this version by Winbox, please download v3.14rc Winbox loader from here:
https://www.mikrotik.com/download/share/winbox.exe

Version 6.43rc19 has been released.

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.

Changes since previous rc release:

*) api - changed authentication process (https://wiki.mikrotik.com/wiki/Manual:API#Initial_login);
*) bridge - fixed FastPath for bridge master interfaces (introduce in v6.42);
*) chr - fixed adding MSTI entries;
*) dhcpv6-client - added missing "Server identifier" parameter in release message;
*) kidcontrol - fixed dynamically created firewall rules order;
*) lte - added extended signal information for Quectel LTE EC25 and EP06 modem;
*) lte - added ICCID reading for info command R11e-LTE and R11e-LTE-US (CLI only);
*) user - all passwords are now hashed and encrypted, plaintext passwords are kept for downgrade (will be removed in later upgrades);
*) w60g - added distance measurement (CLI only);
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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.

In order to access router running this version by Winbox, please download v3.14rc Winbox loader from here:
https://www.mikrotik.com/download/share/winbox.exe

Posted: **Fri May 25, 2018 1:03 pm**

I have a feeling that the API calls cannot authenticate now!

API authentication method have changed, see API manual:
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

Posted: **Fri May 25, 2018 1:56 pm**

In order to access router running this version by Winbox, please download v3.14rc Winbox loader from here:
https://www.mikrotik.com/download/share/winbox.exe

Is it to be expected that using this new winbox on older releases (6.42.2) causes problems?
I see some fields that are read-only in that situation, and amongst them is the field to select the release channel.
So when accessing a router that is running 6.42.2 and is set to current I cannot change that to release candidate.
With the older 3.13 version that field can be changed as normal.

Posted: **Fri May 25, 2018 2:29 pm**

I have a feeling that the API calls cannot authenticate now!
API authentication method have changed, see API manual:
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

I modified it and it seams to work but....
One of my first commands is to modify the username and password but I get a failure that
failure: user name can't be changed
did you lock the admin user from not being able to change? That would be weird, wouldn't it?

Thank you

Posted: **Fri May 25, 2018 2:30 pm**

Basically the last two RouterOS versions have been released for testing purposes for everything besides Winbox. We are working on a new Winbox version and have provided rc version earlier within this topic. When 6.43 and Winbox 3.14 will be released, then both of them will work together just fine. Read-only fields issue will be resolved in next Winbox release.

Posted: **Fri May 25, 2018 2:42 pm**

Basically the last two RouterOS versions have been released for testing purposes for everything besides Winbox. We are working on a new Winbox version and have provided rc version earlier within this topic. When 6.43 and Winbox 3.14 will be released, then both of them will work together just fine. Read-only fields issue will be resolved in next Winbox release.

Is that why I can't modify the username via API?
Will it stay like that?
if yes I would then need to create a new user in my provisioning platform and disable the default user (admin)

Posted: **Fri May 25, 2018 2:55 pm**

When 6.43 and Winbox 3.14 will be released, then both of them will work together just fine.

And will the new Winbox then still support older RouterOS versions?
This time I first upgraded Winbox and expected to be able to manage my existing routers and upgrade one of them, however that failed as I cannot change the release channel.

Posted: **Fri May 25, 2018 2:58 pm**

You can change release channel, just close the window and open open it again.

Posted: **Fri May 25, 2018 3:46 pm**

I have a feeling that the API calls cannot authenticate now!
API authentication method have changed, see API manual:
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

How secure is plaintext password over insecure connection?.. Will there be any change in it back to challenge-response auth?

Posted: **Fri May 25, 2018 3:48 pm**

For secure connection use api-ssl

Posted: **Fri May 25, 2018 4:31 pm**

Will there be any change in it back to challenge-response auth?

In general, challenge-response auth protocols require the availability of the unhashed password on the router and that is what is being removed for security reasons.
There are tricks around that but those protocols are often regarded as not very secure either.

Posted: **Fri May 25, 2018 5:04 pm**

Please Help! I upgraded to 6.43rc17, could not enter and reset the settings. Now I can not go in with a new winbox, not with an old winbox. Version of the nethinstall that is needed to update, I could not find on the download page.

Posted: **Fri May 25, 2018 5:10 pm**

Please Help! I upgraded to 6.43rc17, could not enter and reset the settings. Now I can not go in with a new winbox, not with an old winbox. Version of the nethinstall that is needed to update, I could not find on the download page.

https://www.mikrotik.com/download/share/winbox.exe

Posted: **Fri May 25, 2018 5:18 pm**

New winbox does not work! Wrong password!

Posted: **Fri May 25, 2018 5:57 pm**

New winbox does not work! Wrong password!

download/file.php?id=32109

Posted: **Fri May 25, 2018 6:07 pm**

New winbox does not work! Wrong password!
download/file.php?id=32109

There is an error with this version of winbox::"could not get index missing file".

Posted: **Fri May 25, 2018 6:23 pm**

For secure connection use api-ssl

+ generate your own certificate to exclude MitM
+ check that cert is your cert...

In general, challenge-response auth protocols require the availability of the unhashed password on the router and that is what is being removed for security reasons.
There are tricks around that but those protocols are often regarded as not very secure either.

Why can't router send, for example, salt of the password hash + some challenge, and then client uses that salt to generate hashed password and HMAC with challenge to generate response?

Posted: **Fri May 25, 2018 6:39 pm**

For secure connection use api-ssl

implementing SSL in our utilities is a problem (time etc). Since the API is proprietary protocol the login phase could be easily changed to not send plain text password and still allow you in the RouterOS to store only hashed passwords. Just make the 'challenge' hash from the hashed password not from plaintext one. If the password hash is easily usable one (i.e. if we can use it in our scripts to create the hash from password the same way the ROS does) it should work fine.

Posted: **Fri May 25, 2018 6:54 pm**

I have lost winbox acces since i upgraded to version 17
I still can log via ssh, webfig ...
Do I need to change something?

Thanks

Posted: **Fri May 25, 2018 6:56 pm**

Sure. Newer winbox.

Posted: **Fri May 25, 2018 7:57 pm**

Anyone have netinstall for 6.43rc17?

Posted: **Fri May 25, 2018 8:00 pm**

That version has been withdrawn. You would not want to install that! Get the 6.43rc19

Posted: **Fri May 25, 2018 8:08 pm**

That version has been withdrawn. You would not want to install that! Get the 6.43rc19

Netinstall 6.43rc19 does not work. I think for routeros 6.43rc17 need netinstall 6.43rc17.

Posted: **Fri May 25, 2018 8:22 pm**

No. When it doesn't work it simply indicates you are doing something wrong in the procedure.

Posted: **Fri May 25, 2018 9:12 pm**

API authentication method have changed, see API manual:
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

Wait, the first step in the post-v6.43 login method is to send the password in plain text? Who the hell thought that was a good idea?

Posted: **Fri May 25, 2018 9:22 pm**

Hi,
i have RBwAPG-5HacT2HnD - wAP AC. I have upgraded to cr17. I cant login with admin / no password after reset. i did try with winbox 3.14rc and with multiple older versions but with no success. Plz help me get my wAP AC under my control.
I even tried netinstall. I did install when mikrotik showed in table, but there was no reboot after that. Still on rc17 after install. I tried rc19 and previus version.

Posted: **Fri May 25, 2018 11:04 pm**

Login by Winbox does not work but SSH and Telnet works

Posted: **Sat May 26, 2018 4:47 am**

Login by Winbox does not work but SSH and Telnet works

Winbox 3.14RC work fine.... What's wrong with me?

Posted: **Sat May 26, 2018 6:53 am**

I reset my cfg with no default settings how do I get back in? It's over 300ft on a tower. I can mac telnet, but it tells me password is wrong.

Posted: **Sat May 26, 2018 7:23 am**

SSH and telnet returns wrong user and password.

Posted: **Sat May 26, 2018 7:27 am**

Cmon guys! Give as a way to get our MicroTiks under out control. I have tried everting that i could find here.

Posted: **Sat May 26, 2018 7:32 am**

It's been defaulted with no cfg. It has no IP address so no SSH. I can mac telnet and that's it.

Posted: **Sat May 26, 2018 8:27 am**

I reset my cfg with no default settings how do I get back in? It's over 300ft on a tower. I can mac telnet, but it tells me password is wrong.

download last winbox 3.14RC and "login great again".

Posted: **Sat May 26, 2018 8:32 am**

http://prntscr.com/jmsaj1

Posted: **Sat May 26, 2018 9:21 am**

Working. Latency tho working?

Posted: **Sat May 26, 2018 9:36 am**

Same here, can't login after upgrading both using WinBox and MAC telnet.
Only can connect using SSH with public key auth configured.

Posted: **Sat May 26, 2018 5:54 pm**

Why those who cannot login even installed the rc version?

Posted: **Sat May 26, 2018 6:11 pm**

Why those who cannot login even installed the rc version?

I was experiencing very low download speeds. Been tying several rc versions. But now i have one AP and i cant get on it. Is there anything i can do???? Netinstall recognizes my AP but does not install.

Posted: **Sun May 27, 2018 10:54 pm**

couldn't login , incorrect password

i can login thru web browser just fine

i heard that i need to use winbox 3.14rc but where can i find it?

only 3.13 available to download

Posted: **Sun May 27, 2018 11:01 pm**

WinBox 3.14RC
viewtopic.php?f=21&t=133420&start=150#p664062

Posted: **Mon May 28, 2018 11:25 am**

What a mess.

First I connected via serial. Then I reformatted my NAND. So I Netinstalled 6.41.4 as to me that seems like the only stable version. I then updated firmware to the 6.41.4.. I formatted NAND again to be sure once I was sure of my firmware. I netinstalled 6.41.4 again and used a backup from months ago. This resulted in a clean install using a truly stable version of RouterOS. I dont consider 6.42.x or 6.43.x stable.

Once I had that up and going. I repartitioned to 2. I copied my known good clean install into the second partition. Copied the config. i then made it active and rebooted to change to it and verified it was good.

I then switched back and upgraded 6.41.4 to 6.43.19. Of course I lost Winbox access, however, Winbox 2.x works great as it does not use authentication.

So ive been running 6.43.19 for 3 days on a SOHO setup and its working fine. No issues in my simple test setup other then no 3.x Winbox and NO NETWATCH.

I do have a production older PPC based router which is stuck on 6.42.1 and only has 6MB of disc space left and so I cant update it. This sudden irreversible loss of discspace making it impossible to upgrade/downgrade is a unpatched issue that so far is kinda random. But it also occurs with 43RC so watch your system/resources/diskspace. The only way to fix this is NAND format and Netinstall.

Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.

So for me 6.41.4, all services disabled except Winbox and that set to LAN side only with a custom port.

MIKROTIK - PLEASE REVIEW AND CORRECT ALL KNOWN ISSUES BEFORE ADDING ANY NEW FEATURES. FOCUS YOUR STAFF ON GETTING THINGS STABLE AND RESTORING LOST FEATURES LIKE NETWATCH. 43RC19 is close. Fix authentication and add Netwatch.

Posted: **Mon May 28, 2018 11:30 am**

@Xymox,
what have we (forum users) done to you?
Please stop flooding forum with useless texts. if you have to say something ugly to mikrotik staff, please write directly to support, not here.

What a mess.

First I connected via serial. Then I reformatted my NAND. So I Netinstalled 6.41.4 as to me that seems like the only stable version. I then updated firmware to the 6.41.4.. I formatted NAND again to be sure once I was sure of my firmware. I netinstalled 6.41.4 again and used a backup from months ago. This resulted in a clean install using a truly stable version of RouterOS. I dont consider 6.42.x or 6.43.x stable.

Once I had that up and going. I repartitioned to 2. I copied my known good clean install into the second partition. Copied the config. i then made it active and rebooted to change to it and verified it was good.

I then switched back and upgraded 6.41.4 to 6.43.19. Of course I lost Winbox access, however, Winbox 2.x works great as it does not use authentication.

So ive been running 6.43.19 for 3 days on a SOHO setup and its working fine. No issues in my simple test setup other then no 3.x Winbox and NO NETWATCH.

I do have a production older PPC based router which is stuck on 6.42.1 and only has 6MB of disc space left and so I cant update it. This sudden irreversible loss of discspace making it impossible to upgrade/downgrade is a unpatched issue that so far is kinda random. But it also occurs with 43RC so watch your system/resources/diskspace. The only way to fix this is NAND format and Netinstall.

Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.

So for me 6.41.4, all services disabled except Winbox and that set to LAN side only with a custom port.

MIKROTIK - PLEASE REVIEW AND CORRECT ALL KNOWN ISSUES BEFORE ADDING ANY NEW FEATURES. FOCUS YOUR STAFF ON GETTING THINGS STABLE AND RESTORING LOST FEATURES LIKE NETWATCH. 43RC19 is close. Fix authentication and add Netwatch.

Posted: **Mon May 28, 2018 11:35 am**

Winbox v3.14 has been released:
viewtopic.php?f=21&t=134940

Posted: **Mon May 28, 2018 9:47 pm**

@Xymox,
what have we (forum users) done to you?
Please stop flooding forum with useless texts. if you have to say something ugly to mikrotik staff, please write directly to support, not here.

The forum users here are awesome. So is Mikrotik. Ive been using ONLY mikrotik products for 8 years. Im confident things will get resolved. BUT. Im concerned by all these missteps in a row over the last 2 months.

A manufacturers public forum is the correct venue for my unfavorable posts. This thread is the correct venue for these specific posts as my posts deal with a lack of quality control of a release candidate.

My post of doing a NAND format and Netinstall of 6.41.4 before upgrading to 6.43RC19 and then reporting good results is what this thread is for and on topic. I dont see anyone doing a NAND format before Netinstall, so, I thought it a good idea to cover that and cover how I do a really clean install using partitions to test a RC.

I have experience in working technical issues until they are resolved. I discovered and have worked the Intel Puma issue all the way to Press coverage, a CVE, a class action, a dedicated web site for the issue and finally a firmware update from ALL cable modem mfgrs that is slowly resolving the issue. My web site on the Intel Puma issue http://badmodems.com/ My efforts over 2 years resulted in a change of management at Intel in the connected home division and a better product. It also changed how cable modem devices are tested adding high temporal resolution latency tests as std stuff at the chip development level. I changed the cable modem chip industry and made latency part of the scope in development.

I LOVE Mikrotik, but sometimes some tuff love is required in a relationship

Posted: **Mon May 28, 2018 9:55 pm**

Works fine with CHR!

Posted: **Tue May 29, 2018 1:48 pm**

Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.

If you have been following these topics on the forum for some time, you shold know, they are exactly that.

Unofficially "rc" = "beta" or "nightly build". "current" = "rc". "bugfix" ="stable"

Posted: **Tue May 29, 2018 1:58 pm**

What a small step for normis but huge jump for the mikrotik community!

Posted: **Tue May 29, 2018 2:14 pm**

I find it confusing that any thread about software coming from Miktotik uses the word released in the subject and lets save that word solely for the RC.

Legacy = no further developed
Bug fixed = only security and bug fixes applied
Current = bleeding edge and not always stable
Release Candidate = can break or even brick your device so be warned and prepared

Posted: **Tue May 29, 2018 2:18 pm**

I thought the a warning was included in every post where a new RC is posted?

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.

Posted: **Tue May 29, 2018 2:37 pm**

That warning is perfectly clear. Unfortunately some people don't read.

Posted: **Tue May 29, 2018 2:54 pm**

That warning is perfectly clear. Unfortunately some people don't read.

Unfortunately some people can't read it if they don't visit the forum

There's no such warning in WinBox, for example.

Posted: **Tue May 29, 2018 5:37 pm**

Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.
If you have been following these topics on the forum for some time, you shold know, they are exactly that.

Unofficially "rc" = "beta" or "nightly build". "current" = "rc". "bugfix" ="stable"

So rc!=rc that makes no sense!

Posted: **Tue May 29, 2018 5:40 pm**

That warning is perfectly clear. Unfortunately some people don't read.
Unfortunately some people can't read it if they don't visit the forum There's no such warning in WinBox, for example.

And why should people have to read these things, just make RC a real RC and not a nightly.
Naming of releases should be self explanatory

Posted: **Tue May 29, 2018 5:51 pm**

And why should people have to read these things, just make RC a real RC and not a nightly.
Naming of releases should be self explanatory

... or call it "Recently Compiled" instead of "Release Candidate"...

Posted: **Tue May 29, 2018 6:14 pm**

And why should people have to read these things, just make RC a real RC and not a nightly.
Naming of releases should be self explanatory
... or call it "Recently Compiled" instead of "Release Candidate"...

Or call it "Ridiculous Count"...

Once Linus Torvalds stated:

However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all agree that it stands for "Ridiculous Count" rather than "Release Candidate".

Posted: **Wed May 30, 2018 4:17 am**

Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.
If you have been following these topics on the forum for some time, you shold know, they are exactly that.

Unofficially "rc" = "beta" or "nightly build". "current" = "rc". "bugfix" ="stable"

As I have said. I love Mikrotik. I literally use nothing else. For 8+ years. I have great respect for Normis here on the forum. I NEVER intended any disrespect to anyone or to Mikrotik. In fact, I have great respect that they have allowed me to post these posts.

I have FLOWN out to 5 client sites so far where I have had recover routers that got botched by the "stable" 6.42.1 using Netinstall. I totaled those up a week ago. Ive spent $4,170 in travel costs and that does not include lost income during this last month. I have not complained to Mikrotik about this. As Mikrotik has been incredibly stable for the whole 8+ years ive used it, I gave them a lot of room for oopsie. Mistakes happen. Its OK. So I just absorbed the costs. The mess was caused by a security issue, not thier fault. BUT. Fixing all the issues from 42.1 to 42.2 in such a short period was stunning. They did a amazing job.

The RC's have been so good and so stable and well thought out and tested for 8+ years they were really almost stable releases. This is what I have come to expect from Mikrotik, stunningly good RCs. So these recent issues with RCs caught me really off guard as its not what I have come to expect. So that is why im concerned. Im concerned something has happened to Mikrotik that *might* be a issue long term. Im worried..

Normis, jarda.. What is the plan for Netwatch ? Has it been permanently deprecated ? I have asked this a number of times and ive never had a response.

Ive been testing RC19.. For my use in a simple NATed SOHO environment its working perfectly in all respects. For me I would say it could be released as 43.1 as stable. Im encouraged that this whole last 2 months was a oopsie and Mikrotik will get back to killer awesome stable.

I want Netwatch back. There is no technical reason, or security reason, Netwatch cant trigger a script. It can be done securely. It might require some work to get there, but, it can be done. I need this back. I dont remember any other feature ever removed from RouterOS before.

I will not post like this any more. Im sorry for the disruptions. Im happy with RC19. My only issue is I want Netwatch and I will be annoying on this issue. Again, im sorry for the disparaging and disruptive posts...

Posted: **Wed May 30, 2018 7:10 am**

Netwatch... I want it back also. More than that I want it better with more parameters like it was already requested by many people in the past. I am also really unhappy with the actual result. If this was the way that mikrotik want to go further I would need to rethink the way how I use my devices. Hope it was just a mistake that will be corrected as soon as possible.

I have absolutely no relation to mikrotik company. I am the same user like all others here. Maybe I am here more often and have better overview what is said on the forum during the time then others and maybe because of that the global administrator rights were given to me. So I help with fight against spam mainly and trying to keep the forum clean from all aspects. Nothing more. I am not able to say anything more over that what I see here or what I experienced myself. I definitely cannot say anything else than speculations about what mikrotik will or will not do, how or when. Normis, strods, uldis, mrz and others are mikrotik representatives, thay should answer that.

Regarding the travel cost to many sites from the same reason... It looks like you are not testing the new versions before productive implementation. Otherwise I cannot explain to myself how you could break many remote sites at once. I always deploy newer versions in vawes starting on the closest sites and continue with the further if nothing bad happens during a week or so. But never at once.

Posted: **Wed May 30, 2018 7:34 am**

Regarding the Netwatch problem (which actually should not be discussed in 6.43rc version topic) - can anyone provide an example of Netwatch with single line script that is not working but you think that Netwatch should be able to execute it. Please provide single command example. At the moment, we have not seen any actual case (besides misconfiguration due to policies) where this would be a problem.

/tool netwatch add host=x.x.x.x up-script="/system script run test"
/system script add name=test policy=read,write,test,reboot source="/xxxxx"

Send in such example to support@mikrotik.com and we will see what can be improved.

Posted: **Wed May 30, 2018 10:14 am**

Regarding the travel cost to many sites from the same reason... It looks like you are not testing the new versions before productive implementation. Otherwise I cannot explain to myself how you could break many remote sites at once. I always deploy newer versions in vawes starting on the closest sites and continue with the further if nothing bad happens during a week or so. But never at once.

YES this above is MY FAULT. BUT. 42.1 at first seemed fine. I rolled it out on my home setup first and then at one client. It seemed fine. Let it run for a few days. It was a serious security patch with a notice from MT to update immd. I then rolled it out across everyone. Again at first it seemed fine. I did not notice I lost disc space and could no longer upgrade or downgrade some devices. Then DHCP started failing. They started going offline. My only choice was Netinstall - confirmed with support. So I had to buy and fedex some preconfigured routers and have contractors install them at my expense and I had to fly out and fix others. It was a painful process.

I still have them all on 6.41.4 and im carefully working with 43RC to get it where I feel its stable and will move clients over to 43 once its stable ready. Im concerned and under pressure as 41.4 has security issues. I gotta have Netwatch tho to make this work. So this is why im being annoying and serious because i need a stable and working 43.x right away. 42.x does not seem to have any hope of getting Netwatch back. So im focused on 43.

Sorry. All of this is off topic. Sorry again for a off topic post.

The release notes for 6.42 seemed pretty clear. It simply does not do anything but read/write/test and reboot"

"*) netwatch - limit to read, write, test and reboot policies for Netwatch script execution;"

I have a topic I started on this some week or so back. I have posted a Netwatch set of scripts that dont work. viewtopic.php?f=2&t=134538

Im out of town working on site, I will get back in a few days. I will try and get my scripts that are run to support. I have scripts that send emails, turn on/off LEDS and trigger DDNS scripts. They stopped working on the release of 6.42.

Posted: **Wed May 30, 2018 12:44 pm**

Xymox - for example, your Netwatch includes this command "/system script run IPSMTP". So are policies write,read,reboot,test or only some of them, only ones that are enabled on this script? For example, no romon policy, no dude policy, etc. And again - this is not 6.43rc version related discussion.

Posted: **Wed May 30, 2018 1:29 pm**

And again - this is not 6.43rc version related discussion.

Technically, 6.42 topic is locked, so they continue here

Posted: **Wed May 30, 2018 3:26 pm**

Version 6.43rc21 has been released.

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.

MAJOR CHANGES IN v6.43:
----------------------
!) api - changed authentication process (https://wiki.mikrotik.com/wiki/Manual:API#Initial_login);
!) backup - do not encrypt backup file unless password is provided;
!) btest - requires at least v6.43 Bandwidth Test client when connecting to v6.43 or later version server except when authentication is not required;
!) cloud - reworked "/ip cloud ddns-enabled" implementation (suggested to disable service and re-enable after installation process);
!) mac-telnet - require at least v6.43 MAC Telnet client when connecting to v6.43 or later version server;
!) radius - use MS-CHAPv2 for "login" service authentication;
!) romon - require at least v6.43 RoMON agent when connecting to v6.43 or later RoMON client device;
!) webfig - improved authentication process;
!) winbox - improved authentication process excluding man-in-the-middle possibility (Winbox v3.14 required);
----------------------

Other changes in this release:

*) dhcp - added dynamic IPv4/IPv6 "dual-stack" simple queue support, based on client's MAC address;
*) dhcp - fixed DHCP server stuck in invalid state;
*) dhcpv4-server - added "allow-dual-stack-queue" implementation (CLI only);
*) dhcpv6-server - added "allow-dual-stack-queue" implementation (CLI only);
*) kidcontrol - added dynamic accept firewall rules in order to allow limit bandwidth when FastTrack is enabled;
*) lte - do not allow to remove default APN profile;
*) snmp - added "rssi" and "tx-sector-info" value support for w60g type interfaces;
*) vrrp - improved reliability on VRRP interface configured as a bridge port when "use-ip-firewall" is enabled;
*) w60g - added distance measurement (CLI only);
*) winbox - by default specify keepalive timeout value for tunnel type interfaces;
*) winbox - show "System/Health" only on boards that have health monitoring;
*) wireless - added option for RADIUS "called-station-id" format selection;
*) wireless - updated "germany 5.8 ap" and "germany 5.8 fixed p-p" regulatory domain information;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.

Posted: **Wed May 30, 2018 3:55 pm**

Version 6.43rc21 has been released.
*) dhcp - added dynamic IPv4/IPv6 "dual-stack" simple queue support, based on client's MAC address;
*) dhcpv4-server - added "allow-dual-stack-queue" implementation (CLI only);
*) dhcpv6-server - added "allow-dual-stack-queue" implementation (CLI only);

Things, just got interesting!!

Posted: **Wed May 30, 2018 3:59 pm**

I wonder if we can do it manually. And where does dst-mac lookup happen in Packet Flow diagram?

Posted: **Wed May 30, 2018 10:02 pm**

So this means that now we don't need to set the user with 'password recovered' when using windows Radius?

!) radius - use MS-CHAPv2 for "login" service authentication;

Posted: **Wed May 30, 2018 10:35 pm**

Perhaps it's possible for Mikrotik to consider allowing radius authentication for bandwidth tests, whilst restructuring authentication?

Posted: **Wed May 30, 2018 11:36 pm**

*) w60g - added distance measurement (CLI only)

Could someone please explain why we can see this also in rc19? Has it been "re-worked" somehow between rc19 and rc21?

Posted: **Wed May 30, 2018 11:46 pm**

*) dhcp - added dynamic IPv4/IPv6 "dual-stack" simple queue support, based on client's MAC address;
*) dhcp - fixed DHCP server stuck in invalid state;
*) dhcpv4-server - added "allow-dual-stack-queue" implementation (CLI only);
*) dhcpv6-server - added "allow-dual-stack-queue" implementation (CLI only);

Could you please explain how to enable this function?
I've looked at wiki, but there are details only about leases and bindings.
Cheers

Posted: **Thu May 31, 2018 1:13 am**

*) winbox - show "System/Health" only on boards that have health monitoring;

So... Where's my health?

Posted: **Thu May 31, 2018 4:43 am**

I lost 10MB of disc space when I upgraded from RC19 to RC21 on a CCR. Ive seen this same thing on PPC and MIPSBE.. MT Support replicated it and is working on it. After a few upgrades or downgrades you can run out of space and then the only thing you can do is Netinstall as your stuck on whatever version your at. This effects 6.42.x thru 6.43RC21. So careful upgrading as you might be loosing space with each time you do it, this is kinda critical on devices with low disc space.. MT support has seen it, so, its getting worked on.

IMHO always use partitions when you upgrade so its easy to go back.

Posted: **Thu May 31, 2018 5:06 am**

I lost 10MB of disc space when I upgraded from RC19 to RC21 on a CCR. Ive seen this same thing on PPC and MIPSBE.. MT Support replicated it and is working on it. After a few upgrades or downgrades you can run out of space and then the only thing you can do is Netinstall as your stuck on whatever version your at. This effects 6.42.x thru 6.43RC21. So careful upgrading as you might be loosing space with each time you do it, this is kinda critical on devices with low disc space.. MT support has seen it, so, its getting worked on.

IMHO always use partitions when you upgrade so its easy to go back.

I wish Mikrotik would just move to a compressed root image thats decompressed to a Read-Only RAM disk on boot, with a seperate R/W partition for persistent data (configuration files), accross all platforms. RAM is cheap, and a lot of existing platforms already have enough RAM to do this.

There would be the following benefits:

Simpler
* No need for seperate partitions, just let the bootloader select from the different compressed root images.

Safer
* Upgrades are safer as no files would need to be overwritten, and there would be no chance of corrupted filesystems or varied binary versions
* A compressed root image is a "known good" self contained "system" that Mikrotik engineers can QA and test more thoroughly, and know it is going to work. There are no variations between devices due to the upgrade path or corruption.

Higher Security
* The compressed root could be "signed" by Mikrotik and the bootloader would only load signed root images.
* Hackers could not over-write or add binaries to the READ ONLY root filesystem that is running from RAM
* Any maliciously manipulated files would be gone as soon as the device was rebooted.

There are many reasons why the big boys do it this way... Mikrotik should too!

Posted: **Thu May 31, 2018 6:59 am**

Xymox - for example, your Netwatch includes this command "/system script run IPSMTP". So are policies write,read,reboot,test or only some of them, only ones that are enabled on this script? For example, no romon policy, no dude policy, etc. And again - this is not 6.43rc version related discussion.

Netwatch problem persist

tested on rb750UP with routeros 6.43RC21

No log error, only log the netwatch up or down, script dont run, no error messages

User owner of the script permissions full

Captura.JPG

Posted: **Thu May 31, 2018 7:25 am**

Xymox - for example, your Netwatch includes this command "/system script run IPSMTP". So are policies write,read,reboot,test or only some of them, only ones that are enabled on this script? For example, no romon policy, no dude policy, etc. And again - this is not 6.43rc version related discussion.
Netwatch problem persist

tested on rb750UP with routeros 6.43RC21

No log error, only log the netwatch up or down, script dont run, no error messages

User owner of the script permissions full

Captura.JPG

MT has said this thread is not the place for Netwatch discussion. So I started a separate thread. viewtopic.php?f=2&t=134538

Posted: **Thu May 31, 2018 8:27 am**

valera5505 - Seems that we have missed this one. We will remove this menu from this RouterBOARD too;
Xymox - We will fix the problem with upgrades that results into too much disk space consumed;
chechito - viewtopic.php?f=2&t=134538#p665400
Everyone - Please keep this topic related to v6.43rc version since most of the users visit this page based on its subject. If you have other problems or suggestions, then feel free to create new topics or contact us directly through support@mikrotik.com

Posted: **Thu May 31, 2018 9:46 am**

Everyone who complained about the Netwatch issue - Please see this topic viewtopic.php?f=2&t=134538

Posted: **Thu May 31, 2018 10:53 am**

*) dhcp - added dynamic IPv4/IPv6 "dual-stack" simple queue support, based on client's MAC address;
*) dhcp - fixed DHCP server stuck in invalid state;
*) dhcpv4-server - added "allow-dual-stack-queue" implementation (CLI only);
*) dhcpv6-server - added "allow-dual-stack-queue" implementation (CLI only);
Could you please explain how to enable this function?
I've looked at wiki, but there are details only about leases and bindings.
Cheers

The wiki has been updated with examples:
https://wiki.mikrotik.com/wiki/Manual:I ... e_limiting
https://wiki.mikrotik.com/wiki/Manual:I ... e_limiting

Posted: **Thu May 31, 2018 11:57 am**

When router's identity is very long (for example, "xxx-us-east1.c.xxxxxxx-xxxxx.internal"), Backup files are generated via WinBox (if you don't set custom name) with corrupted names (like "&_jw-20180327-1313.backup") - looks like buffer overflow or something

Posted: **Thu May 31, 2018 5:21 pm**

The wiki has been updated with examples:
https://wiki.mikrotik.com/wiki/Manual:I ... e_limiting
https://wiki.mikrotik.com/wiki/Manual:I ... e_limiting

Thanks for that, artz!
However, I couldn't find a way to enable this for the whole server, not just for the static leases/bindings.
Could you please check this?

We are trying this in an IPoE solution via DHCP Option 82 via RADIUS to provide dual-stack network with queues and accounting.
We are almost there!
Cheers

Posted: **Thu May 31, 2018 8:06 pm**

Everyone who complained about the Netwatch issue - Please see this topic viewtopic.php?f=2&t=134538

I only have suggestions for improvement:

viewtopic.php?f=14&t=133179&p=654580&hi ... ch#p654580

Otherwise it is better that it be discontinued because it is possible to do better things using scripts and schedules.

Posted: **Fri Jun 01, 2018 2:14 am**

Could anyone give an example of how to connect in the api PHP in the new version of mikrotik v3.43rc21

Posted: **Fri Jun 01, 2018 7:53 am**

This makes sense, but, a caution is needed.. If you downgrade from 43RC21 to 42.3 you will be locked out, even at the command line. The new authentication is not backward compatible. So you cannot downgrade.

You also cannot copy the 43RC21 config to 42.3 using the copy config command between partitions.

I dont think thats a bug. It makes sense that previous version of the OS cant read the new authentication files.

It would be good if a downgrade converted the new to the old auth. But that sounds complicated..

Just a caution about this as you can get locked out of a router and only a Netinstall will fix it.

I use partitions, so when i got locked out, I just went back to the other partition.

Posted: **Fri Jun 01, 2018 11:14 am**

Could anyone give an example of how to connect in the api PHP in the new version of mikrotik v3.43rc21

https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

Posted: **Fri Jun 01, 2018 11:30 am**

Will we ever see BGP4 SNMP MIBs on ROS? Please!

Posted: **Fri Jun 01, 2018 11:31 am**

Yes, but not in v6. Currently for monitoring you can already use API.

Posted: **Fri Jun 01, 2018 1:18 pm**

Thanks Xymox, but I know that in this version can work the connection with the API has just changed the way the routeros receives the password. I still do not know which change is required to connect in this current version

I use the class https://github.com/BenMenking/routeros- ... .class.php to connect me with the following code on the page

require ('routeros_api.class.php');

$ API = new RoutersAPI ();
$ API-> debug = false;

if ($ API-> connect ($ ip_RB, $ RBUser, $ password_RB)) {

this version no longer works and can not fix the problem at https://wiki.mikrotik.com/wiki/Manual:API#Initial_login.

I think I need help.

Posted: **Fri Jun 01, 2018 1:35 pm**

Could anyone give an example of how to connect in the api PHP in the new version of mikrotik v3.43rc21
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

I modified the php file for now this way and it works... it is not detecting prior version... I hope 6.43 comes out soon to keep it like that

public function connect($ip, $login, $password) {
for ($ATTEMPT = 1; $ATTEMPT <= $this->attempts; $ATTEMPT++) {
$this->connected = false;
$PROTOCOL = ($this->ssl ? 'ssl://' : '' );
$context = stream_context_create(array('ssl' => array('ciphers' => 'ADH:ALL', 'verify_peer' => false, 'verify_peer_name' => false)));
$this->debug('Connection attempt #' . $ATTEMPT . ' to ' . $PROTOCOL . $ip . ':' . $this->port . '...');
$this->socket = @stream_socket_client($PROTOCOL . $ip . ':' . $this->port, $this->error_no, $this->error_str, $this->timeout, STREAM_CLIENT_CONNECT, $context);
// pre 6.43
// if ($this->socket) {
// socket_set_timeout($this->socket, $this->timeout);
// $this->write('/login');
// $RESPONSE = $this->read(false);
// if (isset($RESPONSE[0]) && $RESPONSE[0] == '!done') {
// $MATCHES = array();
// if (preg_match_all('/[^=]+/i', $RESPONSE[1], $MATCHES)) {
// if ($MATCHES[0][0] == 'ret' && strlen($MATCHES[0][1]) == 32) {
// $this->write('/login', false);
// $this->write('=name=' . $login, false);
// $this->write('=response=00' . md5(chr(0) . $password . pack('H*', $MATCHES[0][1])));
// $RESPONSE = $this->read(false);
// if (isset($RESPONSE[0]) && $RESPONSE[0] == '!done') {
// $this->connected = true;
// break;
// }
// }
// }
// }
// fclose($this->socket);
// }
// post 6.43
if ($this->socket) {
socket_set_timeout($this->socket, $this->timeout);
$this->write('/login', false);
$this->write('=name=' . $login, false);
$this->write('=password=' . $password);
$RESPONSE = $this->read(false);
if (isset($RESPONSE[0]) && $RESPONSE[0] == '!done') {
$this->connected = true;
break;
}
fclose($this->socket);
}
sleep($this->delay);
}

if ($this->connected) {
$this->debug('Connected...');
} else {
$this->debug('Error...');
}
return $this->connected;
}

Posted: **Fri Jun 01, 2018 1:58 pm**

You don't have to check version.

* Send /login with username and password in plain text
* if response is with challenge then fall back to old login method
* otherwise check status if login is successful

As an example see how it is done on python example in the wiki

Posted: **Fri Jun 01, 2018 3:44 pm**

You don't have to check version.

* Send /login with username and password in plain text
* if response is with challenge then fall back to old login method
* otherwise check status if login is successful

As an example see how it is done on python example in the wiki

check version one would need if he has to manage multiple devices prior the change and after like me.

I am managing 500+ sites so my provisioning platform would need to know the routeros version to use the proper login mechanism.

Unless of course I update them all before I change my php file in the production environment

Posted: **Fri Jun 01, 2018 3:47 pm**

As I mentioned you do not need to know version to log in. Fall back to old login procedure if router responds with =ret=.

Posted: **Sat Jun 02, 2018 2:45 am**

thank you very much genesispro

Posted: **Sat Jun 02, 2018 7:23 am**

Based on mrz suggestions I changed API to work with old and new login style.

 if ($this->socket) {
                socket_set_timeout($this->socket, $this->timeout);
                // RouterOS >= 6.43
                $this->write('/login', false);
                $this->write('=name=' . $login, false);
                $this->write('=password=' . $password);
                $RESPONSE = $this->read(false);
                if (isset($RESPONSE[0]) && $RESPONSE[0] == '!done') {
                                //RouterOs < 6.43
                                if  (isset($RESPONSE[1])) {  
                                    $MATCHES = array();
                                    if (preg_match_all('/[^=]+/i', $RESPONSE[1], $MATCHES)) {
                                        if ($MATCHES[0][0] == 'ret' && strlen($MATCHES[0][1]) == 32) {
                                            $this->write('/login', false);
                                            $this->write('=name=' . $login, false);
                                            $this->write('=response=00' . md5(chr(0) . $password . pack('H*', $MATCHES[0][1])));
                                            $RESPONSE = $this->read(false);
                                            if (isset($RESPONSE[0]) && $RESPONSE[0] == '!done') {
                                                $this->connected = true;
                                                break;
                                                }
                                            
                                            }
                                        }   
                                    }
                                else
                                {    
                                    $this->connected = true;
                                    break;
                                }
                            }
                                    
                fclose($this->socket);
            }

Also here is complete api.inc.php file

Posted: **Sat Jun 02, 2018 8:28 am**

This is really ironic. Introducing unencrypted plain text authentication in 2018.

I wish 6.43rc introduces SCRAM or removes non-SSL api service.

Posted: **Sat Jun 02, 2018 9:26 am**

I did test upgrade from 5.26 to this version. Just for testing. Everything went well. Upgrade failed for you due to configuration or something like thta. In general it works just fine.

Nothing worked for me either when I upgraded from v5.26 straight to 6.42.3 and I tested it in different platforms with the same exact boot problem. Everything stopped working after the upgrade and you had to use netinstall to recover. However everything worked good when upgrading to bugfix first and then to current. I had no boot problems whatsoever. However I could not get a clean backup when upgrading from bugfix to current. I get always an error so after both upgrades are done you have to do a final step and reset to factory defaults and then copy paste the original rsc file.

Posted: **Sat Jun 02, 2018 10:30 am**

It is not really reasonable to expect a smooth upgrade with such a large version jump. Often things change in configuration and the upgrade
procedure converts existing configuration to new, but it cannot be expected to work when there are many changes in the same area.
So when you really want to do such an upgrade, do it in a couple of steps. First upgrade to an early 6.x release e.g. 6.1 then to a later
release that has been used very widely like 6.29 and then upgrade to 6.40 as there were big changes in 6.41.
From there you can upgrade to 6.42 and it will probably work just fine.
And, keep "current" a bit more regularly. Running such old versions is a security risk, that is widely known in all of the software world.

Posted: **Sun Jun 03, 2018 2:22 am**

When doing RCs I think its important to do a good job of testing. Testing a big version jump is good for MT to know what happens. HOWEVER that should only be done as a test with the goal of testing a big version jump. I would PLAN for it to fail and a NAND Format and netinstall required. Again the best way to do this kind of thing is with partitions if you your device supports them. That way you just RS232 console boot and pick Y and change back to the working partition and report what went wrong.

I have a disicplene and proceedure I always follow when testing a RC or even a new stable.

1. Make a backup, export compact. Pull both files off router. Copy files to SD card if present so if I have to do a NAND format and netinstall my backup files are still handy.
1. Copy current working partition to the other partition. Copy config to other partition.
2. Make the new partition active and reboot to it. Make sure all is well.
3. Winbox Packages update..
4. Test...
5 If all goes well, then I NAND format and Netinstall the newest version. COpy over the backup or import the export compact.

SOmetimes I simply config the router by hand rather then using a backup. I consider this cleaner and less likely to import anything from a old version that might cause a issue.

I then run this for a while on my own home router and test things.

If all goes well and its a stable release.. I try and NAND format and Netinstall every client router if I can rather then doing a update. I consider this cleaner.

So just updating a old version without a good partition and without Netinstall and a serial cable could well lead to a headache. I consider testing RCs pretty important to MT, so, I try and do the cleanest setups I can. I also have a variety of devices at home I use for testing. I have a CCR1036, a 1009, a 2011 and even a mAP lite. I do all of them and look for issues before rolling things out to my clients.

Posted: **Sun Jun 03, 2018 4:09 pm**

And, keep "current" a bit more regularly. Running such old versions is a security risk, that is widely known in all of the software world.

Security risk is really not as important as functionality and speed to me in some installations as those old versions are not accessible. I was actually forced to downgrade from current as there is lack of MT support and broken code in later versions of ROS for the dual nstream, besides a few other problems, like the backup error current ROS almost always has. Those old versions have been working rock solid for many years. Sometimes upgrading is not a very wise choice.

Posted: **Sun Jun 03, 2018 5:32 pm**

I really like the fact that the wheels stay on the car when drive on the highway. Without security being as good as possible someone else than you can use your router to do harm and thanks to you at a higher speed.

Posted: **Sun Jun 03, 2018 5:43 pm**

Depends on how well your car is heavily guarded or not. lol

Posted: **Mon Jun 04, 2018 8:51 am**

We need a netinstall

oops.jpg

Posted: **Mon Jun 04, 2018 11:59 am**

My tire won't survive a caltrop, sometimes a IED is needed if you are have a more secure tire.

Posted: **Mon Jun 04, 2018 2:37 pm**

It is possible add this comand into winbox?

/interface ethernet poe settings set ether1-poe-in-long-cable=yes
Thanks

Posted: **Mon Jun 04, 2018 4:08 pm**

!) btest - requires at least v6.43 Bandwidth Test client when connecting to v6.43 or later version server except when authentication is not required;

So where is new Windows Bandwidth Test app?

Posted: **Mon Jun 04, 2018 5:57 pm**

HI,

Please help: after upgrading two NetBox to latest 6.43rc21 I can't access them anymore! Winbox reports "wrong username or password". I access then via Dude, so I know that user/pass is OK. Any idea how to access those devices?

P.S. Previous version was 6.43rc6

Posted: **Mon Jun 04, 2018 6:02 pm**

Version 6.43rc21 has been released.

MAJOR CHANGES IN v6.43:
----------------------
!) winbox - improved authentication process excluding man-in-the-middle possibility (Winbox v3.14 required);
----------------------

You can find Winbox here: https://mikrotik.com/download

Posted: **Mon Jun 04, 2018 6:06 pm**

Version 6.43rc21 has been released.

MAJOR CHANGES IN v6.43:
----------------------
!) winbox - improved authentication process excluding man-in-the-middle possibility (Winbox v3.14 required);
----------------------

You can find Winbox here: https://mikrotik.com/download

Thanks. It's working for Winbox, but Dude is still complaining

Posted: **Tue Jun 05, 2018 8:55 am**

I know I have covered this before and Mikrotik has reproduced the issue and is going to issue a fix, but, I have further isolated the issue and wated to report it and mention again the possible danger.

I took a CCR1009-8G-1S-1S+ and split the disc space into 2 partitions, 64MB each.
I Netinstalled 6.42.3.
I winbox upgraded it to 6.43.RC21
Doing this took up too much disc space and now I cannot upgrade or downgrade. To recover it will require a Netinstall or falling back to one partition.

Something is taking up too much disc space on upgrades. This effects all the versions ive tested. Tile, MIPSBE and PPC. Some units have enough disc space where this is not a issue, some devices the OS does not take up the same % of disc space. So this issue effects different devices differently. Ive got a RB1100 and it will run out of space with just 1 partition.

It also seems cumulitive. So if you do stil have room to upgrade or downgrade again, you space becomes even smaller until you eventually cant upgrade or downgrade and netinstall is required.

So watch your disc space.

Mikrotik is top top of this. I just wanted to post another caution and point out its easily reproducable and most likely everybody has this issue to some degree right now.

I also read symptoms that seemed the same over on the 6.42.3 thread, so, this might effect more then the RC. I have not tested that.

Posted: **Tue Jun 05, 2018 1:20 pm**

How do you watch the space of your default drive? I can't seem to find this anywhere. I can tell from the backup file as it gets larger and larger every time that there is something wrong with the space but how do you know the consistency and reliability of the rest of your files? /System check-installation reports everything ok and the old system check-disk is no longer there.

Posted: **Tue Jun 05, 2018 2:13 pm**

/System check-installation reports everything ok and the old system check-disk is no longer there.

As I wrote in the 6.42.3 thread, the check-installation function does not seem to have the claimed new functionality
to check for unwanted extra files (introduced some versions ago to detect and remove trojans etc).

Posted: **Tue Jun 05, 2018 3:22 pm**

Version 6.43rc23 has been released.

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.

MAJOR CHANGES IN v6.43:
----------------------
!) api - changed authentication process (https://wiki.mikrotik.com/wiki/Manual:API#Initial_login);
!) backup - do not encrypt backup file unless password is provided;
!) btest - requires at least v6.43 Bandwidth Test client when connecting to v6.43 or later version server except when authentication is not required;
!) cloud - reworked "/ip cloud ddns-enabled" implementation (suggested to disable service and re-enable after installation process);
!) mac-telnet - require at least v6.43 MAC Telnet client when connecting to v6.43 or later version server;
!) radius - use MS-CHAPv2 for "login" service authentication;
!) romon - require at least v6.43 RoMON agent when connecting to v6.43 or later RoMON client device;
!) webfig - improved authentication process;
!) winbox - improved authentication process excluding man-in-the-middle possibility (Winbox v3.14 required);
----------------------

Other changes in this release:

*) backup - generate proper file name when router identity is longer than 32 symbols;
*) bridge - added ingress filtering options to bridge interface;
*) bridge - added initial Q-in-Q support;
*) capsman - increase timeout for the CAP to CAPsMAN communication;
*) certificate - added "expires-after" parameter;
*) certificate - fixed "add-scep" template existence check when signing certificate;
*) chr - by default enable link state tracking for virtual drivers with "/interface ethernet disable-running-check=no";
*) chr - fixed boot on hosts older than Windows Server 2012 when running CHR on Hyper-V;
*) chr - fixed interface name assign process when running CHR on Hyper-V;
*) chr - fixed MTU changing process when running CHR on Hyper-V;
*) chr - fixed various network hang scenarios when running CHR on Hyper-V;
*) chr - provide part of network interface GUID at the beginning of "bindstr2" value when running CHR on Hyper-V;
*) console - fixed script permissions if script is executed by other RouterOS service;
*) dhcpv6-server - added initial dynamic simple queue support;
*) ipsec - added "responder" parameter for "mode-config" to allow multiple initiator configurations;
*) ipsec - separate phase1 proposal configuration from peer menu;
*) lte - improved modem event processing;
*) ppp - fixed "hunged up" grammar to "hung up" within PPP log messages;
*) ppp - show comments from "/ppp secrets" menu within "/ppp active" menu when client is connected;
*) quickset - added missing wireless "channel-width" settings;
*) quickset - added support for "5ghz-a/n" band when CPE mode is used;
*) quickset - recognize 160 MHz channel as HomeAP mode;
*) romon - fixed RoMON services becoming unavailable after disabled once during active scanning process;
*) supout - added "partitions" section to supout file;
*) switch - added support for port isolation by switch chip;
*) webfig - properly display time interval within Kid Control menu;
*) webfig - properly show NTP clients "last-adjustment" value;
*) winbox - added "poe-fault" LED trigger;
*) winbox - added "secondary-channel" setting to wireless interface if 80 MHz mode is selected;
*) winbox - added missing "dscp" and "clamp-tcp-mss" settings to IPv6 tunnels;
*) winbox - allow to specify full URL in SCEP certificate signing process;
*) winbox - fixed arrow key handling within table filter fields;
*) winbox - properly close session when uploading multiple files to the router at the same time;
*) winbox - removed duplicate "20/40/80MHz" value from "channel-width" setting options;
*) winbox - show "scep-url" for certificates;
*) winbox - show "System/Health" only on boards that have health monitoring;
*) winbox - show firmware upgrade message at the bottom of "System/RouterBOARD" menu;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.

Posted: **Tue Jun 05, 2018 5:03 pm**

is there a final period to close this RC and put it into production mode?

I'm waiting to put into production but do not feel safe with it.

Posted: **Tue Jun 05, 2018 6:48 pm**

*) chr - provide part of network interface GUID at the beginning of "bindstr2" value when running CHR on Hyper-V;

What are those bindstr and bindstr2?

Posted: **Tue Jun 05, 2018 8:06 pm**

I am impressed. Thanks for listening to us all.

Posted: **Tue Jun 05, 2018 11:54 pm**

*) lte - improved modem event processing;

is it for SXT LTE?

Posted: **Wed Jun 06, 2018 12:55 am**

Ive rolled out RC23 on 2 devices. A 2011 and a CCR1016. No obvious issues on a simple SOHO setup.

Interestingly I gained a bunch of disc space.. Not sure if thats a fix or just a random things. I gained on both the above devices. Both devices were Netinstall 6.42.3 > RC21 > RC23..

Posted: **Wed Jun 06, 2018 9:22 am**

Does rc23 fix the w60g issues seen in rc19 and rc21?

Posted: **Wed Jun 06, 2018 5:28 pm**

You don't have to check version.

* Send /login with username and password in plain text
* if response is with challenge then fall back to old login method
* otherwise check status if login is successful

As an example see how it is done on python example in the wiki

Hello @mrz ,

Reading https://wiki.mikrotik.com/wiki/Manual:API_Python3

Can you please tell me if the function login is compatible with v 6.42 and v 6.43 ?

 def login(self, username, pwd):
        for repl, attrs in self.talk(["/login"]):
            chal = binascii.unhexlify((attrs['=ret']).encode('UTF-8'))
        md = hashlib.md5()
        md.update(b'\x00')
        md.update(pwd.encode('UTF-8'))
        md.update(chal)
        self.talk(["/login", "=name=" + username,
                   "=response=00" + binascii.hexlify(md.digest()).decode('UTF-8') ])

Thanks

Posted: **Wed Jun 06, 2018 7:31 pm**

Does rc23 fix the w60g issues seen in rc19 and rc21?

seems, not. rc23 even worse for LHG. alot disconnects (~50/hour). after roll back to 6.42.3 - rockstable.

Posted: **Thu Jun 07, 2018 12:29 am**

any chance to get fully working dude api ?
we need ability to get list from dude of some type devices, for example only switch, radio, etc with its name, ip, note.
for now we ony can get list with device name using cli

Posted: **Thu Jun 07, 2018 11:49 am**

Seems like RC23 needs a user to have the winbox permission to allow API logins, rather than the API permission. RC21 worked as previous version (needing API perm only). Is this an intended change?
Log shows "login failure for user apiuser from 172.16.0.xxx via winbox" where api user is in a group with these permissions: ftp, reboot, read, write, policy, test, sniff, sensitive, api

Posted: **Thu Jun 07, 2018 12:05 pm**

Reading https://wiki.mikrotik.com/wiki/Manual:API_Python3

Can you please tell me if the function login is compatible with v 6.42 and v 6.43 ?

It was last edited a year ago. It's not compatible with 6.43 changes.

Posted: **Thu Jun 07, 2018 4:15 pm**

*) dhcpv6-server - added initial dynamic simple queue support;

Hello strods!
We are still strugling to do dual-stack queues via DHCP server.
There is no enough information available on Wiki.
Could you help us?

Thanks!

Posted: **Fri Jun 08, 2018 11:22 am**

I just found another "issue" with the latest version 6.43rc23 the custom default config that I have using the branding tool gets erased.
It resets to mikrotik's defaults.
Even after I downgrade to stable 6.42.3 and reset it again the default configuration of mikrotik comes up... with the previous rc that rc23 (don't remember the number) it wasn't affected.
I hope that it will be fixed before the 6.43 is out!

MikroTik

v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!

Re: v6.43rc [release candidate] is released!