I'm testing a few android tablets on our wireless the other day when I realize that it seems to be bypassing our inline barracuda filter. I then pull up the logs and realize it thinks the tablet is a legitimate Authenticated domain user. It then occurs to me that it must be using the last authenticated user that used that IP Address. I call Barracuda and sure enough, that's what it's doing. And apparently this is BY DESIGN.
Instead running a simple dns query to realize that the device has changed and have it re-authenticate it just assumes it's an authenticated device. So unless it's a brand new IP it will basically always assume it's Authenticated, essentially it will almost never view them as unauthenticated unless I get "lucky" (technical term used by Barracuda).
Barracuda's solution is to take the whole wireless subnet and force it to be unauthenticated. Authenticated users would they have to manually authenticate through the web browser rather than the seamless AD User authentication their used to.
This is a school, so if I were an enterprising student I would determine my teachers IP, then unplug her computer, assume her IP and get full teachers access to the web. Barracuda confirmed this would definitely work.
I am seriously starting to doubt Barracuda's competence. Has anyone else experienced this? Is this actually by design? Someone please tell me I've been misinformed by some Tier 1 techs.