[Bug 1119145] Re: check_dhcp -s <hostaddress> doesn't work if dhcp-server answers with different next-server ip

[abma]

Imo its this category:
"Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel). " (thanks for pointing to the patch)


** Description changed:

- check_dhcp -s uses wrong ip-address if the dhcp-server answers with a
- next-server ip set which is =! the dhcp server ip.
+ [Impact]
+ specific windows dhcp-servers can't be checked, only if a dhcp-server exists in a subnet. thats bad because faulty dhcp-servers will be detected as fine.
  
- this bug seems to be fixed upstream, see
- http://sourceforge.net/tracker/?func=detail&atid=397597&aid=3503921&group_id=29880
+ [Test Case]
+ setup a windows 2008 r2 dhcp server with the option boot-server set to an ip != dhcp-server and run check_dhcp -s <server ip> against it. it will receive a response but detect it as invalid because it uses the ip from set for the boot server (next-server).
  
- 
- this currently makes check_dhcp -s <ip> unusable for us, without -s it works fine (but is bad as it could get a response from a failed router for example)
+ [Regression Potential]
+ low, as only check_dhcp could be broken by the patch.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1119145

Title:
  check_dhcp -s <hostaddress> doesn't work if dhcp-server answers with
  different next-server ip

To manage notifications about this bug go to:
https://bugs.launchpad.net/nagios-plugins/+bug/1119145/+subscriptions