Page 1 of 3

v6.42.5 [current]

Posted: Wed Jun 27, 2018 12:04 pm
by strods
RouterOS version 6.42.5 has been released in public "current" channel!

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

What's new in 6.42.5 (2018-Jun-26 12:12):

*) api - properly classify API sessions in log;
*) chr - enabled promiscuous mode (requires to be enabled on host as well) when running CHR on Hyper-V;
*) kidcontrol - added dynamic accept firewall rules to allow bandwidth limit when FastTrack is enabled;
*) led - fixed LED default configuration for LtAP mini;
*) snmp - added "rssi" and "tx-sector-info" value support for w60g type interfaces;
*) snmp - added station "distance", "phy-rate", "rssi" value support for w60g type interfaces;
*) ssh - allow to use "diffie-hellman-group1-sha1" on TILE and x86 devices with "strong-crypto" disabled;
*) w60g - added 4th 802.11ad channel (CLI only);
*) w60g - added distance measurement;
*) w60g - do not reset interface after adding comment;
*) w60g - general stability and performance improvements;
*) w60g - improved maximum achievable distance;
*) w60g - properly report center status under "tx-sector-info";
*) winbox - show "sector-writes" on ARM devices that have such counters;
*) winbox - show "System/Health" only on devices that have health monitoring;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

Please keep this forum topic strictly related to this concrete RouterOS release.

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.42.5 [current]

