NthrnNYker60 DD-WRT Novice
Joined: 07 Jun 2022 Posts: 10
|
Posted: Wed Oct 30, 2024 5:54 Post subject: Déjà vu ? |
|
Ok, it seems I am having a repeat of an issue I posted previously 2 years ago :
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=332461
For this iteration, I felt I had to replace my main router- an Asus RT-AC3200 loaded with DD-WRT 10/15/2024 - r58568 std because it attenuated the speed of my spectrum gigabyte internet service down to around 350mbs -- I was told on here to dump the router because it's processor was not fast enough to handle that speed without enabling the CTF option -- which made the router unstable.
So, I replaced that router with an Asus RT-AC5300 with a processor twice the speed, also loaded up with the same version of the firmware -- relegating the AC3200 to use as a wired repeater which in turn is daisy-chained (wirelessly) to a TP-Link AC1750 (also loaded up with the latest version of the firmware) to extend the wireless reach to the far end of my home and beyond (outside).
Once again, it seems that all devices that wirelessly connect to those repeater routers seems to pass along to the primary router the same first three OCTET of the Mac addresses "5A:EF:68" ..... Only last three OCTET reflect the real MAC address of the devices.
Now, disregarding the Mac Randomization feature of the phones (which I disabled and thus resolved) --- even THEY have their MAC addresses changed when connected to the repeaters --- and then revert their original MAC addresses when passing out of the wireless zone of the repeaters and into the wireless zone of the main router. Ditto with my laptops, ditto with my tablets. Thus, even IF I was willing to change the static leases of my main router to reflect those realities --- it would not work for my portable devices.
Just for --- and excuse the language --- just for shits & giggles I re-inserted the old Netgear WNDR3800 back in my system instead of the Asus AC3200 --- and programmed in the exact same manner --- worked perfectly.... passed along the correct (and original) MAC addresses as it should.
Now, the issue was marked 'solved' in that previous post because I chose to revert to the obsolete Netgear WNDR3800 N600 router as the repeaters, as we couldn't seem to get to the bottom of the issue. I don't want to do that this time, as I like the increased speed and range -- not to mention the $$$ I have sunk in all these routers.
So what is it about the Atheros chipset that allows correct operation that the Broadcom chipset refuses to ? Or what am I doing wrong in setting up the repeater mode ?
I use this guide to set up the first stage of the repeater (the Ausus AC3200)
https://wiki.dd-wrt.com/wiki/index.php/Wireless_access_point
Any thoughts ? Any solutions ?
|
|
NthrnNYker60 DD-WRT Novice
Joined: 07 Jun 2022 Posts: 10
|
Posted: Wed Oct 30, 2024 13:10 Post subject: Re: Déjà vu ? |
|
NthrnNYker60 wrote: | Ok, it seems I am having a repeat of an issue I posted previously 2 years ago :
Any thoughts ? Any solutions ? |
Turns out --- with a little bit of further research - that the Mac octet substitution only occurs on the 5Ghz wireless band, and the 2.4 Ghz wireless band passes the original MAC addresses as it should.
What could possibly be going wrong here ?
Description: |
|
Filesize: |
423.76 KB |
Viewed: |
1100 Time(s) |

|
|
|
Alozaros DD-WRT Guru

Joined: 16 Nov 2015 Posts: 6785 Location: UK, London, just across the river..
|
Posted: Wed Oct 30, 2024 13:58 Post subject: |
|
for some odd reason my Iphones / apple devices ware playing a similar game...solution was to restore their not private/stock mac address and reboot those devices...as well cold booted the router, left it for a 5 min off...once it was up and all those devices connected with their not private/stock mac address...also noticed that happened only on those Apple devices running the last IOS 18.xx...all that happened recently on Broadcom based R7000...i haven't checked my R7800 or any other Atheros routers for it...
I've no answer for your case... indeed
_________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 58184 WAP
TP-Link WR1043NDv2 -DD-WRT 59369 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 59369 Gateway/DoT,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 59582 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 59582 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Dynalink DL-WRX36-DDWRT 59582
Broadcom
Netgear R7000 --DD-WRT 59582 Gateway/DNScrypt-proxy2/AD-Block,IPset Firewall,Forced DNS,x4VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913 |
|