Page 1 of 2

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

Posted: Thu May 24, 2018 3:33 am
by null31
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.

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

Posted: Thu May 24, 2018 4:54 am
by squeeze
Loving the priority on security improvements. Keep it coming!

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

Posted: Thu May 24, 2018 4:57 am
by oraculo
Unfortunately I did not succeed, mikrotik is bricked, it was not possible to use netinstall

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

Posted: Thu May 24, 2018 6:02 am
by yhfung
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

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

Posted: Thu May 24, 2018 6:23 am
by nsdadmin
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.

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

Posted: Thu May 24, 2018 7:53 am
by Xymox
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.

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

Posted: Thu May 24, 2018 8:06 am
by eddieb
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 !

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

Posted: Thu May 24, 2018 8:26 am
by antonsb
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.

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

Posted: Thu May 24, 2018 8:52 am
by Xymox
I can confirm old versions of Winbox work if you are locked out..

I have attached a Winbox from 2010 that works..

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

Posted: Thu May 24, 2018 8:58 am
by Xymox
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.

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

Posted: Thu May 24, 2018 11:04 am
by genesispro
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

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

Posted: Thu May 24, 2018 11:07 am
by normis
Link to Winbox rc is in the above post, where RC is announced. Please all read the posts. It is not that hard.

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

Posted: Thu May 24, 2018 11:15 am
by owsugde
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!

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

Posted: Thu May 24, 2018 11:17 am
by pe1chl
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.

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

Posted: Thu May 24, 2018 11:20 am
by pe1chl
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.

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

Posted: Thu May 24, 2018 11:31 am
by genesispro
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

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

Posted: Thu May 24, 2018 11:32 am
by normis
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.

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

Posted: Thu May 24, 2018 12:40 pm
by genesispro
I have a feeling that the API calls cannot authenticate now!

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

Posted: Thu May 24, 2018 3:22 pm
by jlzoroa
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.

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

Posted: Thu May 24, 2018 5:13 pm
by diegotormes
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.

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

Posted: Thu May 24, 2018 5:37 pm
by Chupaka
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 :)

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

Posted: Thu May 24, 2018 8:03 pm
by WebLuke
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. 8)

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

Posted: Thu May 24, 2018 8:04 pm
by genesispro
Did anyone manage to use api calls with this version? My php api fails to login (similar to the winbox problem)

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

Posted: Thu May 24, 2018 8:14 pm
by msatter
.
.
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. 8)
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.

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

Posted: Thu May 24, 2018 8:23 pm
by Xymox

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.

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

Posted: Thu May 24, 2018 11:26 pm
by andriys
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.

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

Posted: Fri May 25, 2018 1:49 am
by nkourtzis

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.

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

Posted: Fri May 25, 2018 9:13 am
by Bergante
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!

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

Posted: Fri May 25, 2018 1:00 pm
by strods
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

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

Posted: Fri May 25, 2018 1:03 pm
by mrz
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

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

Posted: Fri May 25, 2018 1:56 pm
by pe1chl
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.

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

Posted: Fri May 25, 2018 2:29 pm
by genesispro
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

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

Posted: Fri May 25, 2018 2:30 pm
by strods
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.

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

Posted: Fri May 25, 2018 2:42 pm
by genesispro
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)

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

Posted: Fri May 25, 2018 2:55 pm
by pe1chl
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.

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

Posted: Fri May 25, 2018 2:58 pm
by mrz
You can change release channel, just close the window and open open it again.

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

Posted: Fri May 25, 2018 3:46 pm
by Chupaka
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?

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

Posted: Fri May 25, 2018 3:48 pm
by mrz
For secure connection use api-ssl

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

Posted: Fri May 25, 2018 4:31 pm
by pe1chl
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.

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

Posted: Fri May 25, 2018 5:04 pm
by GLUIMAIGINE
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.

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

Posted: Fri May 25, 2018 5:10 pm
by tigro11
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

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

Posted: Fri May 25, 2018 5:18 pm
by GLUIMAIGINE
New winbox does not work! Wrong password!

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

Posted: Fri May 25, 2018 5:57 pm
by tigro11
New winbox does not work! Wrong password!
download/file.php?id=32109

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

Posted: Fri May 25, 2018 6:07 pm
by GLUIMAIGINE
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".

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

Posted: Fri May 25, 2018 6:23 pm
by Chupaka
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?

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

Posted: Fri May 25, 2018 6:39 pm
by dada
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.

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

Posted: Fri May 25, 2018 6:54 pm
by sebasprimeau
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

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

Posted: Fri May 25, 2018 6:56 pm
by jarda
Sure. Newer winbox.

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

Posted: Fri May 25, 2018 7:57 pm
by GLUIMAIGINE
Anyone have netinstall for 6.43rc17?

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

Posted: Fri May 25, 2018 8:00 pm
by pe1chl
That version has been withdrawn. You would not want to install that! Get the 6.43rc19

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

Posted: Fri May 25, 2018 8:08 pm
by GLUIMAIGINE
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.

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

Posted: Fri May 25, 2018 8:22 pm
by pe1chl
No. When it doesn't work it simply indicates you are doing something wrong in the procedure.

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

Posted: Fri May 25, 2018 9:12 pm
by FezzFest
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?

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

Posted: Fri May 25, 2018 9:22 pm
by bugi
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.

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

Posted: Fri May 25, 2018 11:04 pm
by skillful
Login by Winbox does not work but SSH and Telnet works

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

Posted: Sat May 26, 2018 4:47 am
by mica
Login by Winbox does not work but SSH and Telnet works
Winbox 3.14RC work fine.... What's wrong with me?

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

Posted: Sat May 26, 2018 6:53 am
by verystupidsetup
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.

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

Posted: Sat May 26, 2018 7:23 am
by bugi
SSH and telnet returns wrong user and password.

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

Posted: Sat May 26, 2018 7:27 am
by bugi
Cmon guys! Give as a way to get our MicroTiks under out control. I have tried everting that i could find here.

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

Posted: Sat May 26, 2018 7:32 am
by verystupidsetup
It's been defaulted with no cfg. It has no IP address so no SSH. I can mac telnet and that's it.

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

Posted: Sat May 26, 2018 8:27 am
by mica
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".

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

Posted: Sat May 26, 2018 8:32 am
by bugi

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

Posted: Sat May 26, 2018 9:21 am
by human1982
Working. Latency tho working?

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

Posted: Sat May 26, 2018 9:36 am
by imort
Same here, can't login after upgrading both using WinBox and MAC telnet.
Only can connect using SSH with public key auth configured.

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

Posted: Sat May 26, 2018 5:54 pm
by jarda
Why those who cannot login even installed the rc version?

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

Posted: Sat May 26, 2018 6:11 pm
by bugi
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.

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

Posted: Sun May 27, 2018 10:54 pm
by squall0833
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

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

Posted: Sun May 27, 2018 11:01 pm
by sutrus

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

Posted: Mon May 28, 2018 11:25 am
by Xymox
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.

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

Posted: Mon May 28, 2018 11:30 am
by zyzelis
@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.

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

Posted: Mon May 28, 2018 11:35 am
by strods
Winbox v3.14 has been released:
viewtopic.php?f=21&t=134940

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

Posted: Mon May 28, 2018 9:47 pm
by Xymox
@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 :)

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

Posted: Mon May 28, 2018 9:55 pm
by diablothebest
Works fine with CHR!

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

Posted: Tue May 29, 2018 1:48 pm
by normis
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"

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

Posted: Tue May 29, 2018 1:58 pm
by jarda
What a small step for normis but huge jump for the mikrotik community!

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

Posted: Tue May 29, 2018 2:14 pm
by msatter
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

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

Posted: Tue May 29, 2018 2:18 pm
by normis
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.

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

Posted: Tue May 29, 2018 2:37 pm
by eddieb
That warning is perfectly clear. Unfortunately some people don't read.

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

Posted: Tue May 29, 2018 2:54 pm
by Chupaka
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.

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

Posted: Tue May 29, 2018 5:37 pm
by huntermic
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!

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

Posted: Tue May 29, 2018 5:40 pm
by huntermic
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

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

Posted: Tue May 29, 2018 5:51 pm
by Chupaka
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"...

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

Posted: Tue May 29, 2018 6:14 pm
by eworm
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"... :D 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".

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

Posted: Wed May 30, 2018 4:17 am
by Xymox
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...

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

Posted: Wed May 30, 2018 7:10 am
by jarda
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.

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

Posted: Wed May 30, 2018 7:34 am
by strods
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.

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

Posted: Wed May 30, 2018 10:14 am
by Xymox
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.

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

Posted: Wed May 30, 2018 12:44 pm
by strods
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.

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

Posted: Wed May 30, 2018 1:29 pm
by Chupaka
And again - this is not 6.43rc version related discussion.
Technically, 6.42 topic is locked, so they continue here :)

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

Posted: Wed May 30, 2018 3:26 pm
by strods
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.

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

Posted: Wed May 30, 2018 3:55 pm
by macgaiver
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!!

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

