FAQ
TL;DR: Two sockets ended up with the identical MAC C0:50:43:C9:00:01; "After re-flashing, the socket will get the original MAC address." Fix BL602 MAC/IP conflicts by reflashing via BLDevCube, filling partition (.toml), boot2 (.bin), firmware (.bin), and dts (.dts). This FAQ guides OpenBeken users through the fix and safe practices. [Elektroda, ok2vuv, post #21497070]
Why it matters: Duplicate MACs break DHCP and connectivity; the right flash procedure restores unique device identity.
Quick Facts
- Symptom: Improperly flashed BL602s can present MAC C0:50:43:C9:00:01, not Bouffalo’s AC:D8:29, causing DHCP conflicts. [Elektroda, sonnyk88, post #20901947]
- Required BLDevCube inputs: partition table (.toml), boot2 (.bin), firmware (.bin), and dts (.dts); omitting boot2/dts caused duplicates. [Elektroda, sonnyk88, post #20921219]
- Software limits: OpenBeken cannot change BL602 MAC; UI edits won’t persist to the router. [Elektroda, p.kaczmarek2, post #20899258]
- Typical whole‑flash size is 2 MB; Web dump attempts were reported to hang. [Elektroda, sonnyk88, post #20900903]
- Confirmed fix: Reflash with dts (and boot2) to restore unique, original MACs. [Elektroda, adolfonovo, post #21494307]
Why do my BL602 devices show the same MAC after flashing OpenBeken?
Skipping required images during flashing can force a fallback MAC, creating duplicates and DHCP conflicts. Users who only flashed the firmware image reported same-MAC behavior. Reflashing with all four images restores the device’s original MAC. Populate partition (.toml), boot2 (.bin), firmware (.bin), and dts (.dts). [Elektroda, sonnyk88, post #20921219]
How do I fix identical MAC addresses on BL602 right now?
Reflash with BLDevCube and ensure both boot2 and dts are selected, along with partition and firmware. After reflashing, devices regained their original MAC and accepted unique IP assignments from the router. This resolves immediate network conflicts. [Elektroda, ok2vuv, post #21497070]
What's the exact BLDevCube reflash procedure to restore the original MAC?
Follow this 3‑step process:
- In BLDevCube, fill Partition (.toml), Boot2 (.bin), Firmware (.bin), and DTS (.dts).
- Keep Advanced options at defaults unless instructed otherwise.
- Flash, reboot, and verify the MAC in your router’s client list.
After this, users report the original MAC returns. [Elektroda, sonnyk88, post #20921219]
Can I change the MAC from OpenBeken's web UI on BL602?
No. As one developer put it, “OpenBeken interface is not able to change MAC on this platform yet.” MAC edits in the UI won’t propagate to the router for BL602. Use the proper BLDevCube flashing process instead. [Elektroda, p.kaczmarek2, post #20899258]
Why doesn't changing IP in OpenBeken stop the conflict?
A user reported that editing both MAC and IP in OpenBeken had no effect. The router still showed the original MAC and reassigned the same IP. This confirms the conflict originates from the MAC, not the local IP setting. [Elektroda, sonnyk88, post #20898428]
How do I confirm the correct Bouffalo OUI on BL602?
Check the first three octets (OUI). Bouffalo’s OUI observed on stock firmware is AC:D8:29. Devices flashed incorrectly showed C0:50:43 and failed OUI lookup. If you see AC:D8:29 after a correct flash, your unit is using its factory MAC. [Elektroda, sonnyk88, post #20901947]
I flashed incorrectly; can I reflash later and restore a unique MAC?
Yes. Reflashing the same device with BLDevCube while filling the dts (and other required images) resolved the duplicated MAC. Users confirmed that doing so restored unique, original MAC addresses on affected switches. [Elektroda, adolfonovo, post #21494307]
Can BLDevCube back up the full BL602 flash?
Yes, there is a read option under the Advanced tab. A developer confirmed that enabling Advanced exposes the read capability inside BLDevCube. Exact steps weren’t detailed in the thread, but the feature exists in the tool. [Elektroda, p.kaczmarek2, post #20901147]
Is using efuse to change the MAC on BL602 safe?
Avoid it. A developer tried an efuse approach and reported, “it somehow bricked my only BL602 dev board.” Stick to the supported flashing method with BLDevCube to prevent permanent damage. [Elektroda, p.kaczmarek2, post #20899258]
How widespread was the issue in this thread?
One report covered three sockets: two flashed units showed the same MAC C0:50:43:C9:00:01, while a third on original firmware showed a Bouffalo OUI AC:D8:29. That illustrates the duplicated-MAC symptom after an incomplete flash. [Elektroda, sonnyk88, post #20901947]
What MAC should I expect after a correct reflash?
Expect the factory MAC to reappear. Users who reflashed with partition, boot2, firmware, and dts reported that the socket got the original MAC and could receive a unique IP. [Elektroda, ok2vuv, post #21497070]
Does OpenBeken support MAC changes on BK7231 but not BL602?
Yes. The platform currently supports MAC changes on BK7231, not on BL602. That’s why the BL602 path focuses on proper flashing rather than software MAC edits. [Elektroda, p.kaczmarek2, post #20901147]
Do BLDevCube Advanced options matter for the MAC fix?
Users who fixed the issue left Advanced options at defaults. The key change was providing all required images (including boot2 and dts) during the flash. Advanced tuning was not necessary in their reports. [Elektroda, sonnyk88, post #20922216]
Which tutorial shows the working BL602 flashing steps?
See the YouTube tutorial referenced by the user: https://www.youtube.com/watch?v=bs0ylC6xRs0&t=201s. They highlighted populating partition, boot2, firmware, and dts in BLDevCube. Following this process restored original MAC addresses. [Elektroda, sonnyk88, post #20921219]