Zyxel NSA310 wrong MAC address

I have OpenWRT release 19.07.0 installed on a Zyxel NSA310. OpenWRT sets the wrong MAC (00:00:00:00:00:30) address for the ethernet connection. I guess the read address/offset (0xd1475000) for the mtd1 partition (uboot_env) is wrong. Maybe it is caused by the "bad erase blocks" like in this OpenWRT thread for Netgear R6220 / Bugreport FS#1926.
Looking at the mtd1 (uboot_env) binary it shows (dummy MAC to hide my actual MAC address)
at mtd1.bin file address 0x00000280 ethact=egiga0 ethaddr=33:33:33:33:33:33
at mtd1.bin file address 0x00040260 ethaddr=33:33:33:33:33:33

I hope someone with a better understanding of partition/openwrt structure can tell me, if I am on the right track. Any idea what went wrong and how to solve it?

This is a snipped of the kernel log
[ 0.595742] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 0.602148] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 0.606789] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 0.614415] Scanning device for bad blocks
[ 0.622586] Bad eraseblock 42 at 0x000000540000
[ 0.688325] Bad eraseblock 684 at 0x000005580000
[ 0.701793] Bad eraseblock 777 at 0x000006120000
[ 0.713634] Bad eraseblock 853 at 0x000006aa0000
[ 0.734522] 3 fixed-partitions partitions found on MTD device orion_nand
[ 0.741264] Creating 3 MTD partitions on "orion_nand":
[ 0.746427] 0x000000000000-0x0000000c0000 : "uboot"
[ 0.751868] 0x0000000c0000-0x000000140000 : "uboot_env"
[ 0.757592] 0x000000140000-0x000008000000 : "ubi"
...
[ 10.682196] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 10.687849] pci 0000:00:01.0: enabling device (0140 -> 0143)
[ 10.693582] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[ 10.700275] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd1475000, 00:00:00:00:00:30, XID 083000c0 IRQ 36
[ 10.709919] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]

Without knowing how OpenWrt is supposed to read and set that MAC address, I can tell you that 00:00:00:00:00:30 is Kirkwood powerup default.
This is the address which can be used for WOL when the system has had a power failure.

The bad erase blocks are not overlapping uboot_env, so I don't think these have anything to do with it. Does the uboot environment actually contain the MAC address?

Does the uboot environment actually contain the MAC address?

Yes, looking at the mtd1 (uboot_env) binary it shows (dummy MAC to hide my actual MAC address)
at mtd1.bin file address 0x00000280 ethact=egiga0 ethaddr=33:33:33:33:33:33
at mtd1.bin file address 0x00040260 ethaddr=33:33:33:33:33:33

This is very useful to know. So if we setup a startup job to etherwake every 3 minutes on mac address 00:00:00:00:00:30 then it would in effect be like BIOS setting to turn the machine on power restoration (except its upto 3 mintues later).

Thomas: I noticed that in your dmesg, you have eth0 as RTL8168d/8111d meaning you have attached a wifi dongle on USB. Which driver you are using? I would love to make this puppy wireless and I have an old USB card lying around...

Pls help. Thanks.

RTL8168d/8111d is my Ethernet Connection, which ist build in. Pardon, but I don't have any WIFI dongle connected