All, When trying to use the "radauth" tool from nagios to monitor freeradius, I get the following in the freeradius log: Error: WARNING: Malformed RADIUS packet from host ... too long (length 18432 > maximum 4096) radtest seems to be ok. has anyone else experienced this or knows what is wrong?
Mike wrote:
All, When trying to use the "radauth" tool from nagios to monitor freeradius, I get the following in the freeradius log:
Error: WARNING: Malformed RADIUS packet from host ... too long (length 18432 > maximum 4096)
radtest seems to be ok. has anyone else experienced this or knows what is wrong? - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
G'day Mike, Fire up wireshark or tcpdump and have a look what's actually in the packets. -- James Wakefield, Unix Administrator, Information Technology Services Division Deakin University, Geelong, Victoria 3217 Australia. Phone: 03 5227 8690 International: +61 3 5227 8690 Fax: 03 5227 8866 International: +61 3 5227 8866 E-mail: james.wakefield@deakin.edu.au Website: http://www.deakin.edu.au
On Wed, 17 Jan 2007, Mike wrote: |->All, |->When trying to use the "radauth" tool from nagios to monitor |->freeradius, I get the following in the freeradius log: |-> |->Error: WARNING: Malformed RADIUS packet from host ... too long (length |->18432 > maximum 4096) |-> |->radtest seems to be ok. has anyone else experienced this or knows |->what is wrong? I know what some monitoring tool I used a while ago (whats up Gold I think) I had to add the Ip of the whatsup server as a NAS to the allowed list with the shared secret to monitor an old livingston radius server. I have not tried with my Freeradius box yet, but I think I might just to see. The FR is not in production as of yet so I'm not worried about it.
Mike wrote:
All, When trying to use the "radauth" tool from nagios to monitor freeradius, I get the following in the freeradius log:
Error: WARNING: Malformed RADIUS packet from host ... too long (length 18432 > maximum 4096)
radtest seems to be ok. has anyone else experienced this or knows what is wrong?
I haven't seen it. I note that 18432 is hex 0x7200. I suspect that the NAGIOS people missed a 'htons()' somewhere, and the field should be 0x0072. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (4)
-
Alan DeKok -
James Wakefield -
Keith Woodworth -
Mike