From owner-freebsd-arm@freebsd.org Fri Nov 25 19:56:15 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 566DBC55669 for ; Fri, 25 Nov 2016 19:56:15 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud2.xs4all.net (lb3-smtp-cloud2.xs4all.net [194.109.24.29]) (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 F353C397 for ; Fri, 25 Nov 2016 19:56:14 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id CKw31u0084VixDu01Kw5zr; Fri, 25 Nov 2016 20:56:05 +0100 Reply-To: From: "John W. Kitz" To: "'freebsd-arm'" References: <001701d245ce$e64e33f0$b2ea9bd0$@Kitz@xs4all.nl> <454137dc-30f7-cd33-6c75-0cc3045090dd@t-online.de> In-Reply-To: <454137dc-30f7-cd33-6c75-0cc3045090dd@t-online.de> Subject: RE: How to change MAC address on RPI-B? Date: Fri, 25 Nov 2016 20:56:04 +0100 Message-ID: <002801d24755$f9017420$eb045c60$@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: AdJHMT44SOvRXlvkTk63Nm1fBL58QwAILS5Q 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: Fri, 25 Nov 2016 19:56:15 -0000 Reiner, So when doing so the locally administered MAC address is passed on from uEnv.txt to the O/S during boot and is then used to override the globally unique MAC address or does the O/S check both the information found in its configuration files and what is configured in uEnv.txt before configuring and activating the network interface(s)? Makes me wonder which of the two (i.e. locally administered through uEnv.txt or locally administered through the O/S) takes precedence. In addition this might affect configuration decisions when one would want to configure a device for net booting (at least when browsing through what can be configured by means of uEnv.txt I believe that was one of the options I saw) through uEnv.txt? Jk.