Posted: Wed Jun 27, 2018 2:04 pm
by pe1chl
Again no fix for the diskspace loss when upgrading from 6.42.1 on CCR? (and maybe others)
Why are these releases rushed out when known showstopping bugs exist?

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 2:27 pm
by honzam
Again no fix for ARM with NV2 :-(

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 2:47 pm
by eddieb
Updated from 6.42.3 -> 6.42.5 without problems.
RB2011 (gateway with 2 ipsec/l2tp tunnels )
RB1100/CRS125/RB750
RB962(9pc)/RB951 accesspoints
CHR with dude
all went smooth, keep up the great work !

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 3:48 pm
by server8
+1
Again no fix for ARM with NV2 :-(

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 4:37 pm
by danielduffin
is anyone else getting this error with userman and who do i resolve it
PayPal - ssl connection error: handshake failed: error 14077410 (6)

Thank you

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 5:03 pm
by Cha0s
Again no fix for the diskspace loss when upgrading from 6.42.1 on CCR? (and maybe others)
Why are these releases rushed out when known showstopping bugs exist?
I can confirm the problem.

pe1chl, didn't you get the memo?
Kid control fixes are WAY more important than (eventually) "bricking" our routers due to no storage available.

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 5:25 pm
by Cha0s
After rebooting, all EoIP tunnels that used dns hostname for remote address were replaced with IPs.
I have to manually edit all EoIP tunnels and set the hostnames again.

That happened on a couple of RB2011 and a couple of hAP AC^2.
On various x86 installations the issue didn't occur.

This problem didn't start with this release. I definitely had the same issue with 6.42.3 when I was setting up 2 brand new hAP AC^2.
I didn't make much of it at the time, I thought I just made an error during config. But after today's update I can see that was not the case.

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 5:31 pm
by Cha0s
Again no fix for the diskspace loss when upgrading from 6.42.1 on CCR? (and maybe others)
Why are these releases rushed out when known showstopping bugs exist?
I can confirm the problem.

pe1chl, didn't you get the memo?
Kid control fixes are WAY more important than (eventually) "bricking" our routers due to no storage available.
Regarding this, I can see the problem with 'lost' disk space is pretty much random (at least at first glance).
Other devices (even the same model or x86) have increased free space after today's upgrade and others have decreased free space.

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 7:35 pm
by rememberme
What is the OID for RSSI on w60g?

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 9:43 pm
by pe1chl
Regarding this, I can see the problem with 'lost' disk space is pretty much random (at least at first glance).
Other devices (even the same model or x86) have increased free space after today's upgrade and others have decreased free space.
Does it depend on the version sequence?
I am considering rescue of my CCRs by first going back to one partition, then upgrade 6.42.1 to 6.42.2 and then .3 .4 .5 (maybe skipping some when it is no longer required)
to see if sequential updates fix the problem as one user reported. Then after that I can go back to two partitions.

However, going this way means I cannot go back to 6.42.1 anymore when it fails, and I would have to live with using a single partition from then on.
I upgraded from 6.42.1 to 6.42.3 and then the remaining space was not enough to do another full upgrade. A "fix package" would be possible but MikroTik doesn't release it.
So I went back to 6.42.1 by switching active partition, and now I am stuck until something is done. And the situation is not particularly bright as it appears that
MikroTik's standard reply is "do a netinstall". Which for various reasons is not really practical.

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 10:13 pm
by bda
Regarding this, I can see the problem with 'lost' disk space is pretty much random (at least at first glance).
Other devices (even the same model or x86) have increased free space after today's upgrade and others have decreased free space.
Does it depend on the version sequence?
I am considering rescue of my CCRs by first going back to one partition, then upgrade 6.42.1 to 6.42.2 and then .3 .4 .5 (maybe skipping some when it is no longer required)
to see if sequential updates fix the problem as one user reported. Then after that I can go back to two partitions.

However, going this way means I cannot go back to 6.42.1 anymore when it fails, and I would have to live with using a single partition from then on.
I upgraded from 6.42.1 to 6.42.3 and then the remaining space was not enough to do another full upgrade. A "fix package" would be possible but MikroTik doesn't release it.
So I went back to 6.42.1 by switching active partition, and now I am stuck until something is done. And the situation is not particularly bright as it appears that
MikroTik's standard reply is "do a netinstall". Which for various reasons is not really practical.
Hi,

Confirm lost disk space problem too. On all devices. No change from older ROS....
Too bad....

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 10:28 pm
by Qper
I have now installed on hb hap ac (rb962uigs-5hact2hnt) and the device has stopped working. It keeps restarting what to do?

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 10:36 pm
by pe1chl
Confirm lost disk space problem too. On all devices. No change from older ROS....
Too bad....
Well, I updated several RB951G-2HnD and a single RB750Gr3 and a RB2011 and they do not show this problem.
For me it happens only on CCR and I have seen reports where it happens on CHR.
All of these (except the RB750Gr3 of course) were configured with 2 partitions of 64MB each, usually more than enough.

I also want to re-iterate that MikroTik should provide a RAMdisk on models with >16MB flash as well.
When the CCR had a RAMdisk, it would have more than enough free space to do the upgrade even when the flash is nearly
full (same way as the RB750Gr3 does it by storing the update in RAMdisk).
And it would also be useful for file storage that does not wear out the flash (e.g. files retrieved using /tool fetch to load lists).

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 10:47 pm
by ofer
3xHAP AC units upgraded from 6.42.4 -> 6.42.5 without issues

Thanks!

Re: v6.42.5 [current]

Posted: Wed Jun 27, 2018 11:17 pm
by Nickel
Updated from 6.42.3 -> 6.42.5 without problems.
RB2011 (gateway with 2 ipsec/l2tp tunnels )
RB1100/CRS125/RB750
RB962(9pc)/RB951 accesspoints
CHR with dude
all went smooth, keep up the great work !
Hi! Didn't you had any issues like "Some packages unavailable" and the package's name "wireless@" for your RB951G?

I had to go manually and if I force the upgrade the wireless package is not installed.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 1:14 am
by blackwp
is anyone else getting this error with userman and who do i resolve it
PayPal - ssl connection error: handshake failed: error 14077410 (6)

Thank you
Yes we can confirm this error also. No Paypal payments being accepted.
We tried adding an ssl cert to the RB but that didn't work either.

"Mikrotik....please help!!"

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 2:21 am
by gius64
Upgraded from 6.38.1 to 6.42.5 a CCR1009-8G-1S-1S+ resulted in kernel panic and boot loop with “system package not found” error showing in serial console.
I had to do netinstall and opened a ticket to MikroTik (2018062722005146).

Please if someone have the same device try to upgrade and let MikroTik know if you have issues!

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 5:32 am
by minelli
Please add in the next version.
Accounting IPv6 and ASN in traffic flow.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 7:38 am
by strods
pe1chl, honzam, server, Cha0s - Current version that has a third number in its name is a version that contains only fixes backported from rc version. As long as there is no fix in rc, there will be no fix in current version that is a rebuild (6.42 vs. 6.42.5 means that version has been rebuided 5 times by adding fixes from 6.43rc)
danielduffin, blackwp - Please contact support@mikrotik.com and send supout file. Are you sure that downgrade to 6.42.4 fixes the problem? Ther are no UM related changes in this version
Cha0s - Is it possible that you added EoIP tunnels from old Winbox version?
rememberme - You can run "print oid" function on related menu in order to see predeefined OIDs
Qper, gius64 - If version from which you did upgrade your router was older than 6.42, then you should know that upgrade is completely reworked and from now on you should not experience such problem
Nickel - Which package shows as unavailable? Wireless package has @ sign in its name already for a while - since we got rid of -fp, -cm2, -rep pacakges and returned to wireless package name
minelli - Please try to keep this topic related to concrete release. Use support@mikrotik.com for feature suggestions

As for the HDD problem - we are currently trying to find out how to reproduce this problem. If anyone can share such information (step-by-step), then please send in an e-mail to support@mikrotik.com. Is it possible that all of the affected devices had partitions?

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 9:51 am
by vecernik87
RBD52G (hAP ac^2) updated from 6.42.3 to 6.42.5 ->> no significant issue except log saying
script, warning    DefConf gen: Unable to find wireless interface(s)
I am not using DefConf and my wifi is working. Not quite sure why I got this error and what consequences it does have.
Also, it might be important to say, that mine hAP ac^2 is the IPQ4019 version with 233MB RAM. Maybe it couldn't find wireless interfaces due to different chipset?

Strods/Normis: If you think this is worth investigation, I will gladly send supout or do some test (for example try to reset config to default configuration. Until now I always did /system reset-configuration no-defaults=yes) Otherwise I don't want to disturb your support people as it did not cause any harm to me

edit:
*) winbox - show "sector-writes" on ARM devices that have such counters;
does not work (at least not on hAP ac^2). I can see write-sect-since-reboot and write-sect-total and bad-blocks in /system resource print but I cannot see it in winbox - system - resources.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 10:16 am
by pe1chl
pe1chl, honzam, server, Cha0s - Current version that has a third number in its name is a version that contains only fixes backported from rc version. As long as there is no fix in rc, there will be no fix in current version that is a rebuild (6.42 vs. 6.42.5 means that version has been rebuided 5 times by adding fixes from 6.43rc)
It appears that you are unaware that you have introduced a showstopping bug in early 6.42 release versions that potentially prohibits customers to do any further upgrades.
The more of those .x releases you release, the more chance that customers install one of them, and then cannot install any further upgrades without netinstall.
The issue has been reported by a few customers and I think one of them had found what went wrong (because it happened on a CHR so he could look in the image) and
when that is indeed what is wrong (some unneeded large file, probably used during installation, is left after the upgrade) it should be possible for you to fix this in the
6.42 release and for better service even in a small "fix" package that can be installed and run once by customers who already have been affected and cannot rollback anymore.

But the more of those .x releases you release without taking this up, the more impractical it will become.

I can fully understand the policy of RC versions where a mishap like this requires netinstall to fix it. That is why there are RC versions.
But this happened in a "current" version! You should feel it as your responsibility to fix problems like this in such a way that it can be done remotely, as many of your
customers have extensive networks where a trip along the sites to do a netinstall is very difficult.

Maybe you could even develop a solution where a running router with 2 partitions can "install" (like netinstall) a fresh RouterOS in the inactive partition, then the user
can copy the config of the running version into that partition (this function is already present), set the active partition and reboot, so he will have a fresh install without
having to do onsite netinstall.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 11:19 am
by Sob
I tested few things and here it is, missing HDD space, quick and easy:

- VMware Player on Windows, new clean VM without anything special
- start with chr-6.41.4.vmdk (important!)
- initially there's 69.8MB free
- upload routeros-x86-6.42.npk and dude-6.42.npk, reboot
- 6.42 comes up with 69.5MB free
- upload routeros-x86-6.42.1.npk and dude-6.42.1.npk, reboot
- 6.42.1 comes up with 50.1MB free; there's nothing in /files, but almost 20MB is gone

Edit: I checked the difference between vmdk with 6.42 and 6.42.1 and at first there are same files. On second look, 6.42 has /bootimage and /var/pdb/routeros-x86/image as same file (hardlink), but on 6.42.1, only the latter got updated and former was left unchaged from 6.42, so there are now two files, taking double space.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 11:24 am
by Xymox
As for the HDD problem - we are currently trying to find out how to reproduce this problem. If anyone can share such information (step-by-step), then please send in an e-mail to support@mikrotik.com. Is it possible that all of the affected devices had partitions?
It does appear very random and im not sure I can reproduce it every time.

I had this happen on a RB1100AHx2 that did not have room for partitions. So it does occur on devices without partitions.

When it occurs its a large loss of % of space. Cant you just look thru the files and see what is taking up more space ? You had mentioned in a support ticket to me and you had mentioned on the forum you had seen the issue, so, you should be be able to look thru files to see what staking up too much space ?

Ive seen it occur on a downgrade.

I had to fly to 4 sites to netinstall recover these devices and I am now firmware frozen on all my clients since I first discovered this issue. Its cost me a lot of money and time. I can no longer update firmware on client gear as that could lead to unserviceable device because of a lack of discspace so the security of my clients is at risk from a lack of updates.

This is a serious issue that needs to be addressed.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 11:38 am
by Xymox
I just now updated a CCR1036 im using to test new releases and it gained space. It gained 20MB. Going from 42.3 to 42.4 it lost 20MB and going to 42.5 it gained it back.

This does seem really weirdly random.

On the same hardware, same device, sometimes you end up loosing 20MB.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 12:00 pm
by pe1chl
I tested few things and here it is, missing HDD space, quick and easy:

Edit: I checked the difference between vmdk with 6.42 and 6.42.1 and at first there are same files. On second look, 6.42 has /bootimage and /var/pdb/routeros-x86/image as same file (hardlink), but on 6.42.1, only the latter got updated and former was left unchaged from 6.42, so there are now two files, taking double space.
So, the only thing they have to do is release a fix package that executes "ln -f /var/pdb/routeros-x86/image /bootimage" and it is fixed.
Or, of course, a "shell" package that allows the user to do that :)

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 12:26 pm
by maznu
is anyone else getting this error with userman and who do i resolve it
PayPal - ssl connection error: handshake failed: error 14077410 (6)

