Yes, I did see that in the FAQ, but wanted clarification because it functions unlike other captive-portal-like software where all traffic is intially denied except for 80/443 which is then taken to the login page. The FAQ actually does make it seem like all IP traffic is blocked except for 80/443 which is redirected. The current implementation isn’t sufficient for my needs. I already have them on a separate subnet, but giving access to everything but port 80/443 is not quite what I am looking for. It would be nice if we had the option to block all traffic in a subsequent release. Thanks.