I haven't used IDE for a while and today, when i opened to do something, it was throwing me multiple errors. Error 1 : error: Found argument '--filter-platform' which wasn't expected, or isn't valid in this context The rust-analyzer invokes the command cargo metadata with the flag --filter-platform. This flag was added in Rust 1.41.0. The older versions will give the following error. C:/.cargo/bin/cargo.exe metadata --verbose --format-version 1 --all-features --filter-platform x86_64-pc-windows-msvc stdout : error: Found argument '--filter-platform' which wasn't expected, or isn't valid in this context Error 2 : Another error was Fetching Cargo Config failed. Execution failed (exit code 101). C:/.cargo/bin/cargo.exe -Z unstable-options config get stdout : stderr : error: no such subcommand: `config` Error 3 : Rust 1.39.0 which is no longer supported. It may lead to unexpected errors. Consider upgrading your toolchain to at least 1.56.0 Solution is to
Modular Policy Framework (MPF) configuration defines set of rules for applying firewall features, such as traffic inspection, QoS etc. to the traffic transiting the firewall
There are 3 main components in creating a MPF.
1) Class Map
Class map is used to identify the type of traffic. This can be done by creating an ACL.
2) Policy Map
Policy Map specifies what action the ASA should take against the traffic identified by the Class Map.
3) Service Policy
Finally Service policy specifies where to apply it. The policy is applied to an interface or Globally.
Udacity has special offers worldwide to help anyone learn important, higher-paying job skills during this challenging time. Click here to get your offer and start learning now!
access-list OUTSIDE-TO-INSIDE permit tcp any any eq ftp
<--- The above ACL will allow FTP traffic. This ACL can be different than the Interface ACL--->
class-map FTP-CLASS-MAP
match access-list OUTSIDE-TO-INSIDE
<--- The class map FTP-CLASS-MAP will look for the FTP traffic based on ACL --->
policy-map FTP-POLICY-MAP
class FTP-CLASS-MAP
inspect ftp
<--- What action need to be done? here inspect the ftp. --->
service-policy FTP-POLICY-MAP interface outside
<--- Apply the policy in the outside interface --->
The above illustration is just an example. MPF enables the administrator to assign different network policies to different traffic flows in a flexible and granular manner.
There are 3 main components in creating a MPF.
1) Class Map
Class map is used to identify the type of traffic. This can be done by creating an ACL.
2) Policy Map
Policy Map specifies what action the ASA should take against the traffic identified by the Class Map.
3) Service Policy
Finally Service policy specifies where to apply it. The policy is applied to an interface or Globally.
Udacity has special offers worldwide to help anyone learn important, higher-paying job skills during this challenging time. Click here to get your offer and start learning now! 
Sample Illustration
Consider the following Command lines.access-list OUTSIDE-TO-INSIDE permit tcp any any eq ftp
<--- The above ACL will allow FTP traffic. This ACL can be different than the Interface ACL--->
class-map FTP-CLASS-MAP
match access-list OUTSIDE-TO-INSIDE
<--- The class map FTP-CLASS-MAP will look for the FTP traffic based on ACL --->
policy-map FTP-POLICY-MAP
class FTP-CLASS-MAP
inspect ftp
<--- What action need to be done? here inspect the ftp. --->
service-policy FTP-POLICY-MAP interface outside
<--- Apply the policy in the outside interface --->
The above illustration is just an example. MPF enables the administrator to assign different network policies to different traffic flows in a flexible and granular manner.
