Date: Tue, 5 Jul 2022 17:04:08 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Ronald Klop <ronald-lists@klop.ws>, Karl Denninger <karl@denninger.net>, freebsd-arm@freebsd.org Subject: Re: duplicate MAC - Re: 13.1R problems on Pi3 Message-ID: <6E65607C-C8DF-445A-A000-5553D9BDBC70@yahoo.com> In-Reply-To: <20220705233440.GA9228@www.zefox.net> References: <20220704003639.GA1165@www.zefox.net> <8820A9EC-A25E-4D0A-9F8F-52114E58B66F@yahoo.com> <6c377413-9430-54d2-3f92-1215055ca30a@denninger.net> <20220704152834.GA1771@www.zefox.net> <7ce87eef-ded5-8b00-3f11-14407b8af78d@denninger.net> <20220704182526.GB1771@www.zefox.net> <212C86C0-17DB-45F5-A59D-8BDC1932378E@yahoo.com> <1645012198.135.1657014956867@localhost> <6B24FF55-7010-40ED-B32B-AA46F0E7ED80@yahoo.com> <20220705233440.GA9228@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Jul-5, at 16:34, bob prohaska <fbsd@www.zefox.net> wrote: > On Tue, Jul 05, 2022 at 07:02:18AM -0700, Mark Millard wrote: >>=20 >>> So for you I would guess: >>>=20 >>> ifconfig_ue0=3D"ether ??:??:??:??:??:?? inet 50.1.20.28 netmask = 255.255.255.0" >>>=20 >>>=20 >=20 > I tried a few variants, all produced a dead connection.=20 >=20 > Using one like you suggested: >=20 > # ethernet address increased by 1 in the last digit > ifconfig ue0=3D"ether b8:27:eb:71:46:4f inet 50.1.20.28 netmask = 255.255.255.0" >=20 > produced a flood of errors during boot: > ifconfig: interface ue0=3Dether b8:27:eb:71:46:4f inet 50.1.20.28 = netmask 255.255.255.0 does not exist >=20 > There was clearly no network connectivity, but the serial console > remained responsive. The host sharing the same MAC address exhibited > no connectivity problems.=20 >=20 >=20 > Another suggestion was found in an old forum post, assigning the IP > in the usual fashion but adding an alias: >=20 > ifconfig_ue0=3D"inet 50.1.20.28 netmask 255.255.255.0"=20 > ifconfig_ue0_alias0=3D"link b8:27:eb:71:46:4f" > (trading ether for link had no effect) >=20 > resulted in the gateway (and everything else) being unreachable.=20 I also later sent notes about using the RPi* firmware's config.txt to assign a MAC address to an RPi* . Have you tried that? It is not in the main RPi* documentation but RPi* engineers talk about it in the forums. QUOTE I've found references to an undocumented control in config.txt : force_mac_address=3D??:??:??:??:??:?? See, for example, https://forums.raspberrypi.com/viewtopic.php?t=3D327562 Apparently, force_mac_address controls what value shows up in the device tree for what the ethernet0 alias points to in the device tree. Note that having a odd .dtb file could lead to force_mac_address not working. (The RPi* firmware reads the file and then makes a device tree with some modifications applied.) END QUOTE =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6E65607C-C8DF-445A-A000-5553D9BDBC70>