From owner-freebsd-net@freebsd.org  Sat Aug 25 10:17:04 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 2FEC61085565
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sat, 25 Aug 2018 10:17:04 +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 C079A9245C
 for <freebsd-net@freebsd.org>; Sat, 25 Aug 2018 10:17:03 +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 983C1E604A;
 Sat, 25 Aug 2018 12:17:01 +0200 (CEST)
Date: Sat, 25 Aug 2018 12:17:01 +0200 (CEST)
Message-Id: <20180825.121701.146601904.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: <20180706.002623.74678174.sthaug@nethelp.no>
References: <14964521521306770@web10o.yandex.ru>
 <20180319.123058.74660594.sthaug@nethelp.no>
 <20180706.002623.74678174.sthaug@nethelp.no>
X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO)
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.27
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: Sat, 25 Aug 2018 10:17:04 -0000

>> > >> =A0And thank you for that suggestion! The packet loss during AR=
P refresh
>> > >> =A0(of the destination address connected to the output interfac=
e) does
>> > >> =A0*not* happen when the box is forwarding! It only happens wit=
h locally
>> > >> =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 AR=
P
>> entry is refreshed before expiry and there is no packet loss.
>> =

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

> Looks like the r331098 fix hasn't been MFCed. With 11.2 released,
> could we have MFC of r331098, please?

I see that r331098 has been MFC'ed. Thank you!

Steinar Haug, Nethelp consulting, sthaug@nethelp.no