Fresh install of v24.10.0 on a Liksys EA8500, and the WAN port refuses to accept an ip address.
This was previously identified in this issue as occurring because WAN and LAN were being given the same MAC address. The fix that was implemented in the latest version was to increment the Wan's MAC address by 1.
Unfortunately, incrementing it by 1 made the WAN match the address given to the 2.4 GHz radio. So the WAN still wouldn't accept an ip address, as reported by rwl408 two days ago here.
My solution is to assign a completely different MAC address to the WAN, and everything works fine now
(in previous thread I thought a workaround involved changing bridge-ports, but I was incorrect. it seemed to work for a little while if i did that, but would revert after a reboot and stop working).
The primary idea would be to fix according to the OEM specs for this device - and only to set a locally administrated MAC address if that is not possible.
(the original commit adding support for this device assigns the same MAC to wan and lan, I have no idea if that follows the OEM specs or was just an omission).
I had this problem when upgrading from 23.05 to 24.10.1. (I gave up on 24.10.0, as i didn't have the time to analyse this.)
This probably has to do with the switch to DSA, but i don't remember the MAC settings on 23.05, i simply never touched them.
I consider this a bug, as it prevents a working setup unless a parameter is changed which usually is unnecessary to change.
Actually i do and it does contain the WAN mac address (although i never changed it). Alas, it is the same mac addr as the lan. So pre DSA was fine with conflicting (or same, but non-conflicting ) mac addresses, whereas DSA is not.
so if today I did a fresh install of the latest/greatest 24.10.2 on this router, has this issue been fixed or do I still need to manually fiddle with the wan mac address?
I never did a fresh install of 24.10.2, but today i installed 24.10.3. I removed the manual mac settings from all interfaces (some where set on the lan / wan / eth devices). After a reboot, it seems, that now random mac addresses are assigned to the eth devices, which are copied to the lan / wan and br devices. The phy wireless devices still have their native mac addresses.
If this is the “fresh install” behaviour, it would work.