>
> What does complicate things for us is that users may have specified
> policies without the "custom" policy and custom file. When creating
> the Legacy location, we'll have to somehow save these configuration.
> I've asked Tony Nguyen if there's a way to "export" (and later import)
> these configurations to a file so that Legacy location just stores
> that file.
Just finished talking with Tony. We'll have to do the following when
creating the Legacy location (switching from non-nwam to nwam):
1. a. If firewall_config_default/policy is custom, save filename in
firewall_config_default/custom_policy_file.
b. If firewall_config_default/policy is not custom, save its value.
2. set firewall_config_default/policy to custom
3. set firewall_config_default/custom_policy_file to ipf_config_file
property in the activating location.
4. The other config/{ipf6,ipnat,ippool}.conf properties behavior
doesn't change.
The values are reversed to the original when going from nwam to non-nwam.
Anurag