Thank you
Yes we can confirm this error also. No Paypal payments being accepted.
We tried adding an ssl cert to the RB but that didn't work either.

"Mikrotik....please help!!"
@danielduffin @blackwp: PayPal has turned off old TLS ciphers. They announced it a while ago: https://www.paypal.com/au/webapps/mpp/tls-http-upgrade

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 12:27 pm
by maznu
danielduffin, blackwp - Please contact support@mikrotik.com and send supout file. Are you sure that downgrade to 6.42.4 fixes the problem? Ther are no UM related changes in this version
The problem might be related to PayPal deprecating old versions of TLS on 26th June: https://www.paypal.com/au/webapps/mpp/tls-http-upgrade

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 12:40 pm
by normis
danielduffin, blackwp - Please contact support@mikrotik.com and send supout file. Are you sure that downgrade to 6.42.4 fixes the problem? Ther are no UM related changes in this version
The problem might be related to PayPal deprecating old versions of TLS on 26th June: https://www.paypal.com/au/webapps/mpp/tls-http-upgrade

The next RouterOS release will add TLS 1.2 and fix this issue.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 2:19 pm
by Cha0s
Cha0s - Is it possible that you added EoIP tunnels from old Winbox version?
I created the tunnels via CLI. Upgrading or rebooting the router loses the hostname in the remote address field and leaves an old/previously resolved IP.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 3:09 pm
by bda
pe1chl, honzam, server, Cha0s - Current version that has a third number in its name is a version that contains only fixes backported from rc version. As long as there is no fix in rc, there will be no fix in current version that is a rebuild (6.42 vs. 6.42.5 means that version has been rebuided 5 times by adding fixes from 6.43rc)
It appears that you are unaware that you have introduced a showstopping bug in early 6.42 release versions that potentially prohibits customers to do any further upgrades.
The more of those .x releases you release, the more chance that customers install one of them, and then cannot install any further upgrades without netinstall.
The issue has been reported by a few customers and I think one of them had found what went wrong (because it happened on a CHR so he could look in the image) and
when that is indeed what is wrong (some unneeded large file, probably used during installation, is left after the upgrade) it should be possible for you to fix this in the
6.42 release and for better service even in a small "fix" package that can be installed and run once by customers who already have been affected and cannot rollback anymore.

