From owner-freebsd-arm@freebsd.org Wed Nov 9 11:37:11 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 4BCBDC38879 for ; Wed, 9 Nov 2016 11:37:11 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (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 DB12D9BB for ; Wed, 9 Nov 2016 11:37:10 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud6.xs4all.net with ESMTP id 5nbu1u00P4VixDu01nbwNX; Wed, 09 Nov 2016 12:35:56 +0100 Reply-To: From: "John W. Kitz" To: Subject: How to change MAC address on RPI-B? Date: Wed, 9 Nov 2016 12:35:56 +0100 Message-ID: <005701d23a7d$71400630$53c01290$@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: AdI6fW+teEMgsnQnQtCJaL6ZKd6lfg== 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: Wed, 09 Nov 2016 11:37:11 -0000 Hi, I saw a couple of emails whizz by, which discussed how to override the burned in MAC address (BIA) on an RPI-B. First off I'm not familiar with the use or configuration of either a Pi or FreeBSD, but to me it looked like in the emails a dependency between two techniques, i.e. overriding the BIA of a NIC and configuring a NIC into promiscuous mode, was made while such a dependency does not or at least, to the best of my knowledge, should not exist. I used, what in IBM lingo is referred to as a locally administered MAC addresses, numerous times predominantly in the nineties of the previous century in datacenter environments using equipment from big blue or its plug compatible competitors, while such equipment exclusively used IBM's Systems Network Architecture (SNA), i.e. non TCP/IP, protocols. To the best of my recollection at the time there was no need whatsoever to configure these NICs into promiscuous mode, which in itself is needed to have a NIC consider frames that aren't destined for the NIC's BIA address as if they were, so I doubt that such a need exists today. I hope this helps, regards, Jk.