Re: [openwisp] Block menagement page to external networks

2017-06-29 Thread Federico Capoano
In that case, you are right. An nginx rule is needed. You may add an issue on github with this feature request if you like: https://github.com/openwisp/ansible-openwisp2 Federico Il gio 29 giu 2017, 19:07 henriqsc ha scritto: > I want to block console access only from the wan. All clients in t

Re: [openwisp] Block menagement page to external networks

2017-06-29 Thread henriqsc
I want to block console access only from the wan. All clients in the wan side must reach the controller. I thought it would be possible because the console is accessed via GET /admin/ and the clients accesss their configurations using GET /controller/something I'm not sure iptables will do but

Re: [openwisp] Block menagement page to external networks

2017-06-29 Thread Federico Capoano
I think in this case iptables is more suited for this task. I did create an ansible role to set iptables rules but I don't think I added this feature, but it shouldn't be hard to add a variable that let specify the allowed address range to port 443. The ansible role is here: https://github.com/ne

[openwisp] Block menagement page to external networks

2017-06-29 Thread henriqsc
Has anyone successfully applied access restriction to the management part of the controller (*/admin) via nginx openwisp sites-enabled file? I've been trying to block the magement page to non-private IPs but without much of a success. I tryed the standard location /admin {deny all; allow privat