LAN MAC
C0:A0:BB:5C:C8:A0
WAN MAC
C0:A0:BB:5C:C8:A1
Wireless MAC (wl0 2.4G)
C0:A0:BB:5C:C8:A2
(wl1 5G)
C0:A0:BB:5C:C8:A0
So the 1:macaddr is not in use on DD-WRT?
The wl1 mac address is caculated not from nvram?
(I read there's some writing about converting the 868L into AC66U, it is making wl0 = LAN mac address, and wl1=wl0+4)
LAN MAC
C0:A0:BB:5C:Cb:00
WAN MAC
C0:A0:BB:5C:Cb:01
Wireless MAC wl0 2.4G
C0:A0:BB:5C:Cb:02
wl1 5G
C0:A0:BB:5C:Cb:02
The 1:macaddr does not seem to be in the range.
The wl1 mac address should be same as LAN but it is not.
The symptom is after pwering up, wl0 or wl1 seems to try to compete and when 2.4G works, 5G doesn't. When 5G works, 2.4G doesn't.
So how could I fix this? How is the wl1 mac address caculated here?
Do I fix the 1:macaddr in nvram/cfe editting?
Thanks. _________________ [Broadcom]
DIR868L RevA -> r51506
DIR868L RevA -> r51440
Linksys EA6900-> r42819 STD
WL-500gP v2 --->
[Ralink]
DIR-600 Rev.B -> DD-WRT v3.0-r34886
Last edited by skygunner on Sun Jan 22, 2023 16:35; edited 1 time in total
Thanks. On the setup, networking I found the eth2 address might have problem as it is ending with 02. I changed it to the same as LAN mac address ending with 00. This seems to have fixed the wifi issue, also it does survive a settings reset.
Had a look of the nvram and obviously there are more variables relatd here:
I'm not sure which one had problem before the fix, not sure which variable is actually in use for the 5G wifi. But it is working now. _________________ [Broadcom]
DIR868L RevA -> r51506
DIR868L RevA -> r51440
Linksys EA6900-> r42819 STD
WL-500gP v2 --->
Joined: 16 Nov 2015 Posts: 6436 Location: UK, London, just across the river..
Posted: Sat Jan 21, 2023 22:21 Post subject:
i have the similar issue with my R9000 witch i flashed initially with Kong build back in the days, if this makes any sense...you can change those values but than on reset those will get back...as mac address is stored on another partition...
I dont know if this is corrupted partition or bad initial flash ...i haven't tried to go back stock and than initial flash with BS build to see if this will make any difference...but the only way to sort this out for now is manually charge those values...
nvram show | grep hwaddr
than
nvram set lan_hwaddr=xx:xx:xx:36:xx:xx
nvram commit _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 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 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913