and your macs lay out is ok...in my case by default my lan_hwaddr mac was same as wlan2 witch is the 60Ghz radio .. so, i had to change it..via commands...still no idea why my R9000 defaults with wrong mac's it could be because i first flashed it with Kong build...still need to investigate... _________________ 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
Ah... I did not know the startup script changes would make the nvram set commands moot. Good to know. Originally I noted that my changing of the mac didn't reflect in the GUI, so I did that as a measure to insure I didn't confuse myself in the future. My R9000 does a lot for me and I have configs and scripts doing all sorts of things.
Anyway, as requested, here is the output you requested. I still have my override in there. Ended up changing the mac to a virtual nic from an ESXi VM I was going to delete.
Code:
~# nvram show | grep hwaddr
eth0_hwaddr=00:0C:29:EE:98:E3
size: 45764 bytes (85308 left)
eth1_hwaddr=78:D2:94:41:7A:18
eth2_hwaddr=00:0C:29:EE:98:E3
def_hwaddr=00:0C:29:EE:98:E3
wan_hwaddr=78:D2:94:41:7A:19
vlan1_hwaddr=78:D2:94:41:7A:18
lan_hwaddr=78:D2:94:41:7A:18
wl_hwaddr=
nvram set eth0_hwaddr="00:0C:29:EE:98:E3"
nvram set eth2_hwaddr="00:0C:29:EE:98:E3"
def_whwaddr=78:D2:94:41:7A:1A
wlan0_hwaddr=78:D2:94:41:7A:1A
wlan1_hwaddr=78:D2:94:41:7A:1B
wlan2_hwaddr=8C:45:00:21:2B:31
Another question. Considering eth0 and eth2 share the same mac, if I clone to an address for something active on my network, will that cause a conflict. VLAN2 is the WAN port so it won't matter since it is segregatedon the WAN side, but I was unsure of eth0 and eth2, because eth0 is in a bridge with VLAN1. I ended up opting to use a mac address that was no longer going to risk being used on my network, just in case.
Joined: 16 Nov 2015 Posts: 6437 Location: UK, London, just across the river..
Posted: Mon Jan 24, 2022 19:28 Post subject:
on my R9000 i successfully managed to change any of my interfaces belonging MAC addresses using those guidelines form here, sadly those have to be redone after reset...
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=330392&postdays=0&postorder=asc&start=15 _________________ 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
.. so, i had to change it..via commands...still no idea why my R9000 defaults with wrong mac's it could be because i first flashed it with Kong build...still need to investigate...