ACK match?

[gueswhoiam]

With the Atheros cards, does the ACK settings have to match on the AP and Client? Or do you just set it on the AP end and the client gets the setting from there? Or is it possible that you would want to have different ACK settings on both ends?

If I change the setting on the client it will still connect and pass data just fine. It's almost like that setting has no effect.

[tony]

Normally you have the AP set to what works best with the firthest client. All clients should be set to whatever they work best at. They do not need to match each other.

[dnotch]

Small changes in the client ack setting seem to have significant effects on performance once you get close to the minimum setting for a specific link distance (i.e. 0.01 miles makes a difference between a link working or not working). Is there a formula that can be used to calculate the miles to microseconds between 2.0 and 1.13 (pure propagation delay?)? Also, is there a rule of thumb for setting the link mileage in 2.x? The setting in StarOS seems to be a bit longer than the actual geographic distance, even when cable lengths, etc. are taken into account.

[bobbyc]

Are you serious?
I upgraded three towers from real old versions of starOS last night, all three had atheros backhauls. They were older versions and when I loaded the latest beta on them and rebooted, the distance on all of them was set to something like 34.85 miles or something like that. I could log into each one just fine and set the distance on one backhaul to 2 miles (1.5 actual miles) and the other 5 miles (4.5 actual miles)
Anyways I was afraid that since they were older versions before valemount 'perfected' the ack settings, that I would be screwed and would have to log into the tower from the other direction, or log into one of the 2.4ghz AP's on a tower.
Bob C