Jump to content
  • 1

Opi lite MAC address


Parveke16
 Share

Question

Hello, I liked to have fixed MAC address to my Orange Pi lite.

At the moment, after every boot I have different one.

First of all, is there "real" MAC for this board? If there is, how the see it?

Then what would be correct way to set static MAC, U-boot/Scribt.bin/ifconfig...?

I am running Armbian 5.14 Jessie server.

 

Link to comment
Share on other sites

Recommended Posts

Check forum guidelines to use maximum potential!

  • 0

Maybe there was something missing in 5.14, but in 5.17 the firstrun script is creating the file : /etc/modprobe.d/8189fs.conf, it should looks like :

options 8189fs rtw_initmac=00:e0:4c:f5:16:d8

Since latest prebuilt images are of version 5.14 and firstrun script won't be executed after dist-upgrade, this change doesn't work yet.

Link to comment
Share on other sites

  • 0

 

Maybe there was something missing in 5.14, but in 5.17 the firstrun script is creating the file : /etc/modprobe.d/8189fs.conf, it should looks like :

options 8189fs rtw_initmac=00:e0:4c:f5:16:d8

There is such file, and it looks:

options 8189fs rtw_initmac=43:29:B1:0C:84:1C 

But, it gives address from 00:E0:4C: -range

Link to comment
Share on other sites

  • 0

I'm using Mainline 4.6.2, and this /etc/modprobe.d/8189fs.conf works for me, it keep the same MAC at every reboot.

But I don't know if the same happen in Legacy kernel.

Just checked: this is what happens

/*
 * Description:
 * rtw_check_invalid_mac_address: 
 * This is only used for checking mac address valid or not.
 *
 * Input:
 * adapter: mac_address pointer.
 * check_local_bit: check locally bit or not.
 *
 * Output:
 * _TRUE: The mac address is invalid.
 * _FALSE: The mac address is valid.
 *
 * Auther: Isaac.Li
 */
u8 rtw_check_invalid_mac_address(u8 *mac_addr, u8 check_local_bit)
{
	u8 null_mac_addr[ETH_ALEN] = {0, 0, 0, 0, 0, 0};
	u8 multi_mac_addr[ETH_ALEN] = {0xff, 0xff, 0xff, 0xff, 0xff, 0xff};
	u8 res = _FALSE;

	if (_rtw_memcmp(mac_addr, null_mac_addr, ETH_ALEN)) {
		res = _TRUE;
		goto func_exit;
	}

	if (_rtw_memcmp(mac_addr, multi_mac_addr, ETH_ALEN)) {
		res = _TRUE;
		goto func_exit;
	}

	if (mac_addr[0] & BIT0) {
		res = _TRUE;
		goto func_exit;
	}

	if (check_local_bit == _TRUE) {
		if (mac_addr[0] & BIT1) {
			res = _TRUE;
			goto func_exit;
		}
	}

func_exit:
return res;
}

So in case bits 0 or 1 of first byte of MAC address are set, 8189fs driver won't consider this MAC "valid" and will assign a random one.

And firstrun always sets first byte as 0x43, which is 10000112

 

Edit: Added comments to function code to clarify return value logic.

Link to comment
Share on other sites

  • 0

And firstrun always sets first byte as 0x43, which is 10000112

 