But the more of those .x releases you release without taking this up, the more impractical it will become.

I can fully understand the policy of RC versions where a mishap like this requires netinstall to fix it. That is why there are RC versions.
But this happened in a "current" version! You should feel it as your responsibility to fix problems like this in such a way that it can be done remotely, as many of your
customers have extensive networks where a trip along the sites to do a netinstall is very difficult.

Maybe you could even develop a solution where a running router with 2 partitions can "install" (like netinstall) a fresh RouterOS in the inactive partition, then the user
can copy the config of the running version into that partition (this function is already present), set the active partition and reboot, so he will have a fresh install without
having to do onsite netinstall.
Great post! Thank you!!!

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 3:32 pm
by rememberme
pe1chl, honzam, server, Cha0s - Current version that has a third number in its name is a version that contains only fixes backported from rc version. As long as there is no fix in rc, there will be no fix in current version that is a rebuild (6.42 vs. 6.42.5 means that version has been rebuided 5 times by adding fixes from 6.43rc)
danielduffin, blackwp - Please contact support@mikrotik.com and send supout file. Are you sure that downgrade to 6.42.4 fixes the problem? Ther are no UM related changes in this version
Cha0s - Is it possible that you added EoIP tunnels from old Winbox version?
rememberme - You can run "print oid" function on related menu in order to see predeefined OIDs
Qper, gius64 - If version from which you did upgrade your router was older than 6.42, then you should know that upgrade is completely reworked and from now on you should not experience such problem
Nickel - Which package shows as unavailable? Wireless package has @ sign in its name already for a while - since we got rid of -fp, -cm2, -rep pacakges and returned to wireless package name
minelli - Please try to keep this topic related to concrete release. Use support@mikrotik.com for feature suggestions

