Messages

1

Web Proxy Filtering and Caching / Different ACL and FW rules after login to captive portal

« on: October 05, 2021, 05:02:06 pm »

Hello everyone,

is it possible to define different ACL rules (web filter) and/or different firewall rules based on the user logged in to captive portal?

So for example user A is filtered through squid and has no chance pass the firewall without going through the proxy.
User B shouldn't have a proxy and has full internet access.

If it not possible with the user logged into captive portal: Is it possible to filter based on the captive portal the user was using? In this case I could let the users switch between zone 0 (port 8000) and zone 1 (port 8001) and if the log in to zone 0 they have proxy and on zone 1 they have full access.

If this is not possible: Is there another way how to implement this? Maybe using the network behind the SSID just for authentication and then somehow putting the client into net A or net B.

Thanks for your thoughts.
BR

Christian

2

Web Proxy Filtering and Caching / Re: I'm trying to figure out the proper combo for captive portal + user based filter

« on: September 16, 2021, 02:49:11 pm »

Hi Cindex,

I'm working on a similar issue.

In my case I have the same ACL for all users and TCP/UDP forwarding disabled for all users.
But sometimes I would like to login with a privileged user to bypass web proxy and have full internet access.

I see two points here where control via the logged in user (or even better: the user group) would be useful:
Different ACL in web proxy and firewall rules.

For the firewall-part it would be possible to setup a rule based on tagged packets. The tagging could be either the zone-id from captive portal or some tag that can be configured in CP.
So I could setup two captive portals for my interface and switch from one portal (8000 / zone 0 / allowed user-group A) to another (8001 / zone 1 / allowed user group B) before logging in.

BR
evolver