Hi,

Anbody experienced problems with 532A/R52*2, RoS V3.1 ? Association problems seems to be gone and very stable but all of a sudden there's no traffic being forwarded on 2.4Ghz. Have 1 Virtual AP on this radio as well.
The other radio is running at 5Ghz and haven't got this problem.

Seems like disabling/enabling interface get's everything up and running for a while. Have about 15 clients on it.

Regards

Henrik

Hi

We can report that the 3.0 did the same, But! update the Bios on the RB532 then it works.

//Rickard

Hi

We can report that the 3.0 did the same, But! update the Bios on the RB532 then it works.

//Rickard

Thanks m8, done that now. I tell you after the weekend how things went

/Henrik

Seen any other problems with any other routerboards? Just curious if this an issue with only the RB532. -Jordan

Yes i was updating a RB112 that have 3.0 on it to the 3.1 and its now gone so the customer is on the way to pic up a new unit.
So i have to check what gone wrong...this time.

Hi

We can report that the 3.0 did the same, But! update the Bios on the RB532 then it works.

//Rickard

Did the update of firmware but still the same issue. Stops forwarding after a while. All clients stays connected and ARP table shows them all. Maybe a bridge problem. I have sent supout to support.

Regards

Henrik

I also noticed that my clients hardly have any upload so i'm going back to 2.9.50 (if it will)

/Henrik

i uptated rb133c to 3.1 from 2.9.50 and wireless interface disappeared.system resource said that nic is present in system. after reboot card returned to list

I have updated my routerboard 133 from 3.rc13 to 3.1 and all is good works perfect ? so i dont know what is going wrong on your guys ends but im not noticing any problems here.... Wireless AP has been up for 2 days so far and no dissconnects or problems atleast on laptop or Cpe unit.... I dont know.. But i will watch out for this in other units.. -Jordan

I also noticed that my clients hardly have any upload so i'm going back to 2.9.50 (if it will)

/Henrik

Well downgraded to 2.9.50.. Thinks worked for like 30 mins. Then problem came back. I am sure now that problem has something to do with bridging the AP. I saw that i could ping a client 1! time (one ping went through) then nothing came through after that. I removed the bridge interface and put the gw IP directly on card, then everything worked and have been stable for some time now. Just strange that a problem introduced in 3.1 follows back to 2.9.50 (that has been stable for long time before upgrading).

My best guess is that the R52 firmware has been 'upgraded' with the 3.1 packet and stayed there when downgrading. Performace right now is worse than before (users complaining about lack of speed, especially uploads) compared to before i started to upgrade.

Regards

Henrik

I think the more plauseable explanation is the problem is not version 3 related.

Well I have slower sppeds since 3.1, also upgraded to 3.1 & firmware 2.12 and also proiblem remains after downgrade.
Maybe you are onto something with your firmware idea. But then again, you upgraded firmware after problem appeared, after upgrade to 3?

I have a similar problem with one or two of my AP's.

Henrik - does the client last activity timer in winbox show a stupid value for all the associated users - kinda 18450.4s

Malcolm

I have a similar problem with one or two of my AP's.

Henrik - does the client last activity timer in winbox show a stupid value for all the associated users - kinda 18450.4s

Malcolm

Nope not since i had 3.1 on the Routerboard, think it's the reassoiciation problem that is solved now. Now this particular board (1 of 35) is running 2.9.50.

Regards

Henrik

Well I have slower sppeds since 3.1, also upgraded to 3.1 & firmware 2.12 and also proiblem remains after downgrade.
Maybe you are onto something with your firmware idea. But then again, you upgraded firmware after problem appeared, after upgrade to 3?

Yes, i did the firmware upgrade to 2.12 after having forwarding problems on 3.1 but it didn't change anything. When i wrote firmware i forgot to say R52 firmware. The radios also have a firmware on them. I know this is undocumented but the behavior of my system tells me that this has to be the issue, especially because this new behavior with slow uploads and bridge forwarding problems persist even after downgrading RouterOS to 2.9.50.

I have a customer well known to MT having exactly the same issues, even after downgrading to 2.9.50.

My problem is that i can't document it right away because of this particular radio is 50 meters up in the air, and the windy conditions over scandinavia right now makes it impossible to change the card for some time. Just hope MT finds a solution fast.

Regards

Henrik

I had a 532v5 AP stop forwarding traffic today too, and it was the first time I've ever seen this happen. Problem happened about 4-5 hours after upgrading it from 2.9.50 to 3.1.

Someone mentioned firmware upgrades for the RB532 and the R52 wireless card. I've never upgraded firmware on either before - someone mind pointing me to some documentation or something please.

Thanks,
Scott

Actually I have seen the forwarding problem, but its not just been wireless interface - its been any interface and connection tracking has always been off when I have seen it. I just turned it on my AP that had the problem - forgot about that.

Scott

To upgrade RB firmware, go
/system routerboard
print to see if there's an upgrade
then:
upgrade
say yes & reboot

About upgrading the R52, I'd also like to know...

I did a downgrade to 3.0 again and the problem with no traffic was still there ,and tha strange thing was when i was going in to the DNS server and did an apply with the old settings the traffic start to move again.... And before that i was rebooting the RB532 3 times with no sucess..
So it is somthing strange with the 3.1
//Rickard

I had a problem with no traffic after upgrade to 3.1

I removed my bridge and it worked.

Something has changed with bridge I think

I had a problem with no traffic after upgrade to 3.1

I removed my bridge and it worked.

Something has changed with bridge I think

Yes for sure, just funny that this particular problem follows back to 2.9.50 if you downgrade.

/Henrik

Same problem, but on pc(x86). Card is Atheros AR5413.
Only what helps is reboot or disable/enable card. Same problem on 3.1 and 3.0
2.9.50 no problem.

I think the more plauseable explanation is the problem is not version 3 related.

Okay could you please explain why you think it has nothing to do with upgrading ??

/Henrik

the R52 firmware is not changed when you upgrade to v3.0.
We need support output files from the units (APs) when they stops forwarding traffic. Also if they are MikroTik clients and they stop forwarding traffic, make the support output file and send it to support@mikrotik.com

Hi we had a problem for omni (prism card)could not connect to clients back in rc3.10? sent the outputs to MT. They fixed it with next version, we then put the equipment back in place and the backhaul (prism card) only had one way traffic. Guessing it is something 3.0x and prism cards.

In my case its fixed by removing the bridge.

However, if it helps

It was to Mikrotik Client
It was with CM9 radio cards
one was rb133 on was 153
It worked after upgrade from a day of so with no problems
when it stopped, reboot did not help get it working again.

In my case its fixed by removing the bridge.

However, if it helps

It was to Mikrotik Client
It was with CM9 radio cards
one was rb133 on was 153
It worked after upgrade from a day of so with no problems
when it stopped, reboot did not help get it working again.

All i got from support was to change MAC address on bridge

/Henrik

The great support crew @ MT did a fantastic job debugging this problem. It seems like ACL entries with very little bandwith resultet in a buffer overflow in the wireless driver (i did this to blackhole bad users). However removing these ACL entries fixes it for now until a new release comes up.

Regards

Henrik

Hi all,
I can report the same problem using intel based arch. In this tower, I'm using MkT 3.1 with 3 cards Atheros AR5213.

In 3.2 changelog, there is a fixed bug: "fixed wireless transmit lockup detection". What does it means ? are the same problem ?


regards