diff options
| author | Phil Davis <phil.davis@inf.org> | 2015-07-05 23:18:04 +0545 |
|---|---|---|
| committer | Phil Davis <phil.davis@inf.org> | 2015-07-05 23:18:04 +0545 |
| commit | 028ff8f8a3d7c09ee5604d6f3eadcdaaef1610c7 (patch) | |
| tree | 72779176aa19f00e7019e1fd84ce2e86e535f9b0 /usr/local/www/load_balancer_pool_edit.php | |
| parent | 5af646023e447cb386a2bcbeb2900985adce2321 (diff) | |
| download | pfsense-028ff8f8a3d7c09ee5604d6f3eadcdaaef1610c7.zip pfsense-028ff8f8a3d7c09ee5604d6f3eadcdaaef1610c7.tar.gz | |
Fix #4813 validation of enable/disable of gateways and static routes
1) A disabled gateway can always be enabled - no extra validation
needed.
2) When disabling an enabled gateway, check to see that the gateway is
not used in any gateway group or enabled static route (similar tests to
what is already checked before deleting a gateway).
3) A static route can always be disabled - no extra checks needed.
4) When enabling a static route, check that the selected gateway is
enabled - you cannot have a static route enabled on a disabled gateway.
5) Do the address family cross-check between static route and gateway
even when the static route is disabled - we do not want to save
mismatched IP address families in any case.
This covers all the cases I can see to ensure that the enable/disable
status combinations of Gateways and Static Routes is always valid.
Diffstat (limited to 'usr/local/www/load_balancer_pool_edit.php')
0 files changed, 0 insertions, 0 deletions
