The 2 RB800's that are giving me problems both have child AP's off a dedicated card using WDS.Upgraded an rb800 from 4.17 with 2.30 firmware to 5.1 and radio board is completely unstable. It drops pings to the router it is plugged into has Kernel failures. Found "" as the current firmware and after a reboot it would show 2.30 and after another reboot it showed 2.29. had to take it to 4.17 after it hard locked and had to go powercycle it at a tower. Ticket submitted.
Had similar issues with another rb800.
I 2nd this. I was having ether pings drop and kernel failures on an AP when it had a WDS bridge off one of the cards. Switched child to station WDS rather than WDS slave and all problems went away. MT please give us some assistance with a fix! Thanks!5.1 also definately have a problem with bridging.
I have RB493AH
to
SXT via LAN port
the SXT have bridge with the LAN and wlan as ports, connecting to a RB493AH+R52Hn
Ping times even to LAN is erratic, from 5-20ms, ave 15ms.
Winbox times out/disconnect every few minutes.
SXT is just a link between the two routers, the 'local' one via LAN, the 'remote' one with wlan.
removed the bridge, made two subnets and just routed it and all is fine, LAN pings 0 or 1 ms again.
Just copy the downloadlink for your device, paste it in your browser and change the version "by hand", e.g. from http://download.mikrotik.com/routeros-mipsbe-5.1.npk to http://download.mikrotik.com/routeros-mipsbe-5.0.npk and press enter.Where can we find a old versions of RouterOS? On the download page, there is only 4,17v and 5.1. I need 5.0!!!
could you send your support output file to support@mikrotik.com and also the configuration of the setup so we could reproduce your problem?I agree. 5.1 should not be used on an 800. I am going back to 5.0 I have 4 APs that have had Kernel failures. Not good not good at all.
This is exactly what happened to me (5.1 on RB450G) just I did not realize that in fact the last command was interface ethernet switch ?5.1 on a 750G
Connect via ssh/telnet and type "interface ethernet switch ?" and ALL(!) ssh/telnet sessions will freeze instantly.
No new ssh/telnet session possible, traffic keeps flowing through the box. Only solution I've found so far is to power-cycle the box. Can anyone confirm this behaviour?
5.1 on a 750G
Connect via ssh/telnet and type "interface ethernet switch ?" and ALL(!) ssh/telnet sessions will freeze instantly.
No new ssh/telnet session possible, traffic keeps flowing through the box. Only solution I've found so far is to power-cycle the box. Can anyone confirm this behaviour?
The same here in serial console, ssh and winbox terminal too. Profiler says the "console" process is eating up the CPU.I can reproduce this issue too. This is the console 100% CPU usage issue too. In such case you can still log in using WinBox and manage router from there. (reboot)
5.1 on a 750G
Connect via ssh/telnet and type "interface ethernet switch ?" and ALL(!) ssh/telnet sessions will freeze instantly.
No new ssh/telnet session possible, traffic keeps flowing through the box. Only solution I've found so far is to power-cycle the box. Can anyone confirm this behaviour?
http://download.mikrotik.com/all_packages-ppc-5.0.zipWhere can we find a old versions of RouterOS? On the download page, there is only 4,17v and 5.1. I need 5.0!!!
+1Where is broadcast in release 5.x? It's very useful information
The problem with console consuming all the CPU resources will be fixed in v5.2.The same here in serial console, ssh and winbox terminal too. Profiler says the "console" process is eating up the CPU.I can reproduce this issue too. This is the console 100% CPU usage issue too. In such case you can still log in using WinBox and manage router from there. (reboot)
5.1 on a 750G
Connect via ssh/telnet and type "interface ethernet switch ?" and ALL(!) ssh/telnet sessions will freeze instantly.
No new ssh/telnet session possible, traffic keeps flowing through the box. Only solution I've found so far is to power-cycle the box. Can anyone confirm this behaviour?
Please generate and send supout.rif or autosupout.rif file to support@mikrotik.com, right after kernel failure.When trying to run a snooper from the Wireless Tables interface dialog (v5.1 and 5.0), RB800 reboots and first log message after reboot is "System rebooted because of kernel failure"
This does NOT occur when the individual wireless interface is opened and the snooper is run from there. It only occurs when the Wireless snooper button shown below is used.
Webfig will be fixed in v5.2.Webfig does not get to login screen when trying to load on this RB800.
And what about the very low bridging and switching speed issue? Will it be fixed soon?The problem with console consuming all the CPU resources will be fixed in v5.2.
What are the steps to reproduce this problem? Please send this report along with supout.rif file to support@mikrotik.com.And what about the very low bridging and switching speed issue? Will it be fixed soon?
I cannot create a supout.rif because console process hangs during creation. I think it's related to the console bug mentioned before.What are the steps to reproduce this problem? Please send this report along with supout.rif file to support@mikrotik.com.And what about the very low bridging and switching speed issue? Will it be fixed soon?
I can confirm that supout generation and console is working again. Bug report was sent with the support file.Please upgrade to v5.2 and test again. It contains fix for supout.rif generation as well.