[RADIATOR] Bugreport: OTP... PAP

2015-09-24 Thread Patrick Honing
Hello, Due to the update of IOS on the iPhone and de OS on the Mac which uses TLSv1.2 we upgraded our RADIUS setup. The RADIUS-setup is used for our eduroam wireless network as well as for a VmWare VDI environment. We are using a RedHat Enterprise Linux 5 environment for our RADIUS servers. We

Re: [RADIATOR] Use FarmSize parameter

2015-09-24 Thread António Mendes
Hi Hugh, thanks for your answer. The "father" process is consuming too much CPU due to the amount of requests, it's perfectly normal because we have a huge amount of clients. The Radiator's performance it's not a problem. We need to move forward because we see that the hardware it's

Re: [RADIATOR] Use FarmSize parameter

2015-09-24 Thread Hugh Irvine
Hello Antonio - I am curious to know why your “father” process is taking so much time? Have you checked a trace 4 debug with LogMicroseconds enabled to see what exactly is taking the time? If you send me a copy of your configuration file(s) directly, I will take a look and try to make some

Re: [RADIATOR] Use FarmSize parameter

2015-09-24 Thread Amândio Antunes Gomes Silva
Hi António (and the rest)! From the Radiator 4.15 Reference Manual (Section 5) 5.7.43FarmSize This optional parameter allows you to specify how many server instances to create in a server farm. A server farm is a set of identical Radiator servers, all monitoring the same RADIUS sockets.

Re: [RADIATOR] Bugreport: OTP... PAP

2015-09-24 Thread vartiait
Hi, On Thursday, 24 September, 2015 14:09, "Patrick Honing" said: > > Mon Sep 14 14:15:47 2015: ERR: Could not load EAP module Radius::EAP_: Can't > locate Radius/EAP_.pm in @INC (@INC contains: . > /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi >

Re: [RADIATOR] Use FarmSize parameter

2015-09-24 Thread Hugh Irvine
Hi Antonio - I would need to see your configuration file(s) before making suggestions. If you send copies to me directly I will take a look. regards Hugh > On 24 Sep 2015, at 18:10, António Mendes > wrote: > > Hi Hugh, thanks for your answer. > > The