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

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Robie Basak (racb):

[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.

[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).

[Regression Potential]
low, as only check_dhcp could be broken by the patch.

** Affects: nagios-plugins
     Importance: Unknown
         Status: Unknown

** Affects: nagios-plugins (Ubuntu)
     Importance: Undecided
         Status: Fix Released

-- 
check_dhcp -s <hostaddress> doesn't work if dhcp-server answers with different next-server ip
https://bugs.launchpad.net/bugs/1119145
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.