From owner-freebsd-bugs@FreeBSD.ORG Tue Feb 26 13:20:01 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4C15E762 for ; Tue, 26 Feb 2013 13:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 332AE249 for ; Tue, 26 Feb 2013 13:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1QDK16l080520 for ; Tue, 26 Feb 2013 13:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1QDK1Gg080519; Tue, 26 Feb 2013 13:20:01 GMT (envelope-from gnats) Resent-Date: Tue, 26 Feb 2013 13:20:01 GMT Resent-Message-Id: <201302261320.r1QDK1Gg080519@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Alexandre RAYNAUD Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 95234731 for ; Tue, 26 Feb 2013 13:18:36 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 823E822F for ; Tue, 26 Feb 2013 13:18:36 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.5/8.14.5) with ESMTP id r1QDIZRJ064611 for ; Tue, 26 Feb 2013 13:18:35 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.5/8.14.5/Submit) id r1QDIZVC064610; Tue, 26 Feb 2013 13:18:35 GMT (envelope-from nobody) Message-Id: <201302261318.r1QDIZVC064610@red.freebsd.org> Date: Tue, 26 Feb 2013 13:18:35 GMT From: Alexandre RAYNAUD To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: misc/176439: Possible Fping incompatibility with FreeBSD X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2013 13:20:01 -0000 >Number: 176439 >Category: misc >Synopsis: Possible Fping incompatibility with FreeBSD >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 26 13:20:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Alexandre RAYNAUD >Release: 9.1-RELEASE >Organization: MAIRIE DE SALLANCHES >Environment: FreeBSD zabbix 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: In precise circumstances, Fping 3.4 command gives inconsistent results on FreeBSD OS using either Fping 3.4 FreeBSD port or Fping 3.4 compilled from source. >From a FreeBSD box, using fping command to check an unreachable host_ip's availability located in the same subnet as the FreeBSD Host, fping get stuck at the second try returning many errors ("host_ip error while sending ping: Host is down"). The first try will be ok. If we wait few seconds (maybe 1 minute) between each test, the error doesn't occur. The returned fping error message part "error while sending ping" is comming from fping source (fping.c) at line 1581 the second part of fping error message "Host is down" seems to come from /usr/src/sys/sys/errno.h line 133 (#define EHOSTDOWN 64 /* Host is down */). As consequence of this issue, applications relying on Fping to check host availability cannot be fully trusted. (ps : Using fping with ip located on external/routed network, fping always works normally, without any error) >How-To-Repeat: To repeat the problem : -The FreeBSD box from where we run fping command must have an interface configured with an ip address in the same subnet as the host_ip we want to check the availability. The host_ip we want to check availability MUST BE DOWN. All the tests must be done with THE SAME HOST_IP. Running {fping host_ip} for the first time return : {host_ip is unreachable} which is the expected output. As soon as the firt command finish (important to not wait), running another {fping host_ip} return : { host_ip error while sending ping: Host is down host_ip error while sending ping: Host is down host_ip error while sending ping: Host is down host_ip error while sending ping: Host is down host_ip error while sending ping: Host is down host_ip error while sending ping: Host is down host_ip error while sending ping: Host is down .. } Then pfing will get stuck and if you ctrl-c, it will stops and you will get the normal fping output : {^Chost_ip is unreachable} Remark : if you wait about 1 minute between 2 testS, no error occur. >Fix: Don't know how to fix the problem but it seems to be related with a caching issue. >Release-Note: >Audit-Trail: >Unformatted: