| commit | 2482ea13d44bd5b9680f6f9662404f2f59bfe4ec | |
| author | Augusto Bott <augusto@bott.com.br> | |
| Sat, 11 Feb 2012 06:27:46 +0000 (11 04:27 -0200) | ||
| committer | Augusto Bott <augusto@bott.com.br> | |
| Sat, 11 Feb 2012 06:27:46 +0000 (11 04:27 -0200) | ||
| tree | de14f9acdbf0ef80424b0811bf1804f05348d032 | tree |
| parent | 6dc00162aa1c206b1bf06e0e3de655d8553d01fa | commitdiff |
IP Traffic: when/if set to 'disabled', we 'really' mean it
* when set to 'disabled' on page admin-iptraffic.asp, not a single iptables rule should be generated/created/loaded on rc/firewall.c (re: ipt-account rules)
* also, there should be consistency throughout the web UI - therefore, any/all pages under the 'IP Traffic' menu on the web UI should behave accordingly:
* a: show a warning about this particular feature being currently disabled and...
* b: show the user a link to IP Traffic 'main' settings page (similar to what happens on most of the pages inside the 'Bandwidth' group/submenu)
* when set to 'disabled' on page admin-iptraffic.asp, not a single iptables rule should be generated/created/loaded on rc/firewall.c (re: ipt-account rules)
* also, there should be consistency throughout the web UI - therefore, any/all pages under the 'IP Traffic' menu on the web UI should behave accordingly:
* a: show a warning about this particular feature being currently disabled and...
* b: show the user a link to IP Traffic 'main' settings page (similar to what happens on most of the pages inside the 'Bandwidth' group/submenu)