From owner-freebsd-arm@freebsd.org Thu Nov 10 10:12:16 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F36A9C396F1 for ; Thu, 10 Nov 2016 10:12:16 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb1-smtp-cloud2.xs4all.net (lb1-smtp-cloud2.xs4all.net [194.109.24.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FE5D32C for ; Thu, 10 Nov 2016 10:12:16 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id 6AAy1u00D4VixDu01AB3uz; Thu, 10 Nov 2016 11:11:03 +0100 Reply-To: From: "John W. Kitz" To: References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> <20161110065105.77a19e3b@X220.alogt.com> In-Reply-To: <20161110065105.77a19e3b@X220.alogt.com> Subject: How to change MAC address on RPI-B? Date: Thu, 10 Nov 2016 11:11:02 +0100 Message-ID: <000c01d23b3a$c06e1ef0$414a5cd0$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI628oYuEg4+V6mRT2JRNa2s4YREQAXbvkQ Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 10:12:17 -0000 Erich, > To the best of my recollection at the time there was no need > whatsoever to configure these NICs into promiscuous mode, which in you need this for fault-tolerant computing. A machine or a device with a known goes down, the failure will be detected and another device or machine is configured to take over the other's task by also taking over the other's MAC address. The communication partners will only a delay but not a failure. JKi: I'm curious, would, in your experience, the impact of any delay incurred by tinkering with addresses at both layer-3 AND layer-2 in a failover situation be less in comparison to any delay incurred when tinkering with the addresses at layer-3 ONLY and leave the recovery of addressing issues at layer-2 to the relevant protocols? Jk.