Hi,
I have been playing with the new rb333 and rc1,rc2 for a while but cannot make ROSv3 working with 2.9.x - can’t get more than 1Mbps traffic (yes, signal is OK - strength -62, CCQ 100/100%, yes, I tried everything I know).
Is there a proven compatibility issue? If so - when it will be fixed? Sorry but there is more than 200 pieces of rbXXX (and more than 2000 people relying on them) in the network and we can’t afford to switch off whole netowork because of the upgrade to ROS rc2.
yes, there are problems. if you use packet sniffer you will see thousands of extra ACK packets and retransmits going in one direction. I can’t believe this hasn’t come up until now - I ran into this about 2 months ago actually but dismissed it because I thought it was still being worked on in beta stages.
I have the same problem. Beta working very bad with stable. Customers disconnecting non-stop even with good signal
ime=04:13:22 topics=wireless,info message=00:80:48:41:94:43@OW1: disconnected, extensive data loss
time=04:13:30 topics=wireless,info message=00:80:48:41:94:43@OW2: connected, wants WDS
time=04:14:18 topics=wireless,info message=00:80:48:3F:5D:D5@OW3: disconnected, extensive data loss
time=04:14:26 topics=wireless,info message=00:80:48:3F:5D:D5@OW3: connected, wants WDS
time=04:16:02 topics=wireless,info message=00:80:48:3F:5D:D9@OW1: disconnected, extensive data loss
time=04:16:38 topics=wireless,info message=00:80:48:3F:5D:D9@OW1: connected, wants WDS
Uldis, do you still need some supout? We made the first rb333 deployment yesterday and today and we run in extremely low (average less than 300kbps) throughput when combining RB532 (AP) with 2.9.x (tried 2.9.38 and 2.9.46) and RB333 with RC3.
The wireless link is fine, frequency (5Ghz) does not seem to matter, ping is low and stable, around 4 ms, bandwith test is quite fine (over 4 megs), but real speed is extremely low.
RB333 to RB333 performance is perfectly fine (34 megs hdx, single nstream, 20 mhz channel)
Bye,
Ricky