Posted: Wed May 30, 2018 3:59 pm
by Chupaka
I wonder if we can do it manually. And where does dst-mac lookup happen in Packet Flow diagram?

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

Posted: Wed May 30, 2018 10:02 pm
by raffav
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;

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

Posted: Wed May 30, 2018 10:35 pm
by bbs2web
Perhaps it's possible for Mikrotik to consider allowing radius authentication for bandwidth tests, whilst restructuring authentication?

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

Posted: Wed May 30, 2018 11:36 pm
by mlenhart
*) 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?

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

Posted: Wed May 30, 2018 11:46 pm
by kez
*) 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

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

Posted: Thu May 31, 2018 1:13 am
by valera5505
*) winbox - show "System/Health" only on boards that have health monitoring;
So... Where's my health?
Image

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

Posted: Thu May 31, 2018 4:43 am
by Xymox
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.

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

Posted: Thu May 31, 2018 5:06 am
by nz_monkey
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!

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

Posted: Thu May 31, 2018 6:59 am
by chechito
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

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

Posted: Thu May 31, 2018 7:25 am
by Xymox
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

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

Posted: Thu May 31, 2018 8:27 am
by strods
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

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

Posted: Thu May 31, 2018 9:46 am
by strods
Everyone who complained about the Netwatch issue - Please see this topic viewtopic.php?f=2&t=134538

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

Posted: Thu May 31, 2018 10:53 am
by artz
*) 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

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

Posted: Thu May 31, 2018 11:57 am
by Chupaka
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 :)

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

Posted: Thu May 31, 2018 5:21 pm
by kez
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

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

Posted: Thu May 31, 2018 8:06 pm
by juliokato
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.

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

Posted: Fri Jun 01, 2018 2:14 am
by polly
Could anyone give an example of how to connect in the api PHP in the new version of mikrotik v3.43rc21

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

Posted: Fri Jun 01, 2018 7:53 am
by Xymox
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.

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

Posted: Fri Jun 01, 2018 11:14 am
by mrz
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

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

Posted: Fri Jun 01, 2018 11:30 am
by schadom
Will we ever see BGP4 SNMP MIBs on ROS? Please!

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

Posted: Fri Jun 01, 2018 11:31 am
by mrz
Yes, but not in v6. Currently for monitoring you can already use API.

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

Posted: Fri Jun 01, 2018 1:18 pm
by polly
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.

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

Posted: Fri Jun 01, 2018 1:35 pm
by genesispro
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;
}

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

Posted: Fri Jun 01, 2018 1:58 pm
by mrz
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

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

Posted: Fri Jun 01, 2018 3:44 pm
by genesispro
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

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

Posted: Fri Jun 01, 2018 3:47 pm
by mrz
As I mentioned you do not need to know version to log in. Fall back to old login procedure if router responds with =ret=.

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

Posted: Sat Jun 02, 2018 2:45 am
by polly
thank you very much genesispro

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

Posted: Sat Jun 02, 2018 7:23 am
by npero
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

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

Posted: Sat Jun 02, 2018 8:28 am
by nescafe2002
This is really ironic. Introducing unencrypted plain text authentication in 2018.

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

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

Posted: Sat Jun 02, 2018 9:26 am
by LeftyTs
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.

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

Posted: Sat Jun 02, 2018 10:30 am
by pe1chl
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.

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

Posted: Sun Jun 03, 2018 2:22 am
by Xymox
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.

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

Posted: Sun Jun 03, 2018 4:09 pm
by LeftyTs
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.

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

Posted: Sun Jun 03, 2018 5:32 pm
by msatter
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. ;-)

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

Posted: Sun Jun 03, 2018 5:43 pm
by LeftyTs
Depends on how well your car is heavily guarded or not. lol

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

Posted: Mon Jun 04, 2018 8:51 am
by Xymox
We need a netinstall
oops.jpg

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

Posted: Mon Jun 04, 2018 11:59 am
by msatter
My tire won't survive a caltrop, sometimes a IED is needed if you are have a more secure tire.

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

Posted: Mon Jun 04, 2018 2:37 pm
by honzam
It is possible add this comand into winbox?

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

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

Posted: Mon Jun 04, 2018 4:08 pm
by Kliwer
!) 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?

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

Posted: Mon Jun 04, 2018 5:57 pm
by blue
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

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

Posted: Mon Jun 04, 2018 6:02 pm
by nescafe2002
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

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

Posted: Mon Jun 04, 2018 6:06 pm
by blue
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 :(

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

Posted: Tue Jun 05, 2018 8:55 am
by Xymox
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.

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

Posted: Tue Jun 05, 2018 1:20 pm
by LeftyTs
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.

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

Posted: Tue Jun 05, 2018 2:13 pm
by pe1chl
/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).

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

Posted: Tue Jun 05, 2018 3:22 pm
by strods
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.

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

Posted: Tue Jun 05, 2018 5:03 pm
by juliokato
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.

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

Posted: Tue Jun 05, 2018 6:48 pm
by Chupaka
*) 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? :shock:

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

Posted: Tue Jun 05, 2018 8:06 pm
by msatter
I am impressed. Thanks for listening to us all.

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

Posted: Tue Jun 05, 2018 11:54 pm
by th0massin0
*) lte - improved modem event processing;
is it for SXT LTE?

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

Posted: Wed Jun 06, 2018 12:55 am
by Xymox
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..

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

Posted: Wed Jun 06, 2018 9:22 am
by MonkeyDan
Does rc23 fix the w60g issues seen in rc19 and rc21?

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

Posted: Wed Jun 06, 2018 5:28 pm
by oortega
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

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

Posted: Wed Jun 06, 2018 7:31 pm
by zyzelis
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.

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

Posted: Thu Jun 07, 2018 12:29 am
by alexspils
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

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

Posted: Thu Jun 07, 2018 11:49 am
by Tris
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

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

Posted: Thu Jun 07, 2018 12:05 pm
by Chupaka
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.

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

Posted: Thu Jun 07, 2018 4:15 pm
by kez
*) 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!

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

Posted: Fri Jun 08, 2018 11:22 am
by genesispro
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!

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

Posted: Sat Jun 09, 2018 1:08 pm
by z1022
rc23 still have high ping time in hAP ac².

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

Posted: Sun Jun 10, 2018 11:03 am
by Xymox
Ive lost control of LEDs from scripting. I can control them via terminal.

/system leds set leds=user-led type=off 3
/system leds set leds=user-led type=on 3

These work fine from terminal but do not work in a script.

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

Posted: Mon Jun 11, 2018 10:50 am
by netwpl
tested winbox auth. with radius (mschapv2) interworking. works like a charm! :)

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

Posted: Mon Jun 11, 2018 5:00 pm
by k3dt
Plaintext password in API login? WTF WHY? api-ssl is SLOW as hell.. please change your mind.. its a step backward.

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

Posted: Tue Jun 12, 2018 3:49 pm
by strods
Version 6.43rc27 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:

*) dhcpv4-client - fixed DHCP client that was stuck on invalid state;
*) dhcpv4-server - fixed DHCP server that was stuck on invalid state;
*) health - changed "PSU-Voltage" to "PSU-State" for CRS328-4C-20S-4S+;
*) health - fixed incorrect PSU index for CRS328-4C-20S-4S+;
*) ike1 - purge both SAs when timer expires;
*) ipsec - use monotonic timer for SA lifetime check;
*) led - added "dark-mode" functionality for hEX S devices;
*) lte - added additional ID support for SIM7600 modem;
*) lte - added support for Quanta 1k6e modem;
*) lte - improved r11e-LTE and r11e-LTE-US dialling process;
*) lte - improved readings of info command results for the SXT LTE;
*) lte - improved stability of USB LTE interface detection process;
*) ntp - allow to specify link-local address as NTP server;
*) ppp - added support for additional ID for E3531 modem;
*) snmp - added remote CAP count OID for CAPsMAN;
*) snmp - fixed readings for CAPsMAN slave interfaces;
*) usb - fixed power-reset for hAP ac^2 devices;
*) usb - properly detect USB 3.0 flash on RBM33G when jumper is removed;
*) userman - improved unique username generation process when adding batch of users;
*) w60g - added distance measurement (CLI only);
*) w60g - improved link stability;
*) w60g - improved maximum link distance;
*) wireless - improved Nv2 reliability on ARM 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.

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

Posted: Tue Jun 12, 2018 5:21 pm
by Tris
The issue I noted in #298 is still occurring in rc27. Is this the best place to raise possible RC bugs, or should I email support?

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

Posted: Tue Jun 12, 2018 11:13 pm
by strods
We are aware about this problem and will try to resolve it as soon as possible.

This is MikroTik users forum. If you want to discuss configuration, changes, etc. with other users, then use forum. If you are sure that there is a problem, then contact support@mikrotik.com directly.

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

Posted: Wed Jun 13, 2018 10:57 am
by Ulum
Bug in 6.43rc23:
  1. Upgrade from previous version to 6.43rc23 when you have /ip ipsec peer proposal with hash-algorithm=sha512
  2. Open this proposal in Winbox. You will see that in Winbox it have checked md5 and sha1, but in the export it have sha512
  3. Set hash algorithm to sha512 through Winbox, now autosup file starts generating
Is this bug fixed in 6.43rc27?

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

Posted: Wed Jun 13, 2018 11:50 am
by blingblouw
I am still experiencing a problem with the WAP60 on this firmware.

Both client & AP running latest release.

Client connects when ap set to bridge. However when AP set to ap-bridge same client will not connect. No matter which frequency is selected (even the new 64800)

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

Posted: Wed Jun 13, 2018 12:05 pm
by msatter
Bug in 6.43rc23:
  1. Upgrade from previous version to 6.43rc23 when you have /ip ipsec peer proposal with hash-algorithm=sha512
  2. Open this proposal in Winbox. You will see that in Winbox it have checked md5 and sha1, but in the export it have sha512
  3. Set hash algorithm to sha512 through Winbox, now autosup file starts generating
Is this bug fixed in 6.43rc27?
Do you have reported this to Mikrotik and if, what is your support ticket id?

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

Posted: Wed Jun 13, 2018 12:19 pm
by joserudi
*) wireless - improved Nv2 reliability on ARM devices;

There are no improvements in this regard, the nv2 protocol in arm devices remains unstable. It continues to have packet losses. At the moment nstreme is the best option.

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

Posted: Wed Jun 13, 2018 2:47 pm
by Ulum
Do you have reported this to Mikrotik and if, what is your support ticket id?
Reported just now. Ticket id is 2018061322004299

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

Posted: Wed Jun 13, 2018 5:09 pm
by roulyz
I have upgrade my SXT LTE (band 3,7), from ROS 6.42.3 to 6.43RC27.
But after upgrading... I can't get access to my SXT LTE.
Wrong username or password message.
Device is on tower so, difficult to reset device.
What is the problem?

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

Posted: Wed Jun 13, 2018 5:26 pm
by mrz
Please read the changelog.

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

Posted: Wed Jun 13, 2018 5:41 pm
by LeftyTs
I have upgrade my SXT LTE (band 3,7), from ROS 6.42.3 to 6.43RC27.
But after upgrading... I can't get access to my SXT LTE.
Wrong username or password message.
Device is on tower so, difficult to reset device.
What is the problem?
Try to recover with MAC telnet if possible. I had the same issue and I was lucky.

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

Posted: Wed Jun 13, 2018 6:19 pm
by Chupaka
He simply needs new WinBox

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

Posted: Wed Jun 13, 2018 6:44 pm
by LeftyTs
I wonder if there will ever be a *nixbox as well. Would anyone know if there is any mac telnet client for *nix systems that works with ROS?

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

Posted: Wed Jun 13, 2018 6:59 pm
by blingblouw

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

Posted: Wed Jun 13, 2018 9:07 pm
by eworm
But that does not yet work with RouterOS 6.43rc. I opened an issue already.
Is there an detail available about mac telnet protocol?

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

Posted: Wed Jun 13, 2018 10:56 pm
by owsugde
*) w60g - improved link stability;
*) w60g - improved maximum link distance;
Can anyone already quantify this in some way?

I'd like to know, because two NLoS pathways I tried were ever so slightly too far / too faint as of rc21/23. Maybe after some improvements they could actually work.

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

Posted: Thu Jun 14, 2018 3:59 am
by jarda
How could you think that 60g will work without clear line of sight?

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

Posted: Thu Jun 14, 2018 9:32 am
by SergeyMorozov
How could you think that 60g will work without clear line of sight?
I think no.

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

Posted: Thu Jun 14, 2018 9:54 am
by Xymox
Looks like LEDs are working from scripting. Thank you :)

No other issues in my SOHO testing with RC27.

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

Posted: Thu Jun 14, 2018 11:00 am
by kugla007
tested winbox auth. with radius (mschapv2) interworking. works like a charm! :)
Which RADIUS server did you use? Can you post a configuration example?

EDIT: Nevermind, I managed to get it working.

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

Posted: Thu Jun 14, 2018 11:50 am
by roulyz
He simply needs new WinBox
I running lastest version Winbox 3.14.
But problem still

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

Posted: Thu Jun 14, 2018 11:51 am
by roulyz
Please read the changelog.
I have read many many time changelog and nothing explicit about solution or notice about this problem

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

Posted: Thu Jun 14, 2018 10:10 pm
by mlenhart

*) w60g - added distance measurement (CLI only);
*) w60g - improved link stability;
*) w60g - improved maximum link distance;
1) distance mesurement in CLI is here since rc19. Has it been improved somehow? Or what is the difference?
3) what is the new maximum link distance for WAP60 and LHG60?

2) I have a 10 meters long test link between 2 LHG60s (YES, I know it too little for LHG60 and can be clearly solved by wireless wire, but unfortunately I do not have possibility for longer distance for testing at the moment and it will be used for 500m "production" link in the near future) and I have to say that link flaps approximately 5 times per day (no rain, no wind, nothing breaking the clear line of sight, no birds flying, no obvious reason for link flap). Can be caused just by the fact it too close to each other? Or is it something what should be checked by MikroTik (maybe a kind of bug)? The link is under continuous iperf3 bi-directional test, where two servers with 1Gbit/s NICs at the end. Result is somewhere between 800-870 Mbit/s for bi-directional TCP connection and PING is somewhere between 5 to 15 ms.

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

Posted: Fri Jun 15, 2018 8:56 am
by OnixJonix
Big problem...
Updated Mys CCR (to 6,43rc27) an now stucked outside! All is running but cant connect - wrong username or password??? A bit of PANIC!!!

------------------
Sorry! Had two winbox on my pc!! Just need new winbox! Sorry!

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

Posted: Fri Jun 15, 2018 9:17 am
by Kindis
Big problem...
Updated Mys CCR (to 6,43rc27) an now stucked outside! All is running but cant connect - wrong username or password??? A bit of PANIC!!!

------------------
Sorry! Had two winbox on my pc!! Just need new winbox! Sorry!
You need Winbox 3.14

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

Posted: Fri Jun 15, 2018 1:27 pm
by strods
Version 6.43rc29 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 - reduced resource usage of DHCP services;
*) ipsec - improved reliability on IPsec hardware encryption for RB1100Dx4;
*) led - added "dark-mode" functionality for SXTsq 5 ac devices;
*) led - use routers uptime as a starting point when turning off LEDs if option was not enabled on boot;
*) sfp - fixed DDM data with SFP+ modules on CRS328-4C-20S-4S+ (introduced in v6.43rc10);
*) sms - do not require "port" and "interface" parameters when sending SMS if already present in configuration;
*) swos - implemented "/system swos" menu that allows to upgrade, reset, save or load configuration and change address for dual-boot CRS devices (CLI only);
*) w60g - improved maximum link distance;
*) w60g - improved RAM memoy allocation processes;
*) wireless - improved Nv2 reliability on ARM 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.

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

Posted: Fri Jun 15, 2018 3:06 pm
by antonsb

1) distance mesurement in CLI is here since rc19. Has it been improved somehow? Or what is the difference?
3) what is the new maximum link distance for WAP60 and LHG60?

2) I have a 10 meters long test link between 2 LHG60s (YES, I know it too little for LHG60 and can be clearly solved by wireless wire, but unfortunately I do not have possibility for longer distance for testing at the moment and it will be used for 500m "production" link in the near future) and I have to say that link flaps approximately 5 times per day (no rain, no wind, nothing breaking the clear line of sight, no birds flying, no obvious reason for link flap). Can be caused just by the fact it too close to each other? Or is it something what should be checked by MikroTik (maybe a kind of bug)? The link is under continuous iperf3 bi-directional test, where two servers with 1Gbit/s NICs at the end. Result is somewhere between 800-870 Mbit/s for bi-directional TCP connection and PING is somewhere between 5 to 15 ms.
1) Yes, there are some improvements - mostly stability
3) We are still working on distance improvements - currently no exact distance date available

2) Too much power, try to remove reflector and turn them in different directions.
There are some improvements in rc 29 as well that may fix this

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

Posted: Fri Jun 15, 2018 4:51 pm
by roulyz
Big problem...
Updated Mys CCR (to 6,43rc27) an now stucked outside! All is running but cant connect - wrong username or password??? A bit of PANIC!!!

------------------
Sorry! Had two winbox on my pc!! Just need new winbox! Sorry!
MIKROTIK please how can we solve this problem?

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

Posted: Fri Jun 15, 2018 4:53 pm
by Chupaka
As you can read from your quote, the problem was solved by updating WinBox to the latest version.

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

Posted: Sun Jun 17, 2018 7:24 pm
by Haward
Can somebody please recommend stable SW for wireless wire wAP60G ? I have tried many but all are unstable ? (jam after couple of days = hard reset is necessary). It is probably linked with hot weather ... Thank you.

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

Posted: Mon Jun 18, 2018 9:59 am
by antonsb
Can somebody please recommend stable SW for wireless wire wAP60G ? I have tried many but all are unstable ? (jam after couple of days = hard reset is necessary). It is probably linked with hot weather ... Thank you.
Please provide more details to support@mikrotik.com

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

