Morning all
I'm banging my head against this one.....
I took on a new school recently which had literally zero restrictions on the BYOD wifi. This had to change.
My setup:
Ruckus WiFi using Smartzone
Smoothwall firewall
I've recently implemented RADIUS authentication via NPS with accounting forwarded to Smoothwall but it's causing more issues than it's solved. I'm not doing SSL inspection at this point.
Issue 1 - Different android devices deal with certificates in different ways. Some will just join, others require me to type the name of the radius server in to the "domain" filed, others require the students name in the "anonymous" field etc. etc. Can't write a guide due to there being so many different versions. iOS is fine, just trust the certificate and off you go. This is a massive headache for me and my students. Yes, I have a public certificate for the RADIUS server.
Issue 2 - Smoothwall seems to only tie the username to the IP address about 50% of the time in guardian. If I search on an IP address for example, I will see the IP listed against a username, but other times I will see it listed against itself. This causes a problem because anything that doesn't get picked up doesn't get the correct filtering applied (I have a high level of filtering applied for unauthenticated requests). I tried using the Smoothwall as the actual RADIUS server and the DHCP server to see if this would solve the issue but it didn't.
The main issue is that we are a boarding school. I can't say "Right, no more BYOD!" as that's just not cricket for the boarding students. Nor can I force them to only have certain devices.
I just can't figure out how to do this in such a way that both protects the kids from dangerous stuff, while giving boarding students more access (but still stopping the dangerous stuff), and being as simple as possible so that a year 7 student can do it without messing around.
I'm considering forgoing the RADIUS authentication and just doing a captive portal that authenticates against AD once per day with accounting forwarded to Smoothwall. That doesn't get me around the issue I'm having with Smoothwall not linking usernames to IPs all the time though.
Stressed IT manager here. Any advice would be appreciated.