I haven't had this issue with other hardware, so I do suspect something in the wireless driver for this board is at fault. Any ideas, anyone?
Hi,I've been running this one since 3 days after rOc-nOc got their first shipment. It wasn't *bad* with 5.6, but recent versions have had this problem. 5.11 was the worst, 5.12 has been better, but far from perfect. I haven't tried rolling back the firmware to what shipped with 5.6 (is this possible/easy without a serial port?), but I did netinstall 5.12 fresh with keep configuration, and am currently at 2d7h uptime (which is a recent record). So, perhaps it was a bad block in the kernel. Time will tell.
I think I downloaded as far as 5.8 without seeing an improvement. I was more interested in downgrading the firmware, rather than the OS.
I had a reboot about 16 hours ago. Still leagues better than I'd been seeing, and seems to be more frequent when my iPad is downloading large binaries from apple.
Ok, will do.try 5.13
Ok, just upgraded two locations. We'll see.It definitely presents like a wifi driver issue. I've sent numerous supouts to support, and the last suggestion I got was trying 5.12rc1. So far, 5.13 seems to work. I haven't seen this problem since my upgrade to it.
I still see reboots, less then before, but it still happens on 5.13 too.Upgraded to ROS 5.13 - 24 hours ago...so far so good.
I'm very close to forgetting this RB751U-2Hnd. Too much trouble with it.Nope. Not fixed in 5.14, though *much* less frequent.
Thats what I did. Now re-visiting and hoping things are fixed but it would appear notI'm very close to forgetting this RB751U-2Hnd. Too much trouble with it.
We 've stopped deploying them.It all seems to be wireless-related, so I'm hoping they'll eventually get the driver right. But if they don't have these problems with the RB2011 with wireless, they'll probably kill this model outright.
Hi Normis,have any one of you contacted support with RB751U which reboots, and is running v5.14? We need supout.rif files.
post your ticket number pleaseAnyone who heard something from Mikrotik support about this the last weeks?
I've sent them lots of supout's and personal findings, but didn't receive any replies yet
4 posts abovepost your ticket number please
Same thing happened here, no reboots since disabling watchdog.Not I. No reboots since disabling watchdog, much as that idea galls me.
Yes, but other issues will rise if your wifi gets loaded.Same thing happened here, no reboots since disabling watchdog.Not I. No reboots since disabling watchdog, much as that idea galls me.
17:45:15 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:45:22 wireless,info 78:92:9C:06:C3:48@wlan1:hotspot: connected
17:46:20 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: reassociating
17:46:20 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, ok
17:46:20 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:46:27 wireless,info 78:92:9C:06:C3:48@wlan1:hotspot: reassociating
17:46:27 wireless,info 78:92:9C:06:C3:48@wlan1:hotspot: disconnected, ok
17:46:27 wireless,info 78:92:9C:06:C3:48@wlan1:hotspot: connected
17:47:27 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: reassociating
17:47:27 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, ok
17:47:27 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:47:28 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:47:28 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:47:28 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:47:28 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:47:28 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:47:28 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:48:34 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: reassociating
17:48:34 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, ok
17:48:34 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:48:34 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:48:34 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:42 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: reassociating
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, ok
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:44 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:49:59 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:50:18 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:50:27 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: disconnected, received deauth: unspecified (1)
17:50:34 wireless,info 58:94:6B:6D:E9:E0@wlan1:hotspot: connected
17:52:28 wireless,info 60:33:4B:19:68:8F@wlan1:hotspot: connected
17:53:12 wireless,info 60:33:4B:19:68:8F@wlan1:hotspot: disconnected, extensive data loss
Damn, I was just upgrading a few more.Oh, crash and burn.
So, after about a week of zero problems, my AP complete flaked. Couldn't associate, SSID only visible for several seconds every few minutes, not even visible on a WiFi scanner. Reboots didn't restore it, not enabling/disabling. Nothing in the logs, radio still shows under sys reso pci. Downgrade to 5.14 brought it back. That was scary.
So, don't trust 5.15rc1 to solve your problems. I'd rather deal with some reboots.
Check the following in your RouterOS settings: Is wireless rate selection "advanced"? is encryption set to only "AES"? is RouterBOOT upgraded to 2.38? Is distance set to "indoors"?And, there we go again. Big upload caused a reboot:
jan/01/1970 19:00:17 system,error,critical router was rebooted without proper shutdown (cause 1)
[admin@MikroTik] > tool profile
NAME CPU USAGE
wireless all 1.5%
www all 0.5%
ethernet all 0%
console all 2.5%
flash all 92.5%
ssh all 0%
firewall all 0%
hotspot all 0%
management all 1%
profiling all 1.5%
queuing all 0%
routing all 0%
bridging all 0%
unclassified all 0.5%
this is off topic, a different issue. you need to contact support with your RIF file and we will see why Flash process is running so actively.We too are experiencing this on RB750GL. Same process "flash" is using high cpu and eventually triggering the watchdog timer.
Sorry Normis, I wrongly assumed since it was also 7xx series that it was the same issue. I have emailed support.this is off topic, a different issue. you need to contact support with your RIF file and we will see why Flash process is running so actively.
We were trying to create supout.rif while experiencing high CPU load by flash process with no success. 30 minutes wait - and RIF still was not ready. Sorry that I didn't mention this before.you need to contact support with your RIF file and we will see why Flash process is running so actively.
about the above RB751U problems - you all need to send your RIF files to support, make the files as close to the problem as possible.
Then I hope there are still changes compared to 5.15RC1.Please all try v5.15, we have fixed some RB751U problems there.
Ok, we'll see after tonight.there have been at least ten v5.15rc releases, so yes, definitely
[admin@MikroTik] > system resource print
uptime: 5d6h7m39s
version: 5.14
free-memory: 46360KiB
total-memory: 62196KiB
Go for 5.16, 5.15 stops all traffic over wireless after some heavy load.Since RouterOS 5.15 we have no significant issues. Sometimes CPU usage increases but RB recovers without rejecting service. Currently we have 17 days uptime. Wondering do we have to try 5.16 or leave it as is
True enough about the the wifi disappearing. I have booted up all my RBs today morning and in the evening when I got home the 951 wifi was gone. The disable/enable trick worked, but that's not the way to go. Any idea hos is this case progressing with the Support?The 951 seems like a great replacement, since it doesn't suffer from *this* bug in any way, but the wireless does disappear every few hours, until you reboot or re-enable the (enabled) wireless interface. MT support has confirmed this bug has been reported by multiple sources, and they're currently working on it.
Yes, I'm with same problem on rb751U, flash utilization goes up to the max, router gets unstable, no winbox access and, if I'm lucky, I can telnet to it and reboot it.No change to rb751U-2Hn 100% flash utilization with 5.19.
Ticket #2012062266000481
+1 and I really admire your patience with this, I gave up this device months ago already.But it's been 8 months since I've reported my first 751 bug to MT, and they just haven't been able to make it work even as reliably as cheap SOHO gear.
is this a joke? the problem was reported on Nov 2011 and now it's already 1 year and still not fixed? How can we (system integrator) rely on this product with such bad support? This is a major issue that is a deal breaker for this router. If support is unable to fix it, the company should have recalled the product. How can we trust Mikrotik anymore? We have bought over 100 pcs to be implement and now we have to put the project on hold. We have already spend resources buying and implemented the devices on various locations. Now we need to recall them or something and that cost us double of our costs. MT was a very promising company but having this kind of support really set the reputation back few years behind others.
What are you talking about "disappointing range"? Which part of my post have this 2 word?is this a joke? the problem was reported on Nov 2011 and now it's already 1 year and still not fixed? How can we (system integrator) rely on this product with such bad support? This is a major issue that is a deal breaker for this router. If support is unable to fix it, the company should have recalled the product. How can we trust Mikrotik anymore? We have bought over 100 pcs to be implement and now we have to put the project on hold. We have already spend resources buying and implemented the devices on various locations. Now we need to recall them or something and that cost us double of our costs. MT was a very promising company but having this kind of support really set the reputation back few years behind others.
Please clarify which issue you mean. Most of the above reports are very vague and generic. "disappointing range" is not a specific issue, especially for a SOHO (small office, home office) type of device. What range were you expecting? Most phones and laptops can't get 50m with a clear line of sight, no matter which AP you use.
This is the exact issue we are seeing on RB751U, RB750UP, RB750GL and RB2011. If we swap them out with a PPC router e.g. RB1200 the problem goes away completely.Here's the steps that will reliably spin up the flash:
Using my config (or any other it seems) do the following:
On a computer on the WIFI AP load up high-bandwidth, multi-stream traffic (I use debian CD ISO torrents). Once it's running, snmpwalk the router. About halfway through (right before it checks the disk, I suspect), the flash process will go to 100%, the management sessions will freeze, the snmp query will timeout, and the router will remain pegged until the traffic is stopped, at which point it will go back to normal.
(updated to ticket # 2012062266000481)
Ok you both. I did the test as described, and had no issues. Please tell me what I did wrong:This is the exact issue we are seeing on RB751U, RB750UP, RB750GL and RB2011. If we swap them out with a PPC router e.g. RB1200 the problem goes away completely.Here's the steps that will reliably spin up the flash:
Using my config (or any other it seems) do the following:
On a computer on the WIFI AP load up high-bandwidth, multi-stream traffic (I use debian CD ISO torrents). Once it's running, snmpwalk the router. About halfway through (right before it checks the disk, I suspect), the flash process will go to 100%, the management sessions will freeze, the snmp query will timeout, and the router will remain pegged until the traffic is stopped, at which point it will go back to normal.
(updated to ticket # 2012062266000481)
Hi Normis.
Ok you both. I did the test as described, and had no issues. Please tell me what I did wrong:
Ok you both. I did the test as described, and had no issues. Please tell me what I did wrong:This is the exact issue we are seeing on RB751U, RB750UP, RB750GL and RB2011. If we swap them out with a PPC router e.g. RB1200 the problem goes away completely.Here's the steps that will reliably spin up the flash:
Using my config (or any other it seems) do the following:
On a computer on the WIFI AP load up high-bandwidth, multi-stream traffic (I use debian CD ISO torrents). Once it's running, snmpwalk the router. About halfway through (right before it checks the disk, I suspect), the flash process will go to 100%, the management sessions will freeze, the snmp query will timeout, and the router will remain pegged until the traffic is stopped, at which point it will go back to normal.
(updated to ticket # 2012062266000481)
Interesting. I have some of this random reboots on my router weekly. This problems starts ( i believe ) when I upgrade my router to the 5.24 version. With the original 5.16 version i isn't have this problems.In my case the problem was solved installing the firmware 6.0 RC6
Intesting, are you still using this config on your routerboard @Turb0 ?Hi all again, my setup, 14db it not priorities for best stability, it`s just my choice , but rate selection played a major role, and security profile in wireless section.
You try this configurations ?I have also problems with strange restarts by watchdog for some time, I try to connect to the event and it happens most often when talking on Skype - even one person in the network. Upgrade to version 6.0 caused a marked decrease of such events, but not a total elimination.
751U-2HnD ROS 6.0 rb fw 3.07, acting as a home NAT router
Yep, I'm observing this topic from the beginning, but my wifi config was set just before... As I wrote, now resets occur less frequently (literally one since the release version 6).You try this configurations ?
Here with this configs my router was online without reboots for 20 or more.Yep, I'm observing this topic from the beginning, but my wifi config was set just before... As I wrote, now resets occur less frequently (literally one since the release version 6).You try this configurations ?