OK so accounting is a very moving target. Noted. I am probably going to table that discussion for another time. Typically the NAS requires a session timeout in order to be able to disconnect an unauthorized user. I usually recommend once per day be the minimum. The NAS will have more or less subscribers depending on the population surrounding the NAS. The only thing that would cause all subscribers to come online at once is a FR server reboot or something severing the connection between the NAS network and FR. So I guess the answer would be yes, something could cause that to happen. I am really looking for some idea not a hard and fast recommendation. Something like "any quad core will do" or "you are going to need a lot of ram and processor power". David -----Original Message----- From: freeradius-users-bounces+davidp=wirelessconnections.net@lists.freeradius.org [mailto:freeradius-users-bounces+davidp=wirelessconnections.net@lists.freera dius.org] On Behalf Of Arran Cudbard-Bell Sent: Thursday, January 9, 2014 2:08 PM To: FreeRadius users mailing list Subject: Re: Server Scaling On 9 Jan 2014, at 18:30, David Peterson <davidp@wirelessconnections.net> wrote:
Here is the core data: 200 NAS 50,000 WiMax users 1 authentication per day Protocol EAP-TTLS MySQL database (either on the same server or off, looking for recommendations on that). Accounting (looking for a recommendation on whether or not it should be hosted separately.
Is that enough information or am I still missing something?
For accounting data the bulk of the packets are usually interims, so you need to specify what the interim interval will be. Is there a particular reason every single one of your subscribers will re-authenticate at least once a day? What will be the maximum number of users connected to a single NAS (will it be 250, or will some NAS have more)? Are the NAS completely independent? Is there anything that could cause all subscribers to drop offline and come back at once, or will such incidents be limited to a single NAS? Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2