pcl04dl3tt3r
New Around Here
My router is the RT-BE88U. It is the main router in an aimesh. I was experiencing issues with my xfinity gateway in bridge mode and struggled with this for a week thinking the problem was on their end, but narrowed it down to what I believe is a bug in the WAN MAC clone feature in the router. My main symptom was that I could not resolve a DHCP address when using MAC Clone, only with the default hardware MAC.
The first clue was that the xfinity gateway was actually seeing 2 devices, one with each MAC address, when enabled. I tried 10 minute reboots in every which combination to no avail. I was also able to connect a laptop directly to the modem and get DHCP resolution no problem even when changing the MAC.
So today i decided to look at what was going on in NVRAM when MAC clone was enabled and discovered something that stood out as odd. It changes wan_hwaddr_x, wan0_hwaddr, and wan0_hwaddr_x, but not wan_hwaddr. That setting was still the default hardware MAC. So, I set it manually and boom... problem solved. I think this is a bug that might be related to various threads I came across with similar DHCP symptoms.
The first clue was that the xfinity gateway was actually seeing 2 devices, one with each MAC address, when enabled. I tried 10 minute reboots in every which combination to no avail. I was also able to connect a laptop directly to the modem and get DHCP resolution no problem even when changing the MAC.
So today i decided to look at what was going on in NVRAM when MAC clone was enabled and discovered something that stood out as odd. It changes wan_hwaddr_x, wan0_hwaddr, and wan0_hwaddr_x, but not wan_hwaddr. That setting was still the default hardware MAC. So, I set it manually and boom... problem solved. I think this is a bug that might be related to various threads I came across with similar DHCP symptoms.