Posted: Mon Jun 18, 2018 10:03 am
by antonsb
I am still experiencing a problem with the WAP60 on this firmware.

Both client & AP running latest release.

Client connects when ap set to bridge. However when AP set to ap-bridge same client will not connect. No matter which frequency is selected (even the new 64800)
Do You have level4 license on Bridge device?

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

Posted: Mon Jun 18, 2018 10:18 am
by blingblouw
Yes I do

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

Posted: Mon Jun 18, 2018 10:43 am
by Jaxworld
We updated our CCR1016-12G and our network seems to be inverted! We can't tell if it's running default configurations somehow, but our whole network is running in a degraded state.

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

Posted: Mon Jun 18, 2018 10:49 am
by Chupaka
Congratulations. Now you know that RC versions must not be installed in production environments.

Rollback to the 'current' or 'bugfix' version and be happy.

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

Posted: Mon Jun 18, 2018 10:55 am
by Jaxworld
Sorry, I misread the title. We're actually running 6.42.3 with this issue after discovering a vulnerability in 6.35.2. My apologies.

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

Posted: Mon Jun 18, 2018 11:49 am
by Chupaka
Then post details of your problem in appropriate topic.

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

Posted: Tue Jun 19, 2018 12:45 pm
by strods
Version 6.43rc32 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;
----------------------


Other changes in this release:

!) winbox - minimal required version is v3.15;
*) api - properly classify API sessions in log;
*) bridge - improved performance when bridge VLAN filtering is used without hardware offloading;
*) chr - enabled promiscious mode (requires to be enabled on host as well) when running CHR on Hyper-V;
*) crs317 - fixed Ethernet inteface stuck on 100 Mbps speed;
*) crs328 - fixed transmit on sfp-sfpplus1 and sfp-sfpplus2 interfaces;
*) crs3xx - do not report SFP interface as running when interface on opposite side is disabled;
*) dude - fixed client auto upgrade (broken since 6.43rc17);
*) export - do not show w60g password on "hide-sensitive" type of export;
*) log - fixed false log warnings about system status after power on for CRS328-4C-20S-4S+;
*) lte - show UICC in correct format for SXT LTE devices;
*) romon - properly classify RoMON sessions in log and active users list;
*) w60g - improved maximal achievable distance;
*) w60g - properly report center status under "tx-sector-info";

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.

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

Posted: Tue Jun 19, 2018 1:32 pm
by mlenhart
*) w60g - improved maximal achievable distance;
what is the new maximum distance for wAP60g and LHG60G?

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

Posted: Tue Jun 19, 2018 1:40 pm
by owsugde
How could you think that 60g will work without clear line of sight?
That's just wireless PHY basics. The smaller the wavelength gets, the penetrative wave properties decrease rapidly but the reflective ones increase. Think low/medium frequency ≈ broadcast radio (goes literally straight through the ground), very high frequency ≈ visible light (is reflected almost 100% on mirrors or white objects). This is basically the point for having beamforming, too.

You can try it out yourselves. In the office or at home, put two W60s somewhere in the back of different rooms (with the doors open) and even point them in opposite directions. A connection will be established nonetheless in many cases. In the CLI, you will be able to see a connection length considerably longer than the "beeline" distance between the two devices. What you are witnessing is NLoS propagation.

All that said, I have tried out the benefits from rc27 myself. It got me up to 2dB better RSSI for NLoS setups. Not quite enough to get the "big" route going, but it's something. Eager to try out the new rc32. It would just be so neat if I could go NLoS, without having to put a small relay with two additional W60s in the middle.

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

Posted: Tue Jun 19, 2018 2:19 pm
by genesispro
I upgraded to 6.43rc32 and even using winbox 3.15 login fails!

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

Posted: Tue Jun 19, 2018 2:24 pm
by zyzelis
I upgraded to 6.43rc32 and even using winbox 3.15 login fails!
look for problem on your network, for me works fine.

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

Posted: Tue Jun 19, 2018 2:33 pm
by genesispro
I am directly attached to it and still it doesn't work
I upgraded to 6.43rc32 and even using winbox 3.15 login fails!
look problem on your network, for me works fine.

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

Posted: Tue Jun 19, 2018 3:13 pm
by genesispro
I reset it and now it works...
weird because the password is saved as a favorite in winbox so I wasn't typing anything wrong earlier... and right before the update I used the same favorite to login to it and update it!

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

Posted: Tue Jun 19, 2018 3:29 pm
by zyzelis
I reset it and now it works...
weird because the password is saved as a favorite in winbox so I wasn't typing anything wrong earlier... and right before the update I used the same favorite to login to it and update it!
i have observed this weird issue with password in earlier rc. i just changed password before upgrade and not logged in after upgrade with new one, just with old. :)

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

Posted: Tue Jun 19, 2018 3:32 pm
by zyzelis
Version 6.43rc32 has been released.

*) dude - fixed client auto upgrade (broken since 6.43rc17);
still need to upgrade dude client manually. Client crashes after each upgrade via client ui

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

Posted: Tue Jun 19, 2018 4:36 pm
by PaulsMT
Version 6.43rc32 has been released.

*) dude - fixed client auto upgrade (broken since 6.43rc17);
still need to upgrade dude client manually. Client crashes after each upgrade via client ui
Thank you for a report, but can you please confirm that your Dude client (executed with the administrator rights) auto upgrade was working before 6.43rc17, and does not work in 6.43rc32 ?

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

Posted: Tue Jun 19, 2018 7:52 pm
by jarda
Just sidenote. I don't run dude client with admin rights, only the installer, if necessary.

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

Posted: Tue Jun 19, 2018 8:54 pm
by pe1chl
IP->Cloud has disappeared from menu in WebFig and WinBox.

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

Posted: Wed Jun 20, 2018 12:56 am
by jarda
Maybe good way finally.

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

Posted: Wed Jun 20, 2018 2:46 am
by juliokato
:lol:

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

Posted: Wed Jun 20, 2018 7:36 am
by strods
pe1chl - Can you provide supout file from RouterBOARD that does not show IP/Cloud menu on GUI?

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

Posted: Wed Jun 20, 2018 8:38 am
by zyzelis
Version 6.43rc32 has been released.

*) dude - fixed client auto upgrade (broken since 6.43rc17);
still need to upgrade dude client manually. Client crashes after each upgrade via client ui
Thank you for a report, but can you please confirm that your Dude client (executed with the administrator rights) auto upgrade was working before 6.43rc17, and does not work in 6.43rc32 ?
So thats the trick :) Yes, with "launch as administrator" dude client updates as expected. But is this "feature" documented somewhere? Because if i load exe "as administrator" i need to enter credentials like first time.
Another hint - winbox does not require to start "as administrator" when upgrading it.

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

Posted: Wed Jun 20, 2018 12:12 pm
by pe1chl
pe1chl - Can you provide supout file from RouterBOARD that does not show IP/Cloud menu on GUI?
It is a CHR. Apparently it does not have IP Cloud, but I noticed that only because I wanted to have a look at it after reading change notes.

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

Posted: Wed Jun 20, 2018 12:55 pm
by pe1chl
Please fix "/system check-installation" so that it does not only validate the expected installation, but also detects and optionally removes files that should not be there.

E.g. after updating CCR from 6.42.1 a lot of diskspace is lost and "/system check-installation" should identify the file(s) and delete them.

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

Posted: Sat Jun 23, 2018 2:45 am
by oortega
@antonsb I upgrade from v6.43RC21 to 6.43.RC32 and login by API works with old method login.
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

6.43.RC32 will work with the new and previous login?

Thanks

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

Posted: Mon Jun 25, 2018 1:43 pm
by strods
Version 6.43rc34 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 - minimal required version is v3.15;
----------------------


Other changes in this release:

!) cloud - added IPv6 support;
*) console - do not show spare parameters on ping command;
*) crs317 - properly report link state when one link interface is disabled;
*) crs326/crs328 - fixed broken "new-dst-port" ACL rules (introduced in 6.43rc10);
*) crs3xx - fixed flow control;
*) crs3xx - fixed LACP member failover;
*) dhcpv4-client - fixed double ACK packet handling;
*) ethernet - do not show "combo-state" field if interface is not SFP or copper;
*) led - fixed LED default configuration for LtAP mini;
*) lte - added eNB ID to info command;
*) ssh - allow to use "diffie-hellman-group1-sha1" on TILE and x86 devices with "strong-crypto" disabled;
*) supout - added "w60g" section to supout file;
*) watchdog - added "ping-timeout" setting (CLI only);
*) winbox - show "sector-writes" on ARM routers that has such counters;
*) winbox - show "System/Health" only on boards that have health monitoring;

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.

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

Posted: Tue Jun 26, 2018 9:12 am
by server8
Strods any change to se the NV2 issue fixed with arm devices?

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

Posted: Tue Jun 26, 2018 2:40 pm
by strods
What kind of issue are you referring to? Have you contacted support directly to see if problem is not caused by configuration or something that can be adjusted in order to resolve the issue?

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

