That's a bug. When you use Meraki as L3 switch you usually get a random client in the network that get's allotted most traffic coming from the L3 switch. From logical deduction (I don't have the facts like the Meraki team does) I believe the problem is as follows: - The switches/AP can only track clients using MAC - The MX can do both but is configured to use MAC because they're all in the same combined network. - But the L3 switch of course uses it's own MAC to forward frames towards the MX if you use a best practice point-to-point /30 LAN between MX and MS and all LAN traffic gets routed out that /30 towards the MX. - I also believe the traffic recognition differs on the switches than the MX'es so that means if the MX and the MS agree that this traffic is skype.. then the registration of that traffic to the dashboard will be coming from the MS with the correct client MAC address. However if they don't agree for example the MS says it's HTTPS traffic, but the MX classifies the traffic as bittorent then you will have duplicate registration of the same traffic and of course the MX will see the traffic coming from the MAC of the MS causing one client to have major traffic towards WAN/Internet. How it chooses the client name though is a mystery for me. I hope a Meraki technician could provide more inside clarification on this.
... View more
