check_dhcp -s uses wrong ip-address if the dhcp-server answers with a next-server ip set which is =! the dhcp server ip.
this bug seems to be fixed upstream, see http://sourceforge.net/tracker/?func=detail&atid=397597&aid=3503921&group_id=29880
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)
check_dhcp -s uses wrong ip-address if the dhcp-server answers with a next-server ip set which is =! the dhcp server ip.
this bug seems to be fixed upstream, see http:// sourceforge. net/tracker/ ?func=detail& atid=397597& aid=3503921& group_id= 29880
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)