Description of problem: The nagios check-dhcp option does not respect the -s <hostname> option, instead sending the request to 255.255.255.255. Below, the request was made to 10.3.3.1, but the returned results were from 10.2.2.1 and 10.2.2.41, both of which are closer to the nagios client than 10.3.3.1. 10.2.2.54 is the fixed dhcp address of the nagios client. Version-Release number of selected component (if applicable): # /usr/lib/nagios/plugins/check_dhcp -V check_dhcp (nagios-plugins 1.4.3) 1.1 Additional info: # /usr/lib/nagios/plugins/check_dhcp -s 10.3.3.1 -v DHCP socket: 3 Hardware address: 0048546e3569 DHCPDISCOVER to 255.255.255.255 port 67 DHCPDISCOVER XID: 1366388377 (0x51716E99) DHCDISCOVER ciaddr: 0.0.0.0 DHCDISCOVER yiaddr: 0.0.0.0 DHCDISCOVER siaddr: 0.0.0.0 DHCDISCOVER giaddr: 0.0.0.0 send_dhcp_packet result: 548 recv_result_1: 378 recv_result_2: 378 receive_dhcp_packet() result: 378 receive_dhcp_packet() source: 10.2.2.41 Result=OK DHCPOFFER from IP address 10.2.2.41 DHCPOFFER XID: 1366388377 (0x51716E99) DHCPOFFER chaddr: 0048546E3569 DHCPOFFER ciaddr: 0.0.0.0 DHCPOFFER yiaddr: 10.2.2.54 DHCPOFFER siaddr: 0.0.0.0 DHCPOFFER giaddr: 0.0.0.0 Option: 53 (0x01) Option: 54 (0x04) Option: 51 (0x04) Option: 1 (0x04) Option: 3 (0x04) Option: 6 (0x10) Option: 12 (0x18) Option: 9 (0x04) Option: 58 (0x04) Option: 59 (0x04) Lease Time: 3600 seconds Renewal Time: 1800 seconds Rebinding Time: 3150 seconds Added offer from server @ 10.2.2.41 of IP address 10.2.2.54 recv_result_1: 378 recv_result_2: 378 receive_dhcp_packet() result: 378 receive_dhcp_packet() source: 10.2.2.1 Result=OK DHCPOFFER from IP address 10.2.2.1 DHCPOFFER XID: 1366388377 (0x51716E99) DHCPOFFER chaddr: 0048546E3569 DHCPOFFER ciaddr: 0.0.0.0 DHCPOFFER yiaddr: 10.2.2.54 DHCPOFFER siaddr: 0.0.0.0 DHCPOFFER giaddr: 0.0.0.0 Option: 53 (0x01) Option: 54 (0x04) Option: 51 (0x04) Option: 1 (0x04) Option: 3 (0x04) Option: 6 (0x10) Option: 12 (0x18) Option: 9 (0x04) Option: 58 (0x04) Option: 59 (0x04) Lease Time: 3600 seconds Renewal Time: 1800 seconds Rebinding Time: 3150 seconds Added offer from server @ 10.2.2.1 of IP address 10.2.2.54 No (more) data received Result=ERROR Total responses seen on the wire: 2 Valid responses for this machine: 2 DHCP problem: Received 2 DHCPOFFER(s), 0 of 1 requested servers responded, max lease time = 3600 sec.
What is it you're expecting to get?
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.