Been there, done that
![Smile :-)](./images/smilies/icon_smile.gif)
. It's FUN in the beginning.
Follow my story, if you have time for this.
Similar situation: holiday resort with tenants who pay for the expensive internet connection. (Quota metered by ISP because it is based on regular 4G subscriptions used in shared SXT LTE devices, with global wifi distribution in- and outdoor.)
Surrounded by more tenants from the neighboring resorts, that have no decent distributed internet. Open 52 weeks a year, typical stay 1 or 2 weeks.
Those persons around are sometimes tenants in a house with internet subscription.
The procedure and password for wifi is in the Vacation Rental Welcome book.
How to separate rightfull use from abuse? Avoiding false positive and false negative detection of rogue users? Without changing the passwords for owners and regular tenants?
So information is not usable as separation/authorization. Everyone has the needed information, that is valid for the vacation season.
The wifi coverage is a square km, neighbors are only 10 meters away, and sometimes just walk by.
Wifi RF signal and wifi operation principles are not helping. Interface rate will drop, as range extends. Far away clients get much MORE air-time than intended nearby client devices.
Sector limited antenna could indeed do something to limit the coverage.
TX power manipulation is not very effective (incrementing the "antenna gain" parameter in ROS , which is indeed not about the antenna gain itself, but the compensation in the TX power for that antenna gain, and must be equal or greater than that physical characteristic). At least this power reduction does not require math.
Setting TX power with "all rates fixed" TX Power must be calculated. The 'status' of the interface gives the current max value. In my case , for my latest acquired "SXTsq 5 HP" the max TX power in region ETSI is 8 dBm, for the channel with the highest EIRP in ETSI region, which is 27dBm.
And again the access will not drop the way we like, there is no sharp range limit, instead there is a ever declining service speed, that extends very very far.
Lower TX power will reduce the MCS rate used, also for the local devices.
Disabling lower supported interface rates (6-54Mbps and MCS0-MCS7, is NOT possible with VHT MCS (802.11ac))
It will also make local client devices disconnect faster.
Increasing the "basic rate" to enforce a minimum good working MCS never gave a satisfactory distinction.
Access list minimum receive signal, needs a lot of tuning. And many neighbor client devices have a stronger signal than some intended local ones.
How to spot the abusing client devices? By the timing and selection of AP where they connect.
Once identified they can be denied use of the internet. (e.g. MAC based)
Denying or rejecting is the wrong action here. They will just look and test further until they regain access. Remember they have time, and are desperately seeking for internet.
Reducing their services until ISP costs are acceptable, will not inform them when they have full access or not, they have no clue. They eventually stop, because of the poor service.
In the beginning this is doable as manual filtering. But 52 weeks, many tenants. Some automation is needed.
Low power connection, outdoor AP only, wrong user for that AP (this network is on RADIUS EAP authentication, not device MAC), wrong time ... are all indications for putting that device in a list or VLAN , where they have minimal service. But it's like fighting SPAM, you are either too strict, or too loose. Intention is to just get the obvious ones. The reduced service can be gradual, based on the number of indications.
In a public city network we managed, we had to turn off some AP's at night. Indeed large groups congregating outside the city library. We had to send a clear message there, That there was no service outside the library open hours.
Putting in porn filters helped a lot also.(Resident abusers).
Rogue AP, honeypot AP outdoor etc are just next possibilities, to identify abusers.
Identifying client devices that get a DHCP address (also) outside the business hours, is an identifier.