From owner-freebsd-net@freebsd.org  Mon Mar 19 11:31:01 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 C8819F67A65
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon, 19 Mar 2018 11:31:01 +0000 (UTC)
 (envelope-from sthaug@nethelp.no)
Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1])
 by mx1.freebsd.org (Postfix) with ESMTP id 62DB46AEEF
 for <freebsd-net@freebsd.org>; Mon, 19 Mar 2018 11:31:01 +0000 (UTC)
 (envelope-from sthaug@nethelp.no)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1])
 by bizet.nethelp.no (Postfix) with ESMTP id D1596E6047;
 Mon, 19 Mar 2018 12:30:58 +0100 (CET)
Date: Mon, 19 Mar 2018 12:30:58 +0100 (CET)
Message-Id: <20180319.123058.74660594.sthaug@nethelp.no>
To: Alexander V. Chernikov <melifaro@ipfw.ru>
Cc: freebsd-net@freebsd.org
Subject: Re: Does FreeBSD do proactive ARP refresh?
From: sthaug@nethelp.no
In-Reply-To: <14964521521306770@web10o.yandex.ru>
References: <20180316.122720.71152047.sthaug@nethelp.no>
 <20180316.124748.104098359.sthaug@nethelp.no>
 <14964521521306770@web10o.yandex.ru>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
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: Mon, 19 Mar 2018 11:31:02 -0000

> >> =A0And thank you for that suggestion! The packet loss during ARP r=
efresh
> >> =A0(of the destination address connected to the output interface) =
does
> >> =A0*not* happen when the box is forwarding! It only happens with l=
ocally
> >> =A0generated traffic.
> Should be fixed by r331098.

I can confirm that 12.0-CURRENT with the r331098 updates fixes this
problem for me for locally generated traffic. The ARP entry seems to
be refreshed around 4 seconds before expiry, and there is no packet
loss.

Transit traffic (non locally generated) also works as before, the ARP
entry is refreshed before expiry and there is no packet loss.

Thanks for the quick fix! Now waiting for the MFC :-)

Steinar Haug, Nethelp consulting, sthaug@nethelp.no