Posted: Tue Jun 26, 2018 2:50 pm
by server8
I have sent an email to support without answer 19.06.2018 10:48

Here you can find some info viewtopic.php?f=7&t=136002 from me and other user

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

Posted: Tue Jun 26, 2018 9:01 pm
by honzam
What kind of issue are you referring to? Have you contacted support directly to see if problem is not caused by configuration or something that can be adjusted in order to resolve the issue?
There is other topic with problems ARM and NV2 - viewtopic.php?f=7&t=128916&p=670546#p669811
Yes, we have opened ticket with this problem - #2018042522004921
Last answer from support 13.6.2018. No solution yet :-(

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

Posted: Wed Jun 27, 2018 12:42 am
by jriera
*) tile - fixed Ethernet interfaces becoming unresponsive;

I have a very strange problem with a CCR1072. Suddenly there are IP addresses that stop responding, some work and others do not... within the same broadcast (L2) -no routing apply-. There is no problem of firewall or similar, by ARP the MAC is seen, but communication is simply lost... until a reboot is made and everything works again. It has happened to me twice in the last week. With the 6.42.1. Does this changelog correct this problem or similar?

The problem happens in an 802.3ad bonding interface with vlans on it. At the other end there is a CRS317-1G-16S switch. Even if I restart the switch, it does not recover the communication... I must restart the CCR1072.

We have the same problem, with the eactly same scenario. A CCR1072 with CRS317 and bonding 802.3ad. It has happened to us many times, communication is lost in L2. One way to recover it without restarting the CCR1072 is by simply deactivating the bonding and moving the VLANs to one of the two interfaces... then the ICMP will work again.

So my big question is: Is it the problem in CRS317 or in CCR1072, or maybe the mix of both? I think it has some relationship with bonding...

I hope that with 6.43 this is solved, it is causing us many problems!

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

Posted: Wed Jun 27, 2018 7:28 am
by nz_monkey
So my big question is: Is it the problem in CRS317 or in CCR1072, or maybe the mix of both? I think it has some relationship with bonding...
We have about 30 x CCR's installed in exactly this fashion, Bonding interface with LACP to a switch (Extreme x620/x670 and Juniper EX4550) and have not experienced this problem, we have been running this configuration successfully for over 5 years now from 6.0rc5 to 6.40.8

So either the problem is in RouterOS newer than 6.40.8 or it is something specific to the CRS317

I hope this helps you.

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

Posted: Wed Jun 27, 2018 8:57 pm
by docmarius
Still no joy for RG11e-LTE with RB912UAG :-(

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

Posted: Fri Jun 29, 2018 8:45 pm
by pcjc
Do you guys have an ETA for an updated Android TikApp (or beta version), to match the 6.43rc series authentication / login changes?

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

Posted: Fri Jun 29, 2018 8:50 pm
by pe1chl
Thank you very much for the reports about issues with space, next RouterOS version will fix the issue.
Meanwhile this package can be used to clear space on your router,
This fix has a problem, it ruins the installation. When you have only one partition, it means netinstall.

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

Posted: Fri Jun 29, 2018 10:19 pm
by msatter
Do you guys have an ETA for an updated Android TikApp (or beta version), to match the 6.43rc series authentication / login changes?
The current Beta version does match the 6.43rc changes for my device.

v0.0.68 • Fixed login issues on some devices

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

Posted: Sat Jun 30, 2018 1:25 pm
by strods
We are very sorry for any inconvenience caused. Fix package for missing storage space has been temporary removed and will soon be updated to patched version.

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

Posted: Mon Jul 02, 2018 1:58 pm
by sergejs
We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07/02/2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot

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

Posted: Tue Jul 03, 2018 2:35 am
by Xymox
Can the next RC include the fix for the space issue ?

I want to be able to clean the router with the above patch then I want to install a version that does not have the issue that created the lack of space.

:)

Thansk again for the fix and for the clean up patch.

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

Posted: Tue Jul 03, 2018 11:46 am
by strods
Version 6.43rc40 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 - added IPv6 support;
!) 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 - minimal required version is v3.15;
----------------------


Other changes in this release:

!) cloud - added support for licensed CHR instances (including trial);
*) bridge - properly handle packets when bridge port changes states
*) crs317 - properly report link state when one side has disabled interface;
*) ethernet - properly handle Ethernet interface default configuration;
*) ike2 - use "/32" netmask by default on initiator if not provided by responder;
*) package - do not allow to install out of bundle package if it already exists within bundle;
*) package - free up used storage space consumed by old RouterOS upgrades;
*) package - renamed "current-version" to "installed-version" under "/system package install";
*) sms - converted "keep-max-sms" feature to "auto-erase";
*) snmp - added CAPsMAN "remote-cap" table;
*) supout - added "ip-cloud" section to supout file;
*) usb - fixed modem initialisation on LtAP mini;
*) userman - fixed compatibility with PayPal TLS 1.2;
*) w60g - do not reset interface after adding comment;
*) watchdog - added "ping-timeout" setting;
*) winbox - show "sector-writes" on devices that have such counters;
*) winbox - show "Switch" menu on hAP ac^2 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.

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

Posted: Tue Jul 03, 2018 12:51 pm
by raffav
Wow
Nice update..
That why I like mk always improving...


Sent from my XT1580 using Tapatalk


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

Posted: Tue Jul 03, 2018 4:31 pm
by joserudi
*) userman - fixed compatibility with PayPal TLS 1.2;

Paypal works perfectly now. Many thanks.

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

Posted: Tue Jul 03, 2018 8:01 pm
by mstead
WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.

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

Posted: Tue Jul 03, 2018 9:04 pm
by SergeyMorozov
WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
I'm successfully upgraded a hAp ac2.

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

Posted: Tue Jul 03, 2018 9:10 pm
by mstead
WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
I'm successfully upgraded a hAp ac2.
hAp ac2 is not a RBSXTsq5HPnD - also this may depend on what ROS version is being upgraded from. I am happy that you have not had a problem. However I can recreate this bricking process by taking another unit off the shelf :-(

Netinstall does recover the unit and even allowed v6.43rc40 to be loaded - so this is a fault of the upgrade process.

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

Posted: Tue Jul 03, 2018 10:03 pm
by SergeyMorozov
WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
I'm successfully upgraded a hAp ac2.
hAp ac2 is not a RBSXTsq5HPnD - also this may depend on what ROS version is being upgraded from. I am happy that you have not had a problem. However I can recreate this bricking process by taking another unit off the shelf :-(

Netinstall does recover the unit and even allowed v6.43rc40 to be loaded - so this is a fault of the upgrade process.
This also may depend on the configuration of the device.

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

Posted: Wed Jul 04, 2018 12:22 am
by mstead
This also may depend on the configuration of the device.
That was a valid point - however I just tested another fresh unit from the same batch which was fully reset with no defaults and I can confirm it is also bricked.

So once again - BEWARE!!!! v6.43rc40 can brick your device - PLEASE CHECK before doing any remote testing.

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

Posted: Wed Jul 04, 2018 9:40 am
by sindy
It has been stated multiple times here that most of the upgrade process is performed by the old version from which you upgrade. So if you in all cases upgraded from 6.40.4., the issue may also be that one, not the 6.43rc40.

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

Posted: Wed Jul 04, 2018 2:16 pm
by mstead
It has been stated multiple times here that most of the upgrade process is performed by the old version from which you upgrade. So if you in all cases upgraded from 6.40.4., the issue may also be that one, not the 6.43rc40.
Yeah well that doesn't change the value of the warning that I am giving - especially as the units in question came factory shipped with 6.40.4. Also saying that you cannot upgrade from an older version because of problems in the older version is kinda crazy :-)

So

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

Posted: Wed Jul 04, 2018 2:37 pm
by pe1chl
Try to upgrade the 6.40.4 first to the current version (6.42.5) and then upgrade to 6.43rc from there.

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

Posted: Wed Jul 04, 2018 2:45 pm
by sindy
saying that you cannot upgrade from an older version because of problems in the older version is kinda crazy :-)
Well, saying it is not crazy, the fact that it happens for some versions is a different question ;-) But this warning has been published by Mikrotik staff in earlier topics here, the only thing I'm far from sure is whether 6.40.4 is affected by that issue or not.

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

Posted: Wed Jul 04, 2018 4:04 pm
by mstead
Try to upgrade the 6.40.4 first to the current version (6.42.5) and then upgrade to 6.43rc from there.
I did - and that does work :-D

Well, saying it is not crazy, the fact that it happens for some versions is a different question ;-)
That comment made me smile ;-)

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

Posted: Wed Jul 04, 2018 4:21 pm
by Nando_lavras
WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
Same for me, but on a CRS328, upgrade is fine, but when i upgraded the routerboot and rebooted the system not load anymore, i do it a netinstall and recovered the board.

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