As for the HDD problem - we are currently trying to find out how to reproduce this problem. If anyone can share such information (step-by-step), then please send in an e-mail to support@mikrotik.com. Is it possible that all of the affected devices had partitions?
I wouldn't ask if there was anything in the "print oid":

[admin@1-1P-W60] > /interface w60g print oid
Flags: X - disabled, R - running
0 mode=.1.3.6.1.4.1.14988.1.1.1.8.1.2.1
ssid=".1.3.6.1.4.1.14988.1.1.1.8.1.3.1"
frequency=.1.3.6.1.4.1.14988.1.1.1.8.1.6.1

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 5:09 pm
by thaersaadi
I have an issue with ((MikroTik v6.43rc34 (testing))) with RB 3011 & 2011 and when it does all my username and password are wrong when I try to access it ??
is there any way to resolve the issue without hard reset the RB.

Thanks in advanced

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 5:12 pm
by BartoszP
Do you use Winbox 3.15?

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 5:13 pm
by thaersaadi
Do you use Winbox 3.15?
yes I did my friend

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 5:48 pm
by danielduffin
danielduffin, blackwp - Please contact support@mikrotik.com and send supout file. Are you sure that downgrade to 6.42.4 fixes the problem? Ther are no UM related changes in this version
The problem might be related to PayPal deprecating old versions of TLS on 26th June: https://www.paypal.com/au/webapps/mpp/tls-http-upgrade

