Aruba AP-105 same boot image, same MAC

Hello, I have some AP-105 units. With the first one I had problems reading the flashrom correctly. It was incomplete. I took the next device, read the flashrom successfully and transferred it to the flashrom of the first device. With a hex editor I changedd the ethernet-mac and the serial number in the flashrom file.

When I start the first router under OpenWrt, it shows me the ethernet-mac-address of the second router. Not the one I changed in the flashrom.

hexdump -C /dev/mtd6 |grep f3:f7:ca shows me the correct mac entered by me in the flashrom file.

Does anybody have a hint where I could look up to change the mac address?

1 Like

I'm wondering the same thing. I originally set about to see if I could convert a plain AP-105 to the much more useful IAP-105 which has a built in virtual controller. I dumped the flash form a real IAP-105 and loaded it onto the AP-105 guinea pig and it was successful, it came up as an IAP-105 and worked perfectly so that proves the hardware is indeed identical. There is a problem though, it is a complete clone of the real IAP, all the same MAC addresses and such. That won't matter for using it in a separate installation but obviously it's not going to work with the IAP I cloned it from.

So then I came across the OpenWRT support for the AP-105 and decided to have a go with that. Installation was simple enough and worked on the first try booting up OpenWRT. I checked and confirmed that the MAC addresses match those from the IAP image I started out with so OpenWRT (or U-boot) is clearly aware of the location where this data is stored and able to access it. But where is it stored? Like the OP here I did find the MAC in the IAP firmware image using a hex editor but changing it had no apparent effect.

This is really more of an academic exercise than a real need but it's bugging me, I know it must be possible but every path I've tried has been a dead end.

Nobody knows? Surely somebody had to have this knowledge in order to port OpenWRT to the AP-105 in the first place?

check at offset 0xfe001c