Posted: Wed Jul 04, 2018 4:48 pm
by emils
Thank you very much for your report. Looks like the next system reboot after upgrading RouterOS directly from pre-6.41 versions to the latest release-candidate version causes the kernel to disappear on devices with flash memory. We will try to resolve the issue in the next release-candidate version. It is safe to upgrade from 6.41 and later versions.

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

Posted: Thu Jul 05, 2018 10:52 am
by strods
Version 6.43rc42 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 - added IPv6 support;
!) 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 - minimal required version is v3.15;
----------------------


Other changes in this release:

!) cloud - reworked "/ip cloud ddns-enabled" implementation (suggested to disable service and re-enable after installation process);
*) check-installation - improved system integrity checking;
*) chr - fixed interface name order when "virtio-net is not being used on KVM installations;
*) chr - improved balooning process;
*) chr - reduced RAM memory required per interface;
*) defconf - fixed bridge default configuration for SOHO devices with more than 9 Ethernet interfaces;
*) health - improved speed of health measurement readings;
*) interface - improved interface "last-link-down-time" and "last-link-up-time" values;
*) package - free up used storage space consumed by old RouterOS upgrades;
*) routerboard - fixed wrongly reported RAM size on ARM devices;
*) snmp - fixed w60g "phy-rate" readings;
*) w60g - general stability and performance improvements;
*) winbox - added 64,6 GHz frequency to w60g interface frequency settings;

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.

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

Posted: Thu Jul 05, 2018 11:50 am
by Xymox
"*) package - free up used storage space consumed by old RouterOS upgrades;"

Awesome ! thank you.. I will test and report back.

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

Posted: Thu Jul 05, 2018 12:04 pm
by amokkatmt
...
!) cloud - added IPv6 support;
...
How to see it in action?

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

Posted: Thu Jul 05, 2018 1:36 pm
by npero
wAP60G 240m link updated from rc32 to rc42, client not connecting any more in scan see signal but not connecting, back to 6.42.5 it is working again, but seem to me it is not stable as has been in 6.42.1.

Also please check scan for frequency 64800 seems to me it is not scanning that frequency when click scan button.

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

Posted: Thu Jul 05, 2018 1:52 pm
by antonsb
wAP60G 240m link updated from rc32 to rc42, client not connecting any more in scan see signal but not connecting, back to 6.42.5 it is working again, but seem to me it is not stable as has been in 6.42.1.

Also please check scan for frequency 64800 seems to me it is not scanning that frequency when click scan button.
Fixes for connecting issues will be included in next RC version

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

Posted: Thu Jul 05, 2018 2:03 pm
by notToNew
WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
Had the same with my HAP AC2. Had no time to look for a fix, did you need netinstall?

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

Posted: Thu Jul 05, 2018 3:10 pm
by nz_monkey
A little bug, When running 6.43rc42 on a cAP AC running "/system health print" outputs nothing, and the health menu is gone from WinBox.

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

Posted: Thu Jul 05, 2018 6:56 pm
by msatter
A little bug, When running 6.43rc42 on a cAP AC running "/system health print" outputs nothing, and the health menu is gone from WinBox.
In RC34; *) winbox - show "System/Health" only on boards that have health monitoring. I don't know if the cAP AC does support health.

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

Posted: Thu Jul 05, 2018 7:01 pm
by sutrus
Bug DHCP in RC42. It's a pioneer reciver. All other network devices are OK.
17:26:49 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:27:17 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:27:17 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:27:41 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:27:41 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:28:08 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:28:08 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:28:35 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:28:35 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:29:03 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:29:03 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:29:30 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:29:30 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:29:57 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:29:57 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:30:24 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:30:24 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:30:49 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:30:49 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:31:16 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:31:16 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:31:46 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 
17:31:46 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3 
17:32:12 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3 

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

Posted: Thu Jul 05, 2018 7:10 pm
by LeftyTs
I am having a dhcp problem also with VLANs. One of the voip devices gets an IP from a different dhcp-server VLAN every time I reset the switch. If I reset the device after then dhcp assigns proper IP. I will be sending a supout to support about this.

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

Posted: Thu Jul 05, 2018 9:22 pm
by irghost
[admin@MikroTik] /ip cloud> print 
  ddns-enabled: yes
   update-time: no
        status: connecting...
on CHR last build

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

Posted: Thu Jul 05, 2018 9:52 pm
by mlenhart
wAP60G 240m link updated from rc32 to rc42, client not connecting any more in scan see signal but not connecting, back to 6.42.5 it is working again, but seem to me it is not stable as has been in 6.42.1.

Also please check scan for frequency 64800 seems to me it is not scanning that frequency when click scan button.
Fixes for connecting issues will be included in next RC version
I can confirm, LHG60 does not connect for more than few seconds, still disconnecting and reconnecting. Back on 6.42.5 - works again OK.

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

Posted: Thu Jul 05, 2018 11:19 pm
by mistry7
wAP60G 240m link updated from rc32 to rc42, client not connecting any more in scan see signal but not connecting, back to 6.42.5 it is working again, but seem to me it is not stable as has been in 6.42.1.

Also please check scan for frequency 64800 seems to me it is not scanning that frequency when click scan button.
Fixes for connecting issues will be included in next RC version
I can confirm, LHG60 does not connect for more than few seconds, still disconnecting and reconnecting. Back on 6.42.5 - works again OK.
same here

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

Posted: Fri Jul 06, 2018 1:09 am
by CoMMyz
If you remove the w60g interface from getting added to bridge, the link works. otherwise it reconnects constantly.

Please fix ;)

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

Posted: Fri Jul 06, 2018 1:21 am
by LeftyTs
I wonder if the same limitations and/or problems apply to LHGG-60ad. Anyone installed them? We are expecting a pair of those and I was wondering what would be the best stable ROS for it. It will be a production link so stability is a must.

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

Posted: Fri Jul 06, 2018 7:05 am
by strods
amokkatmt - If your router can reach cloud server over IPv6, then Cloud should resolve to IPv6 address instead of IPv4. That happens automatically;
npero, mlenhart, mistry7, CoMMyz - Improvements on this version have had some side affects that will be resolved in upcoming rc releases;
notToNew - Problem was present because upgrade was made directly from pre-6.41 release. With rc42 upgrade from these versions should work just fine regarding this matter;
nz_monkey, msatter - This device does not have anything to show under System/Health menu. As you can see, this product does not have anything listed under "Other" as a monitoring tool (https://mikrotik.com/product/cap_ac), but for example, this one does (https://mikrotik.com/product/RB1100Dx4);
sutrus, LeftyTs - Please contact support@mikrotik.com regarding this matter;
irghost - Can you reach cloud.mikrotik.com from your device? I recommend that you contact support@mikrotik.com;
LeftyTs - Do not ever use an rc version on important devices. Rc versions are released strictly for testing purposes (for your test labs, not for real life scenarios).

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

Posted: Fri Jul 06, 2018 8:08 am
by eworm
amokkatmt - If your router can reach cloud server over IPv6, then Cloud should resolve to IPv6 address instead of IPv4. That happens automatically;
Does it resolve to IPv6 address exclusively then? That would be a real issue for be, because I have devices connected via dual stack, but connect to them from IPv4-only networks.

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

Posted: Fri Jul 06, 2018 10:11 am
by mlenhart
I wonder if the same limitations and/or problems apply to LHGG-60ad. Anyone installed them? We are expecting a pair of those and I was wondering what would be the best stable ROS for it. It will be a production link so stability is a must.
6.42.5 (latest current till now) works OK for me.

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

Posted: Fri Jul 06, 2018 10:12 am
by strods
At the moment RouterOS tries to resolve cloud2.mikrotik.com IPv4 and IPv6 addresses. After that tries to reach IPv4 server, if server is reachable over IPv4, then this address will be used. if IPv4 server is not reachable, then try to use IPv6. At the moment IPv6 cloud is used as a fallback.

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

Posted: Fri Jul 06, 2018 12:39 pm
by Chupaka
So, if RouterOS connects to the Cloud via IPv4 address, it adds 'A' record, and via IPv6 it adds 'AAAA' record? Can we have adding both records, or at least force A record to be added? I have ipip tunnels between routers, and I don't think they will work if address changes from A to AAAA after upgrade/reboot...

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

Posted: Fri Jul 06, 2018 12:43 pm
by nescafe2002
Fallback? That's worrying.. I'd rather have IPv6 as an optional feature.

I'm hosting several services on IPv4 endpoints (NATted to internal servers, DNS entry CNAME'd to mynetname.net).
Some services could be hosted via IPv6, but they'd have different IPv6 address (no IPv6 NAT possible).
Some services cannot be hosted via IPv6.

If cloud update fails somehow, I'd rather have the old IPv4 entry stay the same than to suddenly have an IPv6 address which would break all of the hosted-behind-the-MT services.

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

Posted: Tue Jul 10, 2018 1:00 pm
by nkourtzis
I would better have two separate checkboxes in /ip cloud, one for IPv4 and one for IPv6. Depending on which option is checked, DNS records for the automatically generated FQDN should be created for the IPv4 address, the IPv6 address or BOTH. Even better, have two automatically generated FQDNs, one with a "-ip4" and one with "-ip6" suffixes after the serial number and associate each with the respective address.

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