The next RouterOS release will add TLS 1.2 and fix this issue.
Do you currently have an ETA for this
Thank you

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 5:57 pm
by Chupaka
I have an issue with ((MikroTik v6.43rc34 (testing)))
This topic is about v6.42.5. Do you have this issue with v6.42.5?
Do you currently have an ETA for this
MikroTik never gives ETA, just wait for the release.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 7:31 pm
by bda
Hello,

CRS112-8P-4S is affected by low disk space problem too. I can't even upgrade from 6.42.4 to 6.42.5.
Netinstall is not possible in my case...

We need some sort of cleaning script or something ...

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 7:44 pm
by Xymox
SOme way to clean these remotely would have saved me $3k so far in travel expenses and all sorts of lost income while I traveled all over doing Netinstalls in a emergency mode.

I reported and warned about this issue months ago. I warned this would cause huge issues for people as it effects every flavor of ROS on all devices ive tested. I warned it would result in units locked in a firmware with no way to fix them except to go onsite and netinstall and for some people this would be close to impossible and cost a lot of money.

As I said then. Mikrotik needs to address immediatly as the #1 priority and not release another "stable" until its resolved or tons more people will be effected and need to go Netinstall or replace the router.

A better solution in some cases is to just preconfigure a new one and eat the expenses and ship one on site and have someone replace it. That can be less expensive then flying out to a site with travel expenses and lost income.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 8:04 pm
by bda
SOme way to clean these remotely would have saved me $3k so far in travel expenses and all sorts of lost income while I traveled all over doing Netinstalls in a emergency mode.

I reported and warned about this issue months ago. I warned this would cause huge issues for people as it effects every flavor of ROS on all devices ive tested. I warned it would result in units locked in a firmware with no way to fix them except to go onsite and netinstall and for some people this would be close to impossible and cost a lot of money.

As I said then. Mikrotik needs to address immediatly as the #1 priority and not release another "stable" until its resolved or tons more people will be effected and need to go Netinstall or replace the router.

A better solution in some cases is to just preconfigure a new one and eat the expenses and ship one on site and have someone replace it. That can be less expensive then flying out to a site with travel expenses and lost income.
All you said - true.... Sad but true...

