From owner-freebsd-bugs@FreeBSD.ORG Mon Jul 30 03:10:15 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC4CD106566C for ; Mon, 30 Jul 2012 03:10:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D69E08FC08 for ; Mon, 30 Jul 2012 03:10:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6U3AFZm022208 for ; Mon, 30 Jul 2012 03:10:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6U3AFkA022207; Mon, 30 Jul 2012 03:10:15 GMT (envelope-from gnats) Date: Mon, 30 Jul 2012 03:10:15 GMT Message-Id: <201207300310.q6U3AFkA022207@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Rashid N. Achilov" Cc: Subject: Re: kern/159103: ping local address on box shows source address 0.0.0.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Rashid N. Achilov" List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 03:10:16 -0000 The following reply was made to PR kern/159103; it has been noted by GNATS. From: "Rashid N. Achilov" To: Robert Blayzor Cc: bug-followup@freebsd.org Subject: Re: kern/159103: ping local address on box shows source address 0.0.0.0 Date: Mon, 30 Jul 2012 09:51:47 +0700 On Saturday 28 July 2012, Robert Blayzor wrote: > Running into this bug on 9.0 diskless boot clients. Cannot ping primary IP address of the NIC the server boots from, source address observed via TCP dump is 0.0.0.0, same as initial PR report. > > Any status on a fix/update for this? I do not know nothing about updates. I had have detected a *workaround* - when lo0 is FIRST interface name in network_interfaces or missed in it (this way it will init by default) - bug does not occured. When it is non-first in network_interfaces - bug occured. But this is only *workaround*, this bug need real fix. -- With Best Regards. Rashid N. Achilov (RNA1-RIPE), JID: citycat4@jabber.infos.ru OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] askd.ru PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A