Posted: Tue Jul 10, 2018 7:48 pm
by mkx
Even better, have two automatically generated FQDNs, one with a "-ip4" and one with "-ip6" suffixes after the serial number and associate each with the respective address.
Why do you think two DNS names (one with A record and one with AAAA record) is better than having one DNS name with both A and AAAA records?

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

Posted: Tue Jul 10, 2018 7:55 pm
by sindy
Because that way you can explicitly choose using which protocol you want to connect to the device by choosing the corresponding domain name :-)

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

Posted: Wed Jul 11, 2018 11:58 am
by nkourtzis
Even better, have two automatically generated FQDNs, one with a "-ip4" and one with "-ip6" suffixes after the serial number and associate each with the respective address.
Why do you think two DNS names (one with A record and one with AAAA record) is better than having one DNS name with both A and AAAA records?
Because if for example you have a network with different restrictions for IPv4 and IPv6, you can explicity choose which protocol to use to manage the devices, instead of the device deciding for you.

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

Posted: Thu Jul 12, 2018 2:08 pm
by strods
Version 6.43rc44 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 - added IPv6 support;
!) cloud - added support for licensed CHR instances (including trial);
!) 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 - minimal required version is v3.15;
----------------------


Other changes in this release:

*) backup - added support for new backup file encryption (AES128-CTR) with signatures (SHA256);
*) crs326/crs328 - fixed untagged packet forwarding through tagged ports when pvid=1;
*) crs3xx - fixed tagged packet forwarding in 802.1ad aware bridges (introduced in 6.43rc13);
*) dhcpv6 - improved reliability on IPv6 DHCP services;
*) lte - added support for alternative SIM7600 PID;
*) sms - improved reliability on SMS reader;
*) w60g - temporary disabled distance measurement feature;

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.

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

Posted: Thu Jul 12, 2018 2:53 pm
by pe1chl
*) dhcpv6 - improved reliability on IPv6 DHCP services;
Please do not post change notes like that!
Is it another security issue? Is it recommended to update and/or are there workarounds for issues?

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

Posted: Thu Jul 12, 2018 2:56 pm
by mrz
If dhcpv6 was not working reliably for you then upgrade.

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

Posted: Thu Jul 12, 2018 3:11 pm
by pe1chl
In previous cases when such change notices were posted it became clear later that in fact there was a security problem that was being covered up.
(e.g. some buffer overrun with potential code execution, like in the webserver and the smb server)
Somewhat later the same fix appeared as a current version and everyone was urged to upgrade.
Later when all hell broke loose, we were referred back to the update we should have done because it was recommended, all "to improve reliability".

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

Posted: Thu Jul 12, 2018 10:55 pm
by strods
Not all of the problems can be summarized in one sentence. Or the cause of the problem can lead up to different consequences. Sometimes end-user even can not see software issue and that can be seen in supout file only by MikroTik staff. For example, DHCPv6 issue could lead to DHCPv6 service crash (can be seen only by MikroTik staff) and IPv6 services could not work or work incorrectly.

As you can see in 6.43rc release - we are improving changelog so important notes would be more noticeable. Also, for example, Winbox vulnerability issue was mentioned in changelog and special topics were made.

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

Posted: Fri Jul 13, 2018 12:57 am
by Cha0s
For example, DHCPv6 issue could lead to DHCPv6 service crash (can be seen only by MikroTik staff) and IPv6 services could not work or work incorrectly.
Could this, by any remote chance, be related to the issue described here?
DHCP is installed/enabled but not used at all on both ipv4/ipv6.

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

Posted: Fri Jul 13, 2018 3:01 am
by msatter
I agree that the release notes have improved much with the extra information. Then we have the ticket system that and it often unclear if a ticket is solved and I have written several time that a bug was not solved for me and then the line in the release notes was for an other bug in the same part of RouterOS.

If we could see if the ticket is resolved or still waiting, it would be great.

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

Posted: Fri Jul 13, 2018 6:42 am
by strods
Cha0s - It is not possible to answer your question without seeing supout file from your router. As you know - if you think that there is a software issue on your router, then contact support@mikrotik.com.

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

Posted: Fri Jul 13, 2018 10:57 am
by pe1chl
As you can see in 6.43rc release - we are improving changelog so important notes would be more noticeable. Also, for example, Winbox vulnerability issue was mentioned in changelog and special topics were made.
Yes, it has certainly improved! good to see that warnings like that are now also visible when doing the one-click-upgrade from the router itself. Lots of people never look here so they do not see the warnings about winbox versions when they are not in the changelog.
There still could be some improvement in the clarity of one-line changelog notices, especially when using words like "reliability" that in the past have been used where "security" should actually have been written.

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

Posted: Fri Jul 13, 2018 6:32 pm
by eworm
*) backup - added support for new backup file encryption (AES128-CTR) with signatures (SHA256);
So encryption=rc4 is the old behaviour, encryption=aes-sha256 is the new one? What is the default if I do not specify the option?

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

Posted: Fri Jul 13, 2018 6:35 pm
by mrz
default now is aes-sha256

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

Posted: Mon Jul 16, 2018 12:00 am
by abcde
Are you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).

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

Posted: Mon Jul 16, 2018 11:32 am
by normis
Are you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).
What type of laptop do you have, do you know the WiFi chip and number of antennas it has? There are no known issues with the mentioned model, it works fine for most people

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

Posted: Mon Jul 16, 2018 8:06 pm
by sutrus
Are you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).
Do you have updated wifi card drivers? Use the Intel® Driver & Support Assistant, or manually locate it.
He had the same problem and the update helped.

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

Posted: Mon Jul 16, 2018 10:10 pm
by abcde
Are you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).
What type of laptop do you have, do you know the WiFi chip and number of antennas it has? There are no known issues with the mentioned model, it works fine for most people
It's Sony Vaio Pro 13 (https://www.trustedreviews.com/reviews/sony-vaio-pro-13).
I suppose that this is the card: https://ark.intel.com/en/products/75440 ... ess-N-7260
I'm using 5 GHz N/AC (2.4 is disabled because I don't need it).
Please find useful parts of uname, lspci, systool and dmesg below.
Let me know if you need anything more.
# uname -a
Linux vp 4.17.5-1-ARCH #1 SMP PREEMPT Sun Jul 8 17:27:31 UTC 2018 x86_64 GNU/Linux

# lspci
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
        Subsystem: Intel Corporation Dual Band Wireless-N 7260
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 44
        Region 0: Memory at f7c00000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [c8] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee08004  Data: 4023
        Capabilities: [40] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <32us
                        ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
                LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
                        ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via WAKE#
                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis-, LTR+, OBFF Disabled
                         AtomicOpsCtl: ReqEn-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
                         EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
                        MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
                HeaderLog: 00000000 00000000 00000000 00000000
        Capabilities: [140 v1] Device Serial Number 5c-51-4f-xx-xx-xx-xx-xx
        Capabilities: [14c v1] Latency Tolerance Reporting
                Max snoop latency: 3145728ns
                Max no snoop latency: 3145728ns
        Capabilities: [154 v1] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi


# systool -vm iwlwifi
Module = "iwlwifi"

  Attributes:
    coresize            = "327680"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "1"
    srcversion          = "A082116DEC439F44B0AAD63"
    taint               = ""
    uevent              = <store method only>

  Parameters:
    11n_disable         = "0"
    amsdu_size          = "0"
    antenna_coupling    = "0"
    bt_coex_active      = "Y"
    d0i3_disable        = "Y"
    d0i3_timeout        = "1000"
    debug               = "0"
    disable_11ac        = "N"
    fw_monitor          = "N"
    fw_restart          = "Y"
    lar_disable         = "N"
    led_mode            = "0"
    nvm_file            = "(null)"
    power_level         = "0"
    power_save          = "N"
    swcrypto            = "0"
    uapsd_disable       = "3"

  Sections:
    .altinstr_replacement= "0xffffffffc0a9da3d"
    .altinstructions    = "0xffffffffc0ab9f10"
    .bss                = "0xffffffffc0abeec0"
    .data.once          = "0xffffffffc0abd8f0"
    .data               = "0xffffffffc0abb300"
    .exit.text          = "0xffffffffc0a9da2c"
    .gnu.linkonce.this_module= "0xffffffffc0abeb80"
    .init.text          = "0xffffffffc0acd000"
    .note.gnu.build-id  = "0xffffffffc0a9e000"
    .orc_unwind         = "0xffffffffc0ab35dd"
    .orc_unwind_ip      = "0xffffffffc0aaf6c5"
    .parainstructions   = "0xffffffffc0aba090"
    .ref.data           = "0xffffffffc0abdd00"
    .rodata             = "0xffffffffc0a9e5c0"
    .rodata.str1.1      = "0xffffffffc0aa9bbb"
    .rodata.str1.8      = "0xffffffffc0aab858"
    .smp_locks          = "0xffffffffc0ab9f2c"
    .strtab             = "0xffffffffc0adab40"
    .symtab             = "0xffffffffc0ace000"
    .text               = "0xffffffffc0a7c000"
    .text.unlikely      = "0xffffffffc0a9da45"
    __bpf_raw_tp_map    = "0xffffffffc0abd900"
    __bug_table         = "0xffffffffc0abd0b0"
    __jump_table        = "0xffffffffc0abb000"
    __kcrctab           = "0xffffffffc0a9e490"
    __kcrctab_gpl       = "0xffffffffc0a9e4a0"
    __ksymtab           = "0xffffffffc0a9e030"
    __ksymtab_gpl       = "0xffffffffc0a9e070"
    __ksymtab_strings   = "0xffffffffc0aaf130"
    __mcount_loc        = "0xffffffffc0ab9488"
    __param             = "0xffffffffc0ab9c68"
    __tracepoints_ptrs  = "0xffffffffc0aba1b0"
    __tracepoints_strings= "0xffffffffc0aba280"
    __tracepoints       = "0xffffffffc0abe540"
    _ftrace_events      = "0xffffffffc0abdc20"

# dmesg | grep -i iwl
[    3.119352] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[    3.124355] iwlwifi 0000:01:00.0: loaded firmware version 17.948900127.0 op_mode iwlmvm
[    3.288512] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless N 7260, REV=0x144
[    3.314884] iwlwifi 0000:01:00.0: base HW address: 5c:51:4f:xx:xx:xx
[    3.516017] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    3.518324] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
Are you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).
Do you have updated wifi card drivers? Use the Intel® Driver & Support Assistant, or manually locate it.
He had the same problem and the update helped.
I don't use Windows, I don't have it installed. I use latest Linux kernel so yes, the driver is in latest version :) I use this latptop with many APs all over the world and it has no issues. As I said before, I get 250 Mbit in my house using router provided by my ISP where Mikrotik is not even close. Both routers are next to each other.

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

Posted: Tue Jul 17, 2018 4:23 am
by metricmoose
Version 6.43rc40 has been released.

*) userman - fixed compatibility with PayPal TLS 1.2;
I hope it's not off topic, but when should we expect this to hit the current branch? I have a production userman router that seems to be having some recent Paypal issues lately.

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

Posted: Thu Jul 19, 2018 8:22 pm
by tigro11
sorry for the question, but is it possible to make sure that when I paste a firewall rule script, the doubles are not loaded?

thank you

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

Posted: Thu Jul 19, 2018 9:36 pm
by sindy
How is that related to 6.43rc in particular? There is a different section on the forum for these questions, called Scripting.

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

Posted: Thu Jul 19, 2018 9:57 pm
by tigro11
sorry, delete message

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

Posted: Fri Jul 20, 2018 11:44 pm
by hknet
model: CRS317-1G-16S+
release: v6.43rc44

we use some ports with non-10G SFPs (ie 1G-SX and 1G-TX modules with fiber and copper).

those modules get auto negotiation 'incomplete', while claiming the link is ok but no working datatransmission can be established.

regards,
hk

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

Posted: Sat Jul 21, 2018 2:50 am
by crondrift
model: hAP ac^2 (arm) - RouterBOARD D52G-5HacD2HnD-TC
release: v6.43rc44

I'm experiencing memory leakage. After 8 days of running, free RAM is down to ~90MB (starting at ~205MB after a fresh reboot). The device is "losing" ~14MB of free memory a day...

I don't have any fancy configuration, logs etc. are written external etc.

Anyone else getting this?

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

Posted: Sat Jul 21, 2018 1:39 pm
by osc86
anyone noticing a memory leak that ends with a kernel panic? this is on a CCR1009-7G-1C-1S+ running v6.43rc44

Image

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

Posted: Sat Jul 21, 2018 6:39 pm
by SergeyMorozov
Anyone else getting this?
This is weekly graph on my hAP ac²
Image

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

Posted: Sun Jul 22, 2018 1:04 pm
by osc86
Yesterday I set up an ipsec connection between 2 devices, one running 6.42.6 the other 6.43rc44.
All IKE related settings were the same on both devices, but I wasn't able to establish a connection, unless I changed the hash algorithm to sha256 on the one running 6.42.6 and sha1 on the other.

When I added a new peer configuration using IKEv2, it killed all other non-IKEv2 connections immediately, which shouldn't happen either.

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

Posted: Mon Jul 23, 2018 9:13 am
by emils
Version 6.43rc45 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 - added IPv6 support;
!) cloud - added support for licensed CHR instances (including trial);
!) 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 - minimal required version is v3.15;
----------------------


Other changes in this release:

*) ethernet - improved stability when changing ethernet interface L2MTU on CRS328-24P-4S+ (introduced in v6.43rc11);
*) ipsec - improved invalid policy handling when a valid policy is uninstalled;
*) lte - added additional ID support for SIM7600 modem;
*) sfp - fixed default advertised link speeds;
*) vrrp - fixed VRRP packet processing on VirtualBox and VMWare hypervisors;
*) winbox - properly display all flags for bridge host entries;
*) winbox - show "System/RouterBOARD/Mode Button" on devices that has such feature;
*) wireless - improved Nv2 reliability on ARM 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.

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

Posted: Mon Jul 23, 2018 11:01 am
by nescafe2002
Mikrotik update server 2a02:610:7501:1000::196 still reports 6.43rc44 1531295119.
GET /routeros/LATEST.6rc HTTP/1.1
Host: upgrade.mikrotik.com

HTTP/1.1 200 OK
Date: Mon, 23 Jul 2018 08:01:34 GMT
Content-Type: application/octet-stream
Content-Length: 20
Last-Modified: Thu, 12 Jul 2018 11:05:13 GMT
Connection: keep-alive
ETag: "5b4735e9-14"
Server: ThirdWorldFileDaemon
Access-Control-Allow-Origin: *
Accept-Ranges: bytes

6.43rc44 1531295119
Edit:
Now redirecting to https://download.mikrotik.com/routeros/LATEST.6rc, same cluster.

[2a02:610:7501:1000::196] => 6.43rc44 1531295119
[2a02:610:7501:4000::226] => 6.43rc45 1531816238
159.148.172.226 => 6.43rc45 1531816238
159.148.147.204 => 6.43rc44 1531295119

Edit2:
Now properly propagated.

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

Posted: Mon Jul 23, 2018 11:55 am
by indjov
So, in this version still i have a problem with Tools/SMS when i try to send sms shows me sms send failed: timeout?

Any news around that problem?

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

Posted: Mon Jul 23, 2018 12:09 pm
by sindy
As a workaround worth trying if this issue complicates your life, it might be possible to send the SMSes using /interface lte at-chat and the AT command used to send SMSes on your modem model.

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

Posted: Mon Jul 23, 2018 12:20 pm
by joserudi
*) wireless - improved Nv2 reliability on ARM devices;

The first point-to-point tests with nv2 on arm are not satisfactory. We will perform more tests

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

Posted: Mon Jul 23, 2018 4:32 pm
by indjov
As a workaround worth trying if this issue complicates your life, it might be possible to send the SMSes using /interface lte at-chat and the AT command used to send SMSes on your modem model.
it`s not that the idea? i use this usb stick only for sms netwatch(internet it`s not include it), but i don`t understand why evyrything work normaly before with this gsm option and now did`t not.

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

Posted: Mon Jul 23, 2018 5:09 pm
by sindy
This is a release candidate. Things do break as you add/improve functionality as nobody makes no mistakes at all. Se s tim smiř (in Czech).

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

Posted: Mon Jul 23, 2018 5:26 pm
by server8
Little bit better but the issue still present
*) wireless - improved Nv2 reliability on ARM devices;

The first point-to-point tests with nv2 on arm are not satisfactory. We will perform more tests

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

Posted: Mon Jul 23, 2018 10:14 pm
by abcde
hAP AC2 still works very poorly with Intel Corporation Dual Band Wireless-N 7260. Transfer rate approximately 10 times slower than with other routers and often drops to 0 kbps.

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

Posted: Mon Jul 23, 2018 10:21 pm
by doneware
Little bit better but the issue still present
can you show some results? i was experiencing performance varying between 250-430Mbps using SXTsq ACs with early 6.43rc builds even under excellent conditions.

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

Posted: Tue Jul 24, 2018 11:38 am
by JimmyNyholm
NOOOOO!!!! -"radius - use MS-CHAPv2 for "login" service authentication;"

I hope there is a setting for this. chap, chapv2 with or without ms flavour is doing nothing good to the fact that static passwords are weak and should not be used.

We use one time passwords witch will not work in replay mode due to the fact of being ONE TIME. this makes all challenge based algorithm fail there simply is nothing to do challange on.

put PAP back now or atleast make it a setting so admins may choose the best setting for their env and needs. Make this setting universal så that we may use onetime radius password for winbox as well.

I have requested this many times.... This should be a setting is it or is it not? (Have not yet tested the RC in a router but will later this week.)

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

Posted: Tue Jul 24, 2018 3:36 pm
by JimmyNyholm
Ok so now I test the RC45 Build. My setup scripts fail can't rename user admin anymore? WHY?