From owner-freebsd-net@freebsd.org  Sun Mar 18 09:39:02 2018
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA930F68B94
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sun, 18 Mar 2018 09:39:02 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5405187FFF
 for <freebsd-net@freebsd.org>; Sun, 18 Mar 2018 09:39:02 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1])
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2I9cv3f006184;
 Sun, 18 Mar 2018 02:38:57 -0700 (PDT)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: (from freebsd-rwg@localhost)
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2I9cvJs006183;
 Sun, 18 Mar 2018 02:38:57 -0700 (PDT) (envelope-from freebsd-rwg)
From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
Message-Id: <201803180938.w2I9cvJs006183@pdx.rh.CN85.dnsmgr.net>
Subject: Re: Does FreeBSD do proactive ARP refresh?
In-Reply-To: <3023141521364867@web33j.yandex.ru>
To: "Alexander V. Chernikov" <melifaro@ipfw.ru>
Date: Sun, 18 Mar 2018 02:38:57 -0700 (PDT)
CC: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>,
 "sthaug@nethelp.no" <sthaug@nethelp.no>
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Mar 2018 09:39:03 -0000

> 18.03.2018, 03:31, "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>:
> >> ?17.03.2018, 21:23, "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>:
> >> ?>> ?16.03.2018, 14:50, "sthaug@nethelp.no" <sthaug@nethelp.no>:
> >> ?>> ?..
> >> ?>> ?>> ?And thank you for that suggestion! The packet loss during ARP refresh
> >> ?>> ?>> ?(of the destination address connected to the output interface) does
> >> ?>> ?>> ?*not* happen when the box is forwarding! It only happens with locally
> >> ?>> ?>> ?generated traffic.
> >> ?>> ?Should be fixed by r331098.
> >> ?>
> >> ?> Thanks for the quick fix, do we know about when this breakage started?
> >> ?I guess it's something like r297225.
> >
> > SO 2 years ago, meaning it effects stable/11,
> > and may of been merged to stable/10?
> Side note: if one has monitoring which does ICMP checks, it will mask the issue because icmp replies don't use route caching.
> Typical story  when the observer changes the state of an observed object :-).

Also perhaps why it has not been reported before, as other side effects
have caused it to be a pretty invisible issue.

> IIRC it was not merged to stable/10.
> >
> > Do you plan to MFC your fix?
> Yes, I do :-)

For some reason the MFC: 2 weeks did not register when I read
the commit.  

-- 
Rod Grimes                                                 rgrimes@freebsd.org