check_dhcp seems not working

[jmoseley at corp.xanadoo.com]

Holger Weiss <holger at CIS.FU-Berlin.DE>  wrote:

* jmoseley at corp.xanadoo.com [2009-01-15 14:59]:
>> Holger Weiss <holger at CIS.FU-Berlin.DE>  wrote:
>> * jmoseley at corp.xanadoo.com [2009-01-15 13:06]:
>> >> 2. Have a DHCP relay statement on the router's interface your Nagios
server
>> >> connects to so it knows to which server to relay the DHCP request to
>>
>> >For such a setup, step (2) isn't necessary, as check_dhcp will mimic a
>> >DHCP relay if the "--unicast" option is specified.
>>
>> What I meant was you'd have to have an ip helper-address configured.

>But that's precisely what you don't need if you use check_dhcp's
>"--unicast" option :-)  If you configure an "ip helper-address" (as
>Cisco calls it), the router will relay local DHCP broadcast packets to
>the specified remote DHCP server.  "check_dhcp --unicast" creates the
>same sort of unicast packets such a relay would generate.

OK, I've got you now.

Back to the orginal topic.  Christian, another thing to check on the Nagios
server is if you have SELinux enabled.  That could definitely cause
problems with plugins that are SUID root.  If SELinux is enabled, disable
it and try the check_dhcp plugin again.

James



------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null