Hi,

IMAGES ATTACHED for 4 and 17 Tx Power settings

It appears as changes to interface tx power in CAPsMAN not appearing to be reflected in reported rx signal in CAPsMAN client registration table.

For example:

If tx power at 4dBm and rx signal of device at -65 in CAPsMAN registration table, then I would expect an increase of the rx signal for the same device if tx power at 17dBm. Not necessarily a corresponding increase but a significant change. In CAPsMAN registration table this significant change does not happen but appears to on the devices own rx signal readings.

Setup:

CCR1036 - CAPsMANv2 6.37.1 <-----------> CAP wAP ac 6.37.1 <-----------> Android Samsung S3

Latest firmware on CAPsMAN and CAP

Tx Power (4dBm then 17 dBm) changes to 5GHz interface not appearing to be reflected in reported rx signal in CAPsMAN client registration table.

HOWEVER it is reflected in Wi-Fi analyser on Android phone.

Tx Power *** rx signal in CAPsMAN *** rx signal on Android

4 *** -58 to -60 *** -68 to -66
17 *** -55 to -56 *** -50 to -56

Biggest change: 5dBm in registration table and18dBm on the Android S3

I tried provision of remote CAP / remove remote cap to apply new config changes etc. Although it appears that the tx power change is applied straight away due to de and then re registration of Android handset.

Clean 5Ghz range based on freq scan.

This is concerning for us and others as we use access lists based on rx signal strength of device to encourage AP roaming. If in-accurate this may cause significant issues. Assuming access-list uses same value from registration table. I would consider it odd if it didn`t.

Any suggestions thoughts on this issue. Or is it a problem I should report?

Kind Regards

Aidan

No change to your tx power will ever affect the signal you receive from the client device, unless the client is adaptive, in which case increasing your tx will get you a lower rx.

Sent from my LG-D850 using Tapatalk

Thank You

Thank You - Doh!