PDA

View Full Version : ATHROS "B" mode compatibility


David L. Vrablic
01-04-2004, 07:21 PM
I have a very difficult non LOS <1 mile path with 24 Dbi GD antennas and 500 mw amps and 100 mw Prism 2 cards using version 1.13.2 on each end.
This setup did work with an Qual of mid 30's and cbq'ed 2 meg connection..like killing a fly with a sledgehammer but it did work with all the leaves..
-------------------
I wanted to get a test setup with known factors so I swapped out the Prism's for DLINK ATHROS and the latest beta on both ends leaving everything the same.
----------------------------
I get a fleeting connection of Qual 2 or 4 but most of the time nothing.
I have tried all possible combinations of settings both fixed and auto.
Many times I have to dial in and reset the far end to get it to reassociate again even briefly..
-------------------
I swapped back to the Prism setup on this end leaving the far end with the ATHROS setup.
I got the same conditions as the ATHROS on both ends. ????

I don't think these cards like low sig. levels at all.
-----------------------
I understand the amps will not work in "G or A" mode for obvious reasons..
The question is ....
Is the "B" mode the same as the Prism cards.
-----------------
Granted this is a very tough path but that is why I am testing with it.
It looks as if I will need more drive from the cards to get the same paths as I have now no matter the mode.
------------------
Anyone please confirm legacy of b mode compatibility.

David L. Vrablic
01-04-2004, 07:47 PM
I just dialed into the far end box to see "what I could see".
It showed an association with my (Prism) end with a sig of 4/17.
My box showed no connection at all.
--------------------
I was just reading about the noise issues so I tried something.
I changed the CH on the AP (ATHROS) side from ch 3 to channel 1.
Saved an rebooted ..
It came back with a Quality of 52 a sig of -69 and a noise of -100.
I am now back on the air with this this Hybrid connection.

Strange but that is what testing is all about.
I am getting out the SA tomorrow and check the neighborhood for changes.
Then back to the ATHROS testing.

David L. Vrablic
01-05-2004, 08:20 PM
After the box came back up it ran for about a half a day then dropped it's association on my (Prism ) end.
-------------
I dialed into the far end and did a save and activate and it came right back up again.
-------------------------------------------
I can't afford to loose customers by rebooting the far end box all the time and the additional cards add to the confusion.
So
I am building a pair of single channel ATHROS boxes and hanging another antenna on each end to dup. the path.
I will then have a pure developemental system that I can bang on without beating up the customers.
For me it isn't going to be as easy as just changing out the card on my sector changing the version and connecting.
I am going to drop back to the "kiss system" and go from there.
------------------
I'll report what I find in a couple of days.

lonnie
01-05-2004, 08:40 PM
We have not done any testing that was not to another Atheros. It seems so retro to only get 5 mbps. Thanks for the feedback.

bobbyc
01-05-2004, 09:50 PM
There are a couple b glitches at this time... but that's what beta is for :)
I put 5.8ghz with b10 into service as our primary backhaul. I wouldn't have done this, but it was a emergency since our trango TLINK10's have ethernet problems (which they just fixed via beta release themselves). To date, the starOS 5.8ghz has been flawless.
I've tested some atheros b myself and have found a bug... you can't lock the rate to 11mbps or else some clients can't associate.
Bob C

lonnie
01-05-2004, 11:23 PM
I've tested some atheros b myself and have found a bug... you can't lock the rate to 11mbps or else some clients can't associate.
Bob C
Actually you can't do this with "real" 802.11b cards either. Try it. Lock the AP to 11 mbps and see how many guys you lose. The client can be locked at whatever speed is appropriate for their signal level but the AP pretty much has to be left in auto. At least the way we run things here.

bobbyc
01-05-2004, 11:28 PM
Many of my APs (hermes and prism 2.5) are locked at 11 or 5.5.
I've had no real problems; however I have had instances where when I've had to activate changes, 1 or 2 of my clients did not re-associate... and i've had to activate changes again in order to get them to re-associate.
Is this what you speak of?
Bob C

lonnie
01-05-2004, 11:51 PM
Pretty much. We have never put the AP at anything other than auto. The clients are set to 11 mbps if possible.