You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll explain my need, that would be simpler.
I've allowed a local network: 10.42.0.0/16
And i need only one IP in this range to be blocked from login: 10.42.13.208
This IP is a reverse proxy that handle external network and redirect it to nextcloud (or other webapp)
Currently i've worked this way (and it cover all of the IP, because there is no missing range between 17 to 32):
defining the order (block then allow, or allow then block), and then apply the blocking/allowing rules.
applying the first match, an allow or a deny. Then the rules order would be the important part.
Thus would allow a better but complex filtering.
If that would be thought too complex to manage, something to test ip or range after applying rules could be helpfull.
Best regards
The text was updated successfully, but these errors were encountered:
Hello,
First thanks for your work
I'll explain my need, that would be simpler.
I've allowed a local network: 10.42.0.0/16
And i need only one IP in this range to be blocked from login: 10.42.13.208
This IP is a reverse proxy that handle external network and redirect it to nextcloud (or other webapp)
Currently i've worked this way (and it cover all of the IP, because there is no missing range between 17 to 32):
All of this rather than doing something like
Block 10.42.13.208/32
Allow 10.42.0.0/16
There could be several way to do it:
Thus would allow a better but complex filtering.
If that would be thought too complex to manage, something to test ip or range after applying rules could be helpfull.
Best regards
The text was updated successfully, but these errors were encountered: