From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Mar 4 12:40:02 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1B69498 for ; Mon, 4 Mar 2013 12:40:02 +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 E780F166F for ; Mon, 4 Mar 2013 12:40: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 r24Ce1H6058800 for ; Mon, 4 Mar 2013 12:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r24Ce1I4058799; Mon, 4 Mar 2013 12:40:01 GMT (envelope-from gnats) Date: Mon, 4 Mar 2013 12:40:01 GMT Message-Id: <201303041240.r24Ce1I4058799@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Jason Harris Subject: Re: ports/176439: net/fping: Possible Fping incompatibility with FreeBSD X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Jason Harris List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2013 12:40:02 -0000 The following reply was made to PR ports/176439; it has been noted by GNATS. From: Jason Harris To: bug-followup@FreeBSD.org Cc: Raynaud Alexandre , Jason Harris Subject: Re: ports/176439: net/fping: Possible Fping incompatibility with FreeBSD Date: Mon, 4 Mar 2013 08:33:43 -0400 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable OK, using the CORRECT subnet, I can reproduce it: %fping 10.0.1.99 ; sudo arp -d 10.0.1.99 ; fping 10.0.1.99 ; fping 10.0.1= =2E99 %arp 10.0.1.99 ? (10.0.1.99) at (incomplete) on rl0 expired [ethernet] The difference is if the unreachable IP is in the arp cache when fping star= ts. Note that ping does the same thing: %ping 10.0.1.99 ; sudo arp -d 10.0.1.99 ; ping 10.0.1.99 ; ping 10.0.1.99 (and you have to hit ^C to stop every ping process). It looks like adding -c is a way to get fping to give up sooner: %fping 10.0.1.99 ; sudo arp -d 10.0.1.99 ; fping 10.0.1.99 ; fping -c 5 1= 0.0.1.99 10.0.1.99 is unreachable 10.0.1.99 (10.0.1.99) deleted 10.0.1.99 is unreachable 10.0.1.99 : xmt/rcv/%loss =3D 5/0/100% The OP (Raynaud Alexandre) says this causes problems for zabbix, but only o= n FreeBSD. OP: Is it one or both of ports/net-mgmt/zabbix{,2}-server? [Note: Reply = directly to this message, leaving the subject line and bug-followup@FreeBSD.org inta= ct, to update this PR.] Thanks. --=20 Jason Harris | PGP: This _is_ PGP-signed, isn't it? jharris@widomaker.com _|_ Got photons? (TM), (C) 2004 --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iJ0EARECAF0FAlE0lKdWGGh0dHA6Ly9rZXlzZXJ2ZXIua2pzbC5jb206MTEzNzEv cGtzL2xvb2t1cD9vcD1nZXQmc2VhcmNoPTB4RDM5REEwRTMmd2VoYXZleW91bm93 PXRydWUACgkQSypIl9OdoOOTkgCeOjPt+wsYhtsjRQ4S653Mo2b7oVsAn1f6bbAE cBA9TQ5Bh3NsOtKV/oSC =9ab3 -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g--