From owner-freebsd-net@freebsd.org Sun Mar 18 09:21:12 2018 Return-Path: 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 69BCAF67E8C for ; Sun, 18 Mar 2018 09:21:12 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward105j.mail.yandex.net (forward105j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7566874C7 for ; Sun, 18 Mar 2018 09:21:11 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mxback5g.mail.yandex.net (mxback5g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:166]) by forward105j.mail.yandex.net (Yandex) with ESMTP id 1EA211816AA; Sun, 18 Mar 2018 12:21:09 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback5g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id qpp1Z1cnUS-L7f8WiPE; Sun, 18 Mar 2018 12:21:07 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1521364867; bh=/iH+Q6Kn6saW9qtOLegSQh54vxb7fNZuHebeSxNpEQc=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date; b=ZQDNjacs827yDEjkEi8G+vgaTTJm8z4WJu+vRhS9pPVQ2+smbToWHnxof52GsjG0t U0iVxh/wjvDRjpGfhLuEGhXlgkeNsJv+kEID8y15gdPxLhWzFSc9hXV8iGvbcnRpEt GKXt/mE/OkU1s51Gd6dRDmefZlNuDNa2x006l1Q0= Authentication-Results: mxback5g.mail.yandex.net; dkim=pass header.i=@ipfw.ru Received: by web33j.yandex.ru with HTTP; Sun, 18 Mar 2018 12:21:07 +0300 From: Alexander V. Chernikov To: Rodney W. Grimes Cc: "freebsd-net@freebsd.org" , "sthaug@nethelp.no" In-Reply-To: <201803180028.w2I0S96f004589@pdx.rh.CN85.dnsmgr.net> References: <7275711521311778@web56g.yandex.ru> <201803180028.w2I0S96f004589@pdx.rh.CN85.dnsmgr.net> Subject: Re: Does FreeBSD do proactive ARP refresh? MIME-Version: 1.0 Message-Id: <3023141521364867@web33j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 18 Mar 2018 12:21:07 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 09:21:12 -0000 18.03.2018, 03:31, "Rodney W. Grimes" : > [ Charset UTF-8 unsupported, converting... ] >>  17.03.2018, 21:23, "Rodney W. Grimes" : >>  >> ?16.03.2018, 14:50, "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 :-). IIRC it was not merged to stable/10. > > Do you plan to MFC your fix? Yes, I do :-) > > -- > Rod Grimes rgrimes@freebsd.org > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"