We had this problem (or symptoms) without the openflow package installed. Tested on 6.31rc16 and 6.31. The running services are dhcp, pppoe, routing and mpls. No hotspot or special configuration. But like I said before, I can't report because there are no access to generate the supout file.Upgraded two RB493G, one freezes after 40 - 60 minutes of use, no IP access, no MAC access, only Power off power on to restore...i try upgrade my RB493aH .. run 5 min and blocked, cant acess via mac or ip..
power off, power on.. again 3min, again 20 min.. WTF with 6.31.. with problems i return to 6.29.1, i have lucky that these mtik was on my house, so i can unplug power, but we have some network in the city, not good option.
Another - still running OK for 1 day 6 hours.
Difference in between these two routers was presence of Openflow package on the failing router. Disabled it and more than one hour still running.
32-bit Kernel always was limited to 2GB of RAM, i think they eventually will add it, but as we can see from CHR there are still many things and features not working with that checkbox, so give them time to fix it.yes, 6.32rc2 fixes multicore support, but without checkbox allow x86-64 router uses only 2gb of ram...Normis, may be You can leave this option for x86 systems with more than 2 gb of ram?
Some examples (obviously using 6.31):rextended - Can you please name where are you setting this password? I have tested with PPP/Secrets and User/Password. Have not managed to reproduce.
Thanks, is surely related to this change:rextended - Thank you! Key here was - winbox 2.2.18
With 3.0rc12 it works fine. I will forward this to our developers.
Aug/17/2015 14:31:58 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/17/2015 15:34:02 system,error,critical router was rebooted without proper shutdown
Aug/18/2015 14:30:29 system,error,critical router was rebooted without proper shutdown
Aug/19/2015 00:24:53 system,info,critical Firmware upgraded successfully, please reboot for changes to take effect!
Aug/19/2015 00:25:17 system,error,critical router was rebooted without proper shutdown
Aug/19/2015 04:51:34 system,error,critical router was rebooted without proper shutdown
Aug/19/2015 04:51:33 system,error,critical router was rebooted without proper shutdown
Aug/19/2015 06:08:36 system,error,critical router was rebooted without proper shutdown
Aug/20/2015 02:13:27 system,error,critical router was rebooted without proper shutdown
Aug/20/2015 02:13:27 system,error,critical router was rebooted without proper shutdown
Aug/20/2015 09:41:00 system,error,critical router was rebooted without proper shutdown
Aug/20/2015 09:59:30 system,error,critical router was rebooted without proper shutdown
Aug/20/2015 09:59:30 system,error,critical router was rebooted without proper shutdown
Aug/20/2015 23:30:26 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 01:32:33 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 04:34:44 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 05:38:25 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 05:38:26 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 05:38:25 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 05:38:26 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 05:38:25 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 07:51:27 system,error,critical router was rebooted without proper shutdown by watchdog timer
Aug/21/2015 11:53:43 system,error,critical router was rebooted without proper shutdown by watchdog timer
OK, I've seen the graph.
Well, let me explain what can happen in bulk upgrades, or manually working as a robot late at night (not to disturb you clients...)This looks to be quite dangerous version. It killed one of my testing devices. I still wonder why all the people massively install every new version without any testing in the laboratory before.
That's just what I mentioned.Also, please, do not fool us that 6.32rcXX is something that would be converted in 6.30.X. Please, keep the versioning, so, if you maintain 6.30 for bugfixes, make the 6.30rcXX and then the correct 6.30.X but keep it distinct from 6.31rcXX and from 6.32rcXX. Do not mix the bugfixing with new features release, so we will never saw sentence like "This will not be corrected in 6.30.X but in 6.31..." Everything should be corrected in the version actually maintained for bugfixes and not delayed to the next version. The subsequent version should always adopt the bugfixes from previous version and not to bring the old bugs again. Otherwise your new huge versioning system is useless.
I confirm, happened to me in an IPsec connection type on Peers/Secret (i prefer to use WinBox from The Dude 3.6 but I don't know what version of WinBox it is...)Some examples (obviously using 6.31):rextended - Can you please name where are you setting this password? I have tested with PPP/Secrets and User/Password. Have not managed to reproduce.
Simply open on winbox 2.2.18 interface/wireless/wlan1 panel and change somethihng, nv2 password are replaced with literallly "***********".
Launch bandwidth test (on one device with password) it start,
stop the test and click start again, instead of real password the winbox sent literally "******" as password, because on memory the password are replaced with "*"
Open one wireless security profile, if you uncheck hide password, the passwords are still to "********",
if you close and re-open the panel the password are show.
If you suibmit the panel with "hide password" checked, the passwords are replaced with real "*"
SAme thing with EoIP shared password
14:45:55 script,warning DefConf: Unable to find wireless interface
This is exactly the problem I noticed on 6.31rc16 and 6.31 final. Can you make a supout file and send it to Mikrotik support? I could not send because my routers (two, not so important) were in production and I needed go back to 6.30.2.RB750UP is not accesible or visible in Neighbours since the upgrade. Ruter is responding to ping and is working.
Same here. RB750 - all switch1 ports (ether2-ether5) are flapping like crazy every 2-3 seconds. Downgraded to 6.30.2 and the issue disappeared. Another try to upgrade to 6.31 - flapping is back. Downgrade agin to 6.30.2 - no flapping.I have issue with switch port flapping with 6.31 on "model: 750", after downgrade to 6.30.2 all is ok
Hm, I am afraid that programmers from Mikrotik will be able to maintain only one working version - this is the way they are used to do for several years. They tried to create new versioning system, but look - there are much more "new" and "rc" versions and only two bugfix versions for 6.30. And look to changelog, how many bugs are solved in versions > 6.30 which are currently still not implemented to 6.30.X. I impatiently wait for bugfixing version 6.30.X which will contain correction of at least CRS port flapping problem (I think I am not alone, because this bug is f*****g annoying). I would like to update my CRS with bugfix version, but currently I do not have any other option than install screwed version 6.31 or some 6.32 "rc" version. So from my point of view (with several years of programming exprerience) they are not able to maintain several versions, they will release new versions in the same way they did it for years. From my point of view this is not good info regarding RouterOS software because they promised something they are not able to achieve (at least in this moment from version 6.30).jarda wrote:
Also, please, do not fool us that 6.32rcXX is something that would be converted in 6.30.X. Please, keep the versioning, so, if you maintain 6.30 for bugfixes, make the 6.30rcXX and then the correct 6.30.X but keep it distinct from 6.31rcXX and from 6.32rcXX. Do not mix the bugfixing with new features release, so we will never saw sentence like "This will not be corrected in 6.30.X but in 6.31..." Everything should be corrected in the version actually maintained for bugfixes and not delayed to the next version. The subsequent version should always adopt the bugfixes from previous version and not to bring the old bugs again. Otherwise your new huge versioning system is useless.
RB750, same problem, ports 2 - 5 flaps permanently. 6.30.2 works.RB750:
Switch DES-1005P on any port mikrotik.
Auto Negatiation is ON.
Link at intervals of 2 seconds up...down...up....down...
Downgrade to 6.30.2 solved a problem,
If I can't access the router, I can't make supout eitherThis is exactly the problem I noticed on 6.31rc16 and 6.31 final. Can you make a supout file and send it to Mikrotik support? I could not send because my routers (two, not so important) were in production and I needed go back to 6.30.2.RB750UP is not accesible or visible in Neighbours since the upgrade. Ruter is responding to ping and is working.
PS: They stopped working completely after some time and I had to do a manual power cycle.
[root@net-dfw1 snmp]# snmptable -v2c -Ci -c monitor 172.16.0.50 mtxrScriptTable
SNMP table: MIKROTIK-MIB::mtxrScriptTable
index mtxrScriptName mtxrScriptRunCmd
15 monitor_config 0
16 regmonitor 0
17 startup 0
18 syslog 0
[root@net-dfw1 snmp]# snmpget -v2c -c command 172.16.0.50 MIKROTIK-MIB::mtxrScriptName.15
MIKROTIK-MIB::mtxrScriptName.15 = No Such Instance currently exists at this OID
[root@net-dfw1 snmp]# snmpset -v2c -c command 172.16.0.50 MIKROTIK-MIB::mtxrScriptRunCmd.15 = 1
Error in packet.
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: MIKROTIK-MIB::mtxrScriptRunCmd.15
[root@net-dfw1 snmp]# snmpset -v2c -c command 172.16.0.50 MIKROTIK-MIB::mtxrScriptRunCmd.16 = 1
Error in packet.
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: MIKROTIK-MIB::mtxrScriptRunCmd.16
[root@net-dfw1 snmp]# snmpset -v2c -c command 172.16.0.50 MIKROTIK-MIB::mtxrScriptRunCmd.17 = 1
Error in packet.
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: MIKROTIK-MIB::mtxrScriptRunCmd.17
[root@net-dfw1 snmp]# snmpset -v2c -c command 172.16.0.50 MIKROTIK-MIB::mtxrScriptRunCmd.18 = 1
MIKROTIK-MIB::mtxrScriptRunCmd.18 = INTEGER: 1
No i have the same problem on my router. My wifi hang/freeze many times and the system too.By upgrading to version 6.31 on an RB751U-2HnD the WiFi and sometimes the system too hangs or completely freezes. I was unable to create the supout.rif because of the system hang. (Firmware version is 3.24)
I have fallen back to version 6.30.2 and there is now no problem at all.
Please let me know if anybody else has the same problem, or if it's a unique hang/freeze on my system only.
Thanks.
DomiNet.
What's new in 6.31 (2015-Aug-14 15:42):
*) chr - added support for VMware SCSI virtual disks
*) chr - added support for VMware vmxnet3 network card
for some time, standard releases are unstable, and beta/candidate are stableFor several years all standard releases was never a danger to upgrade to, but with version v6.31 you guys just made it. If I were you, I might consider to call back version v6.31 and to keep v6.30.2 as the latest standard release.
Dominet.
If there would be an 6.30.3 with the PPoE upload speed and the CA certificate import fixed, I would be happy with it...
Nah, forget the CA, just the upload speed fix, backport from 6.31...
This is so sad... We are on the MT hands now (or brains). Let's wait.If I can't access the router, I can't make supout eitherThis is exactly the problem I noticed on 6.31rc16 and 6.31 final. Can you make a supout file and send it to Mikrotik support? I could not send because my routers (two, not so important) were in production and I needed go back to 6.30.2.RB750UP is not accesible or visible in Neighbours since the upgrade. Ruter is responding to ping and is working.
PS: They stopped working completely after some time and I had to do a manual power cycle.
This problem no longer exists in version 6.32RC5RJ45 SFP 10/100 / 1000M copper module in RB922 with RouterOS 6.32RC3 does not work when you plug the network cable into the SFP module, you lose the connection to the Ether1.
Stay tuned...
Problem confirmed. I upgraded 28 routers (incl. two x86 machines) from v6.29.1 to v6.31 and, on 2 of those, I completely lose Winbox access via IP or MAC, as well as SSH, a short while after each and every reboot. Otherwise, they seem to function fine.i try upgrade my RB493aH .. run 5 min and blocked, cant acess via mac or ip..
power off, power on.. again 3min, again 20 min.. WTF with 6.31.. with problems i return to 6.29.1, i have lucky that these mtik was on my house, so i can unplug power, but we have some network in the city, not good option.
In our case, what sets these two 951G-2HnD routers apart from the others, is that 4 of their ports are on a bridge and ether5 is used to connect to another router – an identical 951G-2HnD which serves as the former's backup, and which can be accessed without problems. When ether5 is disconnected, the problem seems to go away. Do I need to contact support?
Many update firmware each time when software brings new. Several complaint about the fact it can't be done in one go. Now you always need two reboots.6.31 version works fine on my test lab equipment RB750G after firmware upgrade to 3.24 .
Previous version of firmware was 2.26 and I was getting port flapping, kernel caused reboots and other unwanted issues.
It looks like Mikrotik staff tests only with fresh firmware, btw everyone never updates firmware without reason. If there are possible issues, you need to inform user with LARGE RED LETTERS that old firmware is not recommended with new release.
Can anyone confirm that 6.31 is ok with last firmware on their test environment.
Anyway I am still unsure if it is safe to install it in production environment.
Yes, Mikrotik should pull off v6.31 from download page to avoid more headaches. We already have it enough in everyday life.This is a very serious problem, as routers in remote locations cannot be accessed and hence cannot be downgraded. Ideally, it should not recur in a proper released version ever again.
All versions are a danger to upgrade. Run it in a lab first. That's what we do, for a number of hours/days.Normis,
Unfortunately version v6.32.RC3 still hangs or completely freezes devices RB751U-2HnD after using for a couple of hours.
For several years all standard releases was never a danger to upgrade to, but with version v6.31 you guys just made it. If I were you, I might consider to call back version v6.31 and to keep v6.30.2 as the latest standard release.
Dominet.
Agree, I have similar problem. If a POE powered device is connected, the 750UP completly hangs. I had to downgrade to ROS 6.29.1.Big WARRNING DO NOT upgrade 750UP I have problem on network after couple hours devices just crash some reset by watchdog some not.
I kill my network with this upgrade.
Upgrade to ROS version 6.30.4 it works, but with 6.31 it very unstable.Agree, I have similar problem. If a POE powered device is connected, the 750UP completly hangs. I had to downgrade to ROS 6.29.1.Big WARRNING DO NOT upgrade 750UP I have problem on network after couple hours devices just crash some reset by watchdog some not.
I kill my network with this upgrade.
Not true! The 'becoming invisible' issue of some 750UP's existed until 6.32rc2, and rc3. Only now in rc5 it seems to have been solved....Please follow changelog for 6.32rc versions. Basically, if you use version 6.x, then check if issue is not fixed in 6.x+1rc.
Omnitik and 750UP issues are already fixed in 6.32rc version for a while now.
First of all use normal carácter size... this is very irritating. Like you are shouting...hi
i have a routerboard ( hap lite RB941-2nD ) and i want to install user man. on it. how could i do this?
in this site (mikrotik.com/download) there is no package for user man.
version of my router os : 6.31
i've downloaded extra package And main Package but user manager.npk doesn't exist.
is it possible ,that user-man install on my RB?
what should i do????
please help meeeeeeeeeeeeeeeee
/system package update> install
channel: current
current-version: 6.31
latest-version: 6.31
status: Downloaded 90% (8.0MiB)
/system package update
cancel check-for-updates download edit export get install print set
1) http://download2.mikrotik.com/routeros/ ... s-6.27.zipthanks for your help
please give me the url for:
1- router OS 6.27 for SMIPS ( hap lite - RB941-2nD )
2- a package that contain USER-MANAGER
thanks a lot