[mac913]

I noticed the latest Kong build is this case 26135 has made changes to the VAP MACs. I always factory default before and after any firmware update. I have posted some comparisons...

R7000 Build 26135 K3.x

root@AP:~# ifconfig | grep HWa
br0 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:68
br0:0 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:68
br1 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:68
br2 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:68
br3 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:68
br4 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:68
eth0 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:69
eth1 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:6B
eth2 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:68
tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
vlan1 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:69
vlan2 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:6A
vlan3 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:69
vlan5 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:69
vlan6 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:69
vlan8 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:69
wl0.1 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:68
wl0.2 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:69
wl0.3 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:6A
wl1.1 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:69
wl1.2 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:6A
wl1.3 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:6B

eth0 mac is the same as vlan1,3,5,6,8
eth1 mac on it's own
eth2 mac is the same as br0,0:0,1,2,3,4
vlan2 mac on it's own
wl0.1 mac on it's own
wl0.2 mac same as wl1.1
wl0.3 mac same as wl1.2
wl1.3 mac on it's own



R7000 Build 26075 K3.x

root@AP:~# ifconfig | grep HWa
br0 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:23
br0:0 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:23
br1 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:23
br2 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:23
br3 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:23
br4 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:23
eth0 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:24
eth1 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:26
eth2 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:23
tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
vlan1 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:24
vlan2 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:25
vlan3 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:24
vlan5 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:24
vlan6 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:24
vlan8 Link encap:Ethernet HWaddr E4:xx:xx:xx:xx:24
wl0.1 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:27
wl0.2 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:24
wl0.3 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:25
wl1.1 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:20
wl1.2 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:21
wl1.3 Link encap:Ethernet HWaddr E6:xx:xx:xx:xx:22

eth0 mac is the same as vlan1,3,5,6,8
eth1 mac on it's own
eth2 mac is the same as br0,0:0,1,2,3,4
vlan2 mac on it's own
wl0.1 mac on it's own
wl0.2 mac on it's own
wl0.3 mac on it's own
wl1.1 mac on it's own
wl1.2 mac on it's own
wl1.3 mac on it's own



E3000 Build 22000++ K2.6

root@MAIN:~# ifconfig | grep HWa
br0 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
br0:0 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
br1 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
br2 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
br20 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
br3 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
br4 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
br5 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
eth0 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
eth1 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:48
eth2 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:49
vlan1 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
vlan15 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
vlan2 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:47
vlan3 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
vlan4 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
vlan5 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
vlan6 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46
vlan7 Link encap:Ethernet HWaddr 98:xx:xx:xx:xx:46

eth0 mac is the same as vlan1,15,3,4,5,6,7 & br0,0:0,1,2,20,3,4,5
eth1 mac on it's own
eth2 mac on it's own
vlan2 mac on it's own
No VAPs on this router to compare (but is the past I recall VAPs had there own un-shared MACs)

Currently I don't know if the latest builds will cause any problems with the way MACs are paired up. I have updated one R7000 to 26135, the AP unit; I have 2 wireless device that are connected 24/7 and with build 26075 these devices would drop out after 4 days.

[SirSilentBob]

I too have noticed this. It hasn't been an issue for me, but the last 3 firmware updates caused me to be issued a new IP address from my ISP, due to the different MACs. I don't know if some ISPs are picky about MAC addresses, but fortunately mine isn't. R7000 as well.

[mac913]

The R7000's physical MAC hasn't changed. My 1st post is from two different R7000s but I was just stating that the MAC pairing has changes from different builds and I'm not sure how this will impact operation and/or network security if I'm isolating VAPs and VLANs.

I haven't done any real testing. Maybe KONG can enlighten us if it's a problem or not. If I have some time I'll see if the networks are isolated from each other.