| commit | b855eb2925fecf0b2f0f0e3d08045c87c135d0de | |
| author | Augusto Bott <augusto@bott.com.br> | |
| Sat, 11 Feb 2012 06:27:46 +0000 (11 13:27 +0700) | ||
| committer | Toastman <toastman@galactic_core> | |
| Sun, 12 Feb 2012 07:09:48 +0000 (12 14:09 +0700) | ||
| tree | e167c832ad13682c75fc4b31f562a898a65de256 | tree |
| parent | 9ee8d737f58312e4e4a72af33023792748719ead | 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)