So I added just another bug when adding this to firstun :(

 

The MAC prefix 00:e0:4c is registered for RealTek so should we switch to this in firstrun?

Link to comment
Share on other sites

  • 0

That's explain everything ...

If I remember when I faced the same issue, I've explicitly copied the current MAC into the 8189fs.conf file, so I "fixed" the issue by placing a 00:e0:4c manually.

 

In mainline, it looks like the same code, because in fact, when I commit it, the sources was merged with Hans changes, but origins are common.

 

I see that the random init is using this code :

               *((u32 *)(&mac[2])) = rtw_random32();
               mac[0] = 0x00;
               mac[1] = 0xe0;
               mac[2] = 0x4c;

So, Yes, the firstrun should place the same RealTek prefix.

Link to comment
Share on other sites

  • 0

I'd like to achieve the same as OP, but on a OrangePI PC with mainline kernel and u-boot.

If I set a fix mac address in the /etc/network/interfaces, the board doesn't boot, so I guess there should be another way to do it.

Link to comment
Share on other sites

  • 0

I'm testing on Armbian mainline now

OPi Zero Armbian 5.27.170614

 

need to achieve static mac address per boot in the next 12 hours before 200 OPiZ's get silicone sealed into waterproof containers. so looking into this now...

 

also adding notes for others with same issue who might also be less familiar with the inner workings of armbian and/or linux

 

tried adding the file:
/etc/modprobe.d/8189fs.conf
(note that file didn't exist before)

 

and setting its contents to:
options 8189fs rtw_initmac=00:e0:4c:f5:16:d8

 

but that didn't help (new random MAC address on reboot)

 

theres a file /etc/default/brcm40183 with:

MAC_ADDR=43:29:B1:55:01:01
which doesn't correspond to any of the mac addresses its chosen at boot so far as I know

(also this seems to be cubietrick specific?)

 

also similar in /etc/default/ap6212

 

 

found the lines in /etc/init.d/firstrun:

# set MAC for eth0
  255: 			MACADDR=$(printf 'da:42:ea:%02X:%02X:%02X\n' $[RANDOM%256] $[RANDOM%256] $[RANDOM%256])
  256: 			sed -i "s/^\#[^ tab]\+hwaddress ether/\thwaddress ether $MACADDR/" /etc/network/interfaces
  257  			;;

will investigate here..

 

Link to comment
Share on other sites

  • 0

got some hints from the other thread:

 

 

especially on how best to misuse an internet forum / your life

 

so I keep hearing about 'device tree'

 

looking at the linked code:

https://github.com/megous/linux/blob/orange-pi-4.11/drivers/net/ethernet/allwinner/sun8i-emac.c#L1221-L1226

it looks like if of_get_mac_address fails to get a mac address from of_node then it will assign a random one

so i guess that in order to succeed we need to fix Device Tree?

 

i didn't have this issue on the legacy kernel (but need docker, so need mainline kernel)

any primer notes on Device Tree ?

 

 

Link to comment
Share on other sites

  • 0
52 minutes ago, Elliot Woods said:

it looks like if of_get_mac_address fails to get a mac address from of_node then it will assign a random one

so i guess that in order to succeed we need to fix Device Tree?

MAC address should be set by u-boot first. In order to find network devices it looks for aliases named ethernetX (where X is a number) pointing to the network devices DT nodes. In the source DT an alias looks like this: https://github.com/megous/linux/blob/orange-pi-4.11/arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts#L58

 

Regarding the wireless driver - no idea if it supports a fixed MAC address and what method should be used for it.

Edit: the first OPi Zero uses the XRadio driver, not a Realtek one, and current mainline images don't have this driver at all in the kernel sources due to many issues with it)

 

1 hour ago, Elliot Woods said:

need to achieve static mac address per boot in the next 12 hours before 200 OPiZ's get silicone sealed into waterproof containers. so looking into this now...

If you are using mainline kernel for production and it works good enough for you (even though I would not recommend it, especially for OPi Zero) - okay, fine, but please use apt-mark hold to freeze the kernel, DT and board support packages (or remove /etc/apt/sources.list.d/armbian.list) to minimize the chance of getting a 200 waterproof useless bricks broken by the upgrade.

Link to comment
Share on other sites

  • 0

@zador.blood.stained, I've discovered some thing funny ...

In sun8i-h2-plus-orangepi-zero.dts, there is a comment in the alias section :

/* ethernet0 is the H3 emac, defined in sun8i-h3.dtsi */

But it seems that it is not true any more, neither in sun8i-h3.dtsi or sunxi-h3-h5.dtsi !

So, that is why we lost fix MAC on few boards when we switched from 4.10 to 4.11 ...

 

I will prepare a patch in the following minutes ...

 

Link to comment
Share on other sites

  • 0

Assuming you have "dtc" installed (and keep a backup of the original /boot/dtb/sun8i-h2-plus-orangepi-zero.dtb :

dtc -I dtb -O dts -o sun8i-h2plus-orangepi-zero.dts-4.11.12 /boot/dtb/sun8i-h2-plus-orangepi-zero.dtb

Edit the DTS with "nano sun8i-h2plus-orangepi-zero.dts-4.11.12" and add 'ethernet0 = "/soc/ethernet@1c30000"; ' in the "aliases" section.

Then, recompile the DTB :

dtc -I dts -O dtb -o /boot/dtb/sun8i-h2-plus-orangepi-zero.dtb sun8i-h2plus-orangepi-zero.dts-4.11.12

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...