Still waiting for fix from developers...

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 8:23 pm
by expert
I guess all of the following my devices are not upgradeable in the future due to low disk space :-(
                  version: 6.42.5 (stable)
           free-hdd-space: 4648.0KiB
               board-name: CRS112-8P-4S

                  version: 6.42.5 (stable)
           free-hdd-space: 4700.0KiB
               board-name: CRS106-1C-5S

                  version: 6.42.5 (stable)
           free-hdd-space: 4692.0KiB
               board-name: wAP ac

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 10:37 pm
by Beone
RBD52G (hAP ac^2) updated from 6.42.3 to 6.42.5 ->> no significant issue except log saying
script, warning    DefConf gen: Unable to find wireless interface(s)
I am not using DefConf and my wifi is working. Not quite sure why I got this error and what consequences it does have.
Also, it might be important to say, that mine hAP ac^2 is the IPQ4019 version with 233MB RAM. Maybe it couldn't find wireless interfaces due to different chipset?

We have the same issue, when upgrading devices, some of them loose the wireless interfaces (mostly the 5Ghz radio, sometimes both 2.4ghz and 5Ghz, reset to defaults will do the trick, but in the meantime you have customer downtime which isn't good in a large deployment

Strods/Normis: If you think this is worth investigation, I will gladly send supout or do some test (for example try to reset config to default configuration. Until now I always did /system reset-configuration no-defaults=yes) Otherwise I don't want to disturb your support people as it did not cause any harm to me

edit:
*) winbox - show "sector-writes" on ARM devices that have such counters;
does not work (at least not on hAP ac^2). I can see write-sect-since-reboot and write-sect-total and bad-blocks in /system resource print but I cannot see it in winbox - system - resources.

Re: v6.42.5 [current]

Posted: Thu Jun 28, 2018 10:49 pm
by NetflashTechnical
Still can't turn off flooding options on dynamic bridge members :(
Should be an option to blanket deny or blanket accept for a given bridge, then allow static port settings to override.
FloodingL2TP.PNG

Re: v6.42.5 [current]

Posted: Fri Jun 29, 2018 4:47 am
by vecernik87
RBD52G (hAP ac^2) updated from 6.42.3 to 6.42.5 ->> no significant issue except log saying
script, warning    DefConf gen: Unable to find wireless interface(s)
I am not using DefConf and my wifi is working. Not quite sure why I got this error and what consequences it does have.
Also, it might be important to say, that mine hAP ac^2 is the IPQ4019 version with 233MB RAM. Maybe it couldn't find wireless interfaces due to different chipset?
....
We have the same issue, when upgrading devices, some of them loose the wireless interfaces (mostly the 5Ghz radio, sometimes both 2.4ghz and 5Ghz, reset to defaults will do the trick, but in the meantime you have customer downtime which isn't good in a large deployment
I believe you confused everyone with writing your response directly into my quoted text. :lol:

Anyway, thanks for confirmation that I am not alone and that the warning message actually has real consequences with some specific configurations. I will send supout.rif to mikrotik together with referring my and your post in this topic. (supout sent, Ticket#2018062922002154 , I will publish update once I hear back from them)
This might affect tons of users who are using defconf.

Re: v6.42.5 [current]

Posted: Fri Jun 29, 2018 9:17 am
by Kliwer
What is the OID for RSSI on w60g?
.1.3.6.1.4.1.14988.1.1.1.8.1.12.1
This worked for me.

Re: v6.42.5 [current]

Posted: Fri Jun 29, 2018 2:53 pm
by bda
Hello,

Are anybody have any info on "low hdd space" problem?

Re: v6.42.5 [current]

Posted: Fri Jun 29, 2018 3:40 pm
by Mudz
I wonder why does the newest current version of RouterOS (6.42.5) neglects the filter rules for blocking ADS using layer7, the rule was working fine on the previous version (6.42.3)....Can someone answer me? Thanks

Re: v6.42.5 [current]

Posted: Fri Jun 29, 2018 3:43 pm
by rememberme
What is the OID for RSSI on w60g?
.1.3.6.1.4.1.14988.1.1.1.8.1.12.1
This worked for me.
Thanks, but I'm getting values like 4294967228 from the OID above.
Mikrotik support, what OID to use for RSSI on w60g?

Re: v6.42.5 [current]

Posted: Fri Jun 29, 2018 4:02 pm
by vecernik87
I wonder why does the newest current version of RouterOS (6.42.5) neglects the filter rules for blocking ADS using layer7, the rule was working fine on the previous version (6.42.3)....Can someone answer me? Thanks
Are you certain that only difference is version? Is it possible that ADS are delivered through HTTPS? or maybe you enabled HW offload?
Did you try to downgrade with same config? If yes, did it start working again?

Re: v6.42.5 [current]

Posted: Fri Jun 29, 2018 4:31 pm
by Cha0s
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,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot

It works on every board and does not depend on version.
Thanks, it works ok :)