Replace Ubiquiti products.

[AtTilla]

So today we not waiting longer for the new firmware because our customers very angry. Replace all New Ubiquiti products with another vendor access point. The 5.1 RC3 software impression is sometimes very good and sometimes very poor. Now the older 802.11G client could not connect correctly to Ubiquiti accesspoint. The New Ubiquiti system have to much known mistake. Thank you Ubiquiti for the very bad christmas time.

Attila Borbely
CEO
WZone Ltd.
Hungary

[lncommunications]

Hi AtTilla,

Could you explain a bit more about the 802.11g compatibility issue please, I assume you are using the BulletM2 as there are no other 2.4Ghz M devices out yet.

I have tested a number of 802.11b and 802.11g CPE using the BulletM2 as an AP and they work brilliantly, the RX sensitivity is excellent and I even managed to get 5mbps (actual TCP speed) from an ageing 802.11b CPE via the BulletM2.

What are your issues?

[AtTilla]

Yes we use Bullet M2HP. We only about 10-15 user per accesspoint. I think is not to much. :) We have more than 20 accesspoint in different RURAL area. The NanoStation2 CPE connecting to Bullet M2 sometimes work correctly, but the older client (Integrated NoteBook wireless card, and another vendor CPE device, and USB wireless client) after we upgrading 5.1 RC3 could not connect correctly. The Bullet M2 Web management AutoACK information after 1-2 hour show brutal value in example 43km and 62km in all Bullet M2 accesspoint. We testing Manual ACK setting with longest client distance + 20% or 50% the result is slow speed and connecting problem with legacy device. And some place the Bullet M2 with WDS accesspoint mode randomly (Daily, Hourly) freezing with or without UPS. We tesing (Line Interactive and Offline or Online UPS with same result). Before we using Cisco 1200 AP all the site without any problem. We change Cisco 1200AP with Bullet M2 because the Ubiquiti have better receiver sensitivity and TX power. I think is not my best step. :) But the Ubiquiti communication works very well. Just not true. :)

[lncommunications]

But the Ubiquiti communication works very well. Just not true.

It's true for me, we have a Bullet2M with 17 clients on that has been working AOK for at least 2 months solid.

CCQ's are good and ACK is good.

http://www.freetheinternet.org/g_on_bullet2m.gif

[AtTilla]

My Results:

And off course 5.1Rc3 impression the "older or integrated" wireless client could not connect or could not connect correctly. The client AP50 terrible icmp and tcp performance. We test all channel, with or without Manual ACK setting. The 5.1Beta allow connect "older or integrated" wireless client connection, but not very well performance, the 5.1Rc not.

... The Extra reporting function not work correctly in all 5.1 version.

The base station CCQ and data rate information is not valid. Because can you see AP50 information in Bullet M2 status page after ClientAP50 data, in ClientAP50 status page. It's not true. Similar than Mickey Mouse. :) I make this image less than 1 minute difference.

The distance from AP50 and ClientAP50 less than 2 km.

[AtTilla]

And another two problem Accesspoint with different area. :(

In Ap04 enable AutoAck the realy max client distance less than 2km.

And off course the noise rate all place -96dbm :)

When reboot the device the Auto Ack about 2-5 minutes show about correct value, and after ... This time the NanoStation2 CPE recalibrate the ACK timeout (Auto ACK) , and the CPE ACK change similar terrible.

[gunther_01]

In a fixed environment I would think you would try to limit your variables, like adaptive antenna selection in the NS radio. And having data rates enabled that are higher then your legecy equipement can handle. Shown in one pic as a unit going up to 58Mbps.

[lncommunications]

Noise floor -77dB?

[EdEllingham]

I caught that too...that's a really high noise floor. You also have a fantastic signal, but still...

[rdw]

if you are using M series gear with 802.11 AB or G then i recommend only using firmware version 5.0.2 build 2956 it works the best with alien gear

[AtTilla]

The high noise floor starts when you use 2 device with all 2 in APWDS mode. When disable APWDS mode and setting only Accesspoint mode, the noise floor in ClientAP50 is normal.
:(

[rdw]

at one location we have about 20 customers on a AP and all those customers are using Nano M5,s connected to a alien AP in standerd AP mode (NO WDS) and it work flawless. it has to work flawless since it requires a air plane flight to get there . we can not have any failure

[lncommunications]

AtTilla, are all your AP's in AP/WDS mode, as in Wirelessly connecting to each other via WDS?

[AtTilla]

The High Noise Floor Mistake is solved. We restart NanoStation2 (ClientAP50). The noise floor now -96 :).

- Just 2 pair of our Accesspoint running AccessPoint WDS Mode. This is just testing scenairo.

- The highest data rate in AP50 (58.5) made by one BulletM2 connect in AP50 with WDS Acesspoint mode. When the AP is not "heavy loaded" (12 user and 2-3Mbit/s) the connection data rate switching back (65).

[lncommunications]

Do any clients get a good connection to the Bullet2M as an AP?

