I have a customer who's Eero seems to be exposing either their entire LAN L2 or at least several Eero MACs to the SP side consistently upon every reboot, and given the lack of configurability that the Eero presents, I'm at a loss to figure out how to make it not do that. Some sources suggest this is "expected behavior" which seems baffling. I can't imagine many SPs take kindly to having their access network flooded with dozens of MACs all asking for addressing via DHCP on a single access port. Is this really "expected behavior" from a customer edge router, these days? If so, what's the protocol people have adopted to handle it? The only thing I can think of is very short MAC aging at L2 and then blindly handing any device that shows up on the same access port the same addresses regardless of what L2 address it purports to have. Of course that doesn't fix the fact that any device on the customer's network that successfully completed the DHCP exchange while the true border Eero was "getting ready" now has unusable addressing. Turning DHCP lease times down low enough to combat this without the customer noticing is pretty much a non-starter. So what gives? -- Brandon Martin