2.9.44 and 3.0.10beta association problem

RouterOS Wireless Networking
1

Hi all:
I have a very interesting problem. I have a test system set up with a 532a with sr9 and 2.9.38 as a ap-bridge on a tower. I have a client test that is a 532a in a rootenna with sr9 as station running 3.9.10beta. All works perfectly 2gh-5mhz channel.

Tonight I upgraded the tower only to 2.9.44 and the tower would not associate anymore with the client. I changed the configuration around where the tower was the station and the rootenna was the ap and I could associate again. Signals and thruput were the same as before upgrade.

I down graded to 2.9.43 and the same thing happened. Tower as ap and rootenna as client would not associate. Reversed them and all is good.

I downgraded back to 2.9.38 and everything worked as before. Tower as ap, rootenna as client perfect connection and performance.

anyone seen this before???

Everything is set at default on both ends. SR9 cards. 532a boards on both ends.

Tomorrow I am going to walk up the 2.9 releases from 38 to see where it quits working.

any info would sure help.
Kenny

2

I could never get 2.9.44 and 3.0b10 to associate… I think the same problem on 2.4.42 and even earlier. I think it has to do with the SR9s as well. I could get SR2 to associate but 10x retransmissions for every packet.

3

if you scan, do you see the other end? send us the supout.rif files from both ends

4

I’ve same problem.
I see other end from my antenna and viceversa, but WDS is not going up.

Maybe STP problem (with version 2.9.38) with newer versions of RouterOS… :open_mouth: