Date: Sat, 12 Nov 2016 12:38:43 +0100 From: "John W. Kitz" <John.Kitz@xs4all.nl> To: <freebsd-arm@freebsd.org> Subject: Re: How to change MAC address on RPI-B? Message-ID: <001301d23cd9$5775bf70$06613e50$@Kitz@xs4all.nl>
next in thread | raw e-mail | index | archive | help
Reiner, I was again looking at one of the first posts in the thread in which you wrote: "I've tried it this way in /etc/start_if.ue0: ifconfig ue0 down delete ifconfig ue0 promisc ifconfig ue0 ether 00:FF:CC:00:11:11 But it's only possible to do it in promicous mode of the device." In the man pages for ifconfig the parameter 'down' is explained as follows: "Mark an interface ``down''. When an interface is marked ``down'', the system will not attempt to transmit messages through that interface. If possible, the interface will be reset to disable reception as well. This action does not automatically disable routes using the interface." So based on the information supplied it would seem logical that "there is no more network connection after applying these settings." as you mentioned. Looking further down the man pages you'll notice the parameter "up" to "Mark an interface ``up''. This may be used to enable an interface after an ``ifconfig down''. It happens automatically when setting the first address on an interface. If the interface was reset when previously marked down, the hardware will be re-initialized." Hence my question shouldn't you also use "ifconfig ue0 up" at the end in the example you supplied (see above). Also you are referring to the bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168268 The method stated in this bug report to reproduce the issue is: "How-To-Repeat: /etc/rc.conf ifconfig_re0="inet 192.168.0.2/24" ifconfig_re0="inet 192.168.0.2/24" ifconfig_re0_alias0="ether 00:02:1a:2b:3c:4d" I don't know if the operating system interprets "alias" in "ifconfig_re0_alias0" as per the man pages of ifconfig or if it just considers it to be a label, but if it is being interpreted as per the man pages I'd imagine the operating system to expect the parameter to contain an IP address intended to serve as secondary IP address for the interface, rather than a MAC address. Did you try this command-by-command through the CLI and have the output of that? Jk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001301d23cd9$5775bf70$06613e50$>