Hello list -
I've been trying to integrate the Radiator monitoring interface with Nagios
and MRTG, specifically to graph the request rate and average response times
on an ongoing basis.
To do this, I'm using Net::Radiator::Monitor to query the Monitor port with
StatisticsOnly and LogMicrose
We're currently chasing down some wireless issues which, at least in
some cases, manifest as the EAP-PEAP or EAP-TTLS conversation being
aborted in the middle; i.e. after a couple of successful back and
forths, Radiator sends an EAP Request in a RADIUS challenge, and we
never receive a subseque
On 08/24/2015 02:24 AM, Steve Shipway wrote:
> n The ‘Average response time’ metric does not appear to be what it says
> – it is continually increasing, and is possibly total time spent
> handling responses? I cannot find any detailed documentation covering this.
This is a moving average over t
log the
Called-Station-Id and the NAS/Client IP (%c).
And of course it would be ideal if I could eventually do this with a Hook
instead of custom modifications to the actual Radiator code. :)
Thanks,
David
diff -ru radiator-20150716/radiator/lib/perl5/Radius/Context.pm
radiator-20150826.dmrz
We have a Windows 7 client that in certain locations around campus periodically
gets booted off wireless and prompts the user to re-enter his credentials.
Each time this happens, my normal RADIUS logs show:
2015-08-26T21:57:09.002570-05:00 radius1.cites.illinois.edu
radius.auth2[36852]: [wirele
