Nagios Check_ Radius Auth Error

how Nagios can help your organization. Register Now Contact Us Phone: 1-888-NAGIOS-1 Email: sales@nagios.com Login Username Password Remember Me Create an account Forgot your username? Forgot nagios check_radius your password? RSS Feeds New Listings Updated Listings Directory Quicklinks Home All

Nagios Radius Authentication

Categories Add Listing New Listings Recently Updated Listings Most Favoured Listings Featured Listing Most Popular Listings Most freeradius status server Rated Listings Top Rated Listings Most Reviewed Listings check radius adv Submit reviewRecommendPrintClaimRating3 votes Favoured: 0 OwnernagiosexchangeHits97907Files:FileDescriptionsamplefile.txtA sample attributes file check_radius_adv_2006_08_23.tar.gzThe plugin This plugin is based on the check_radius (radauth.c by Matt Miller). Basicly it will check authentication against radius server.Advanced features The advanced featetures compared to original check_radius are: * radius attributes used for the authentication can be defined. * command paramater for which radius reply ends in an ok state * command parameter to check the Reply-Msg from the radius server Installation Just unpack the file. And afterwards use ./configure and make Usage check_radius_adv Usage: # ./check_radius_adv OPTIONS... OPTIONS -v verbose (output with verification) -u [username] cleartext username -p [password] cleartext password -s [shared secret] shared secret for RADIUS server -r [radius server] radius server to auth -c [radius port] radius server port (default: 1812) -t [auth timeout] interval to wait until auth timeout in seconds (default: 30 sec.) -a [attributes] filename of the attributes file (see samplefile) -o [ok state] auth reply code which will return ok state (default: 2 = accepted) -e [error code] plugin error-code in case reply code differs (default: 2 = critical) -m [replymsg] expected replymsg (type=18) (default: "") -h this menu Additional Attributes You can add Strings, Integers, Addresses and Times. But please, check the attached samplefile Credits This plugin was kindly sponsored by T-Mobile Changelog * **2006-03-22** Parameters with hexvalues (e.g. /x3B for a semicolon) as patterns are translated into their ascii characters. //That is why / has also be escaped as ``//``//. * failure was not recogniz

X 10.8 Server, I decided I wanted a way to monitor the customers FreeRADIUS server to ensure it's up and running, and processing requests. Given that we use GroundWork for monitoring, I decided to write a bash script that verifies the process is running, and that it's processing authentication requests. Queue code! Take a look at the code on GitHub ps aux -o tty | grep "/usr/sbin/radius" Initially, we do a quick process check to make sure FreeRADIUS is even running. If it's not running, we exit with a critical warning (there's no point proceeding any further in the script). This script was written for OS X 10.8 Mountain Lion Server, so https://exchange.nagios.org/directory/Plugins/Network-Protocols/RADIUS/check-radius-adv/details adjust the path to radius to your liking. OK, so we've verified the radiusd process is running, now it's time to try and authenticate using valid login credentials to the FreeRADIUS server (in my case, users in the com.apple.access_radius group). echo "User-Name=,User-Password=,Framed-Protocol=PPP " | radclient -x -r 1 -t 2 localhost:1812 auth testing123 2> /tmp/radius_error Running the command radclient by itself doesn't work, you have to pipe radius authentication attribute/value pairs. We use https://www.yesdevnull.net/2013/10/freeradius-monitoring-with-nagios/ PPP for the Framed-Protocol as we are providing a username and password and using the Point-To-Point Protocol. It's worth taking a look at RFC 2865 for more information regarding RADIUS and user authentication. After authentication and server credentials are supplied, we pass all standard error (stderr) to a temporary log file (stored at /tmp/radius_error) so it doesn't cause the script to produce any unexpected output. I also assign a variable with the contents of that temporary file so we can see what the error was. An incorrect shared secret will throw a stderr, but wrong credentials will just output to stdout. The next part of our script is an if statement that checks what our authentication attempt has returned, then process accordingly. We check if it's successful, wrong shared secret, or wrong authentication details. If there's any other response, I throw a generic error. ./check_radius.sh -u username -p password -h localhost -p 1812 -s sharedsecret To run the script, you enter the code above (this assumes you're running with escalated privileges i.e. sudo -s, otherwise prepend the command with sudo). This should be run on the same server as your FreeRADIUS server, or on an authorised Network Access Server (NAS) client. GroundWork Configuration First off, we need a command that does the actual check. See below for t

plugins are set-up (including conf files for radiusclient) and http://osdir.com/ml/network.nagios.plugins/2005-01/msg00011.html running. My problem is the check_radius plugin. If I launch a check_radius request from the command line, i am getting an "Auth OK". If I run nagios, the same request gets a "Auth Error". I have double checks all nagios check_ my nagios conf files, includind macro def and directory links. I have also checked files ownerchip ... Does any one have a clue ?? Her's sample of my conf files: ==== checkcommands.cfg ==== # 'check_radius-test' command definition define command{ command_name nagios check_ radius check_radius-test command_line $USER1$/check_radius -v -H my_radius_server -F /etc/radiusclient/radiusclient.conf -u my_user_test@my_radius_server -p my_user_test_password -P 1812 } ==== services.cfg ==== define service { use generic-service host_name my_radius_server service_description check_radius is_volatile 0 check_period 24x7 max_check_attempts 3 normal_check_interval 5 retry_check_interval 1 contact_groups admin notification_interval 60 notification_period 24x7 notification_options w,u,c,r check_command check_radius-test } ==== command-plugins.cfg ==== command[check_radius]=/usr/lib/nagios/plugins/check_radius $ARG1$ $ARG2$ $HOSTADDRESS$ 1812 $ARG3$ ==== resources.cfg ==== # Sets $USER1$ to be the path to the plugins $USER1$=/usr/lib/nagios/plugins ==== ls -la /usr/lib/nagios/plugins/ ==== -rwxr-xr-x 1 nagios apache 16883 Apr 26 2004 check_radius ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Nagiosplug-help mailing list Nagiosplug-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxx