SquidGuard content filtering, captive portal and smart devices

  • Hello,

    I've seemed to have reached a snag in my current setup. Using the captive portal to force user logon, I've been trying to create a "parental block" kind of content filtering situation. It goes like this.

    1. Create users and sort them by "group"
    2. Create ACLs for each "group" (list of users)
    3. Force login using the captive portal so "age restrictions" can be implemented

    Now, this works great until I try to connect a smart device like my Amazon echo. I'm assuming that the captive portal is making the device unable to connect as it just performs a simple WiFi setup. Does anyone have any insight onto this situation?

Log in to reply