Thanks, I can get data show in statistics, but still device can be accessed and access resources itself
Keep trying, it works reliably here, device doesn’t even get IP address, because all packets are immediatelly dropped.
It only seems to indeed work when device boots, if device is already connected when filter is activated, it does not get stopped (count goes up, but that’s it)
If count goes up and the action is drop, but it’s not actually dropping packets, then it’s not right. Almost like a bug, but I wouldn’t be too quick saying that it’s definitely that, maybe it’s something else in config, but I don’t know what.
I could not say either, but definitely what I see happening
Since the second-least-significant bit of the first octet indicates it is private, I started denying private mac address access to my WiFi networks in capsman with an access-list deny rule. I wish I could give them an error that tells them that private Wi-Fi addresses are not allowed.
/caps-man access-list
add action=reject mac-address=02:00:00:00:00:00 mac-address-mask=02:00:00:00:00:00 comment="reject private oui"