MAC address changes after reboot on PRO2. **solved**

[RichardH]

I want to change my LAN network configuration from a fixed IP to DHCP and add the MAC address in my router to set the IP address to a reserved IP. But every time I reboot the PRO2, I see another MAC address on the Information/System tab and also my router detects a new device.
Why is that? And can this annoying behaviour be fixed?

I only use a cabled LAN connection. SW version: 6.2 (Sep 23 2025, build 6183), FW 1.3

Thanks,
Richard

[admin]

Can you please give me remote access? Might be a HW issue. Please send credentials to "info(at)meteobridge.com".

[RichardH]

Thank you so much for your help. I will send the credentials to you.

[admin]

Working remotely on Richards MBPRO2 we were able to understand and fix the issue.

The root case is located in the flash partitions prepared from my VOCORE SOC provider in China. There have been a very few instances where mtd2 partition where the MAC is stored was not setup correctly. When the OS starts it detects the issue and generates a random MAC. This is also mentioned in the kernel messages. When you do "dmesg | grep random" on the CLI of your MBPRO2 and get a match like "mtk_soc_eth 10100000.ethernet: generated random MAC address ba:01:5d:09:dd:39" then your MBPRO2 is impacted by this issue.

As a cure the mtd2 partition of the SOC needs to be reflashed. I can do that remotely, when you setup remote login and give me the credentials. As the mtd2 image needs to be setup individually, I do not provide it as an automated fix. Just contact me at "info(at)meteobridge.com" to get this solved.

Currently all new batches of MBPRO2 are checked against this failure pattern, so new PRO2s will not have any need to be reflashed later on.

Sorry for the lengthy text, but I wanted to give some background for the tech savvy to make you fully understand what is going on here.

[admin]

Impacted systems are showing a corresponding warning on "System Info" tab on newest SW release.

[Mattk]

Is there a way to identify units which might be impacted by this issue before any FW updates? Say by Lic #/Details etc? Or is there some cut-off date etc from which newer units are known to be issue free?

Also does this issue affect the Nano which I believe pre-dated the MBPro2

[admin]

It is just a very few and I do not have any pattern in regard to license or manufacturing date.

To test (without using newest SW update) you can direct your browser to

Code: Select all

http://ip-of-your-meteobridge/cgi-bin/system.cgi?dmesg

and search for "random generated" in the resulting text.