I would stay well away from AP/WDS to AP/WDS if you can, it can cause many problems.

[gunther_01]

How are you able to run Airmax Rates with non-Airmax capable devices (alien B/G)? 58.5 and 65Mbps air rates aren't your normal g/radio rates. Unless you are running turbo Gmode. And that by itself is a nightmere. Something doesn't jive there unless you have NO alien devices attached to that AP.

[AtTilla]

Ok ! The data rate is default automatic, because the client connetcing to the accesspoint with different signal different distances and off course different data rates. We start WISP anno 2000. So we are not amatour this area. But i think is very funny. The client device (NanoStation2) show different parameter compared the BulletM2 Accesspoint. And some mistake for CCQ, Noise Floor, Data Rate, I'think all the information showing Bullet M2 is not true.

[AtTilla]

Dear gunther_01! The MCS7 rates and modulation is not "AirMax rates", is 802.11n data rates and modulation. The AirMax is not a wireless standard or protocol. Airmax just simple implementation polling procedure to the 802.11n standard.

- Please remember the first expectation in 802.11n standard qualifications the fail-safe backward compatibility with "legacy" 802.11a/b/g device.

[gunther_01]

I should have just said "n" and not Airmax.. Same difference to me (although it's not) ;). BUT, can you run "n" and b/g at the same time on a "N" capable AP. I would think that trying to put a N capable AP in the mix of a b/g environment wouldn't work well UNLESS the "N" data rates were removed on both any clients and the AP. I don't know if this is allowed with the M-series radios or not. But I would venture to say its going to mess up your qualities on the B/G only clients becuase they will have ZERO idea what is being said to them for brief moments of time. Likewise with the b/g clients talking to the N enabled AP that was just talking to a N radio in a different data rate.

If your mixing up "N" and "B/G only" clients I (think) you are going to see issues like you are seeing. I could be wrong, and don't mind if I am :) But it's something to think about since others don't seem to be having your same issue.

[AtTilla]

Thank You ! But the mixed enviroment working is expectation in 802.11n standard. The Accesspoint communicate each client with different data rates. Not the lower data rates client speed. Is the first information let you know. Please search this forum... after you find million of factory problem with ubiquiti hardware and software. Just lot of people easy resolving problem...(Change the hardware with another vendor device), and lot of UBNT customers wait the new buggy firmware (like me before).

[gunther_01]

I understand N is backward compatible with B/G. And G was suppose to be compatible with B and so forth. "Mixed B/G" was a joke... I would imagine "mixed B/G/N" will be comparible ;) This has nothing to do with UBNT in general. It's a flawed method in general to try and have so many clients (and be backward compatible) using "mixed modes" It's never worked well for ANYONE. Or at least those who pay attention to packet loss, Jitter, and overall system quality.

I think there was a bug also mentioned in the forum at one point about too high of data rates messing up your CCQ. Maybe that has been fixed. Or maybe that too is turning your bandwidth to junk. What I can tell you is that you will have a hard time letting "auto" do anything properly in a fixed point Wireless System. It's Fixed, So "fix" it and be done with it ;)

[AtTilla]

Ok ! We try change Bullet M2HP to Bullet 2HP is the legacy UBNT products in AP03 site. After i post some result. Many thanks all for the helping.

[AtTilla]

We change AP3 BulletM2HP with Bullet2HP the result is very interesting.

In AP3 connecting 20 active client. And everything works great. Even before... The ICMP and throughput fantastic good in every connected client.

-So the conclusion: When use legacy CPE device e.g NanoStation2. The Bullet2HP more more more better AccessPoint than BulletM2HP.

[whitedot]

AirOS 3.x is far more mature than AirOS 5.x.

Not all that surprising, really.

[gunther_01]

You could have also tried to limit data rates on M2 to 54 so "N" mode wouldn't kick in..like wise on "N" capable client.
That or a G mode only if available. Glad it helped

[AtTilla]

It's not possible because the M2 AirOs Firmware allow only N-Mode MCS data rate selection. Ubiquiti only allow Mixed Mode (B/G/N mixed) in Bullet M2HP.

[gunther_01]

That's good to know then.. So it's not "truly" backwards compatible. Maybe they can write that in at some point ;).

[AtTilla]

So my customers connecting in AP3 very happy and me too. After we change all AccessPoint to Bullet 2HP.

[UBNT-Mike.Ford]

Hey Guys,

We have a lot of user's in similar situations that work without issue. You CANNOT have static data rates set, and you cannot use 40Mhz mode when connecting legacy clients.

Thanks,

[AtTilla]

Thanks Mike. But before reply please read all post in this topic. :) Today we order a couple of Bullet 2HP because you know the Bullet M2HP have to much (hardware or software i' dont know) problem. We change all Bullet M2HP to Bullet 2HP. After we change all Bullet M2HP with 5.1 RC3 Firmware we start a big race. :) Like this:

http://www.indavideo.hu/video/Mobiltelefon_hajito_verseny