From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A360BC433DB for ; Tue, 5 Jan 2021 02:52:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 687A022582 for ; Tue, 5 Jan 2021 02:52:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727986AbhAECwK (ORCPT ); Mon, 4 Jan 2021 21:52:10 -0500 Received: from youngberry.canonical.com ([91.189.89.112]:39153 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726599AbhAECwK (ORCPT ); Mon, 4 Jan 2021 21:52:10 -0500 Received: from 50-125-80-157.hllk.wa.frontiernet.net ([50.125.80.157] helo=famine.localdomain) by youngberry.canonical.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1kwcRT-0005VP-UF; Tue, 05 Jan 2021 02:51:28 +0000 Received: by famine.localdomain (Postfix, from userid 1000) id E655161DDA; Mon, 4 Jan 2021 18:51:25 -0800 (PST) Received: from famine (localhost [127.0.0.1]) by famine.localdomain (Postfix) with ESMTP id DE922A0409; Mon, 4 Jan 2021 18:51:25 -0800 (PST) From: Jay Vosburgh To: "Finer, Howard" cc: "andy@greyhouse.net" , "vfalico@gmail.com" , "netdev@vger.kernel.org" Subject: Re: bonding driver issue when configured for active/backup and using ARP monitoring In-reply-to: References: <14769.1607114585@famine> Comments: In-reply-to "Finer, Howard" message dated "Mon, 04 Jan 2021 23:08:38 +0000." X-Mailer: MH-E 8.6+git; nmh 1.6; GNU Emacs 27.0.50 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9067.1609815085.1@famine> Date: Mon, 04 Jan 2021 18:51:25 -0800 Message-ID: <9069.1609815085@famine> Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Finer, Howard wrote: >Please advise if there is any update here, and if not how we can go about >getting an update to the driver to rectify the issue. As it happens, I've been looking at this today, and have a couple of questions about your configuration: - Is there an IP address on the same subnet as the arp_ip_target configured directly on the bond, or on a VLAN logically above the bond? - Is the "arp_ip_target" address reachable via an interface other than the bond (or VLAN above it)? This can be checked via "ip route get [arp_ip_target]", i.e., if the target address for bond0 is 1.2.3.4, the command "ip route get 1.2.3.4" will return something like 1.2.3.4 dev bond0 src [...] If an interface other than bond0 (or a VLAN above it) is listed, then there's a path to the arp_ip_target that doesn't go through the bond. The ARP monitor logic can only handle a limited set of configurations, so if your configuration is outside of that it can misbehave in some ways. -J --- -Jay Vosburgh, jay.vosburgh@canonical.com