I suggest adding traffic quota (or limitation) for each user + expiration date.
I assume expiration date is pretty straight forward: just a simple script that auto DISABLEs (temporarily deleted but kept somewhere for re-enabling) the user's (or peer's) account at a certain date.
Also by traffic quota or limitation I mean the ability to limit data usage of a peer to X GB per month. It requires a field in each peers' settings for the limit to be set by the admin and a periodic job that checks total data from the database and compares it to the limit and disables the peer if the limit has been reached. This task can be done every 1 hour or maybe even 4.
I suggest adding traffic quota (or limitation) for each user + expiration date. I assume expiration date is pretty straight forward: just a simple script that auto DISABLEs (temporarily deleted but kept somewhere for re-enabling) the user's (or peer's) account at a certain date. Also by traffic quota or limitation I mean the ability to limit data usage of a peer to X GB per month. It requires a field in each peers' settings for the limit to be set by the admin and a periodic job that checks total data from the database and compares it to the limit and disables the peer if the limit has been reached. This task can be done every 1 hour or maybe even 4.