ET Firewall is very easy to configure, and you can start making settings to manage traffic on the network
Network administrators can open (pass), block (block), or reject (reject) traffic in the network, using the menu available in the ET Firewall software included in the sales package.
Administrators can add, modify, and edit rules using the easy-to-understand ET Firewall software interface.
You can use the same rules for different kinds of traffic settings.
When enabled, administrators can prevent suspicious traffic from entering the network, using a set of blocking settings based on location and IP address.
Assigns multiple URL lists of IP addresses in the blocking list to one alias and then selects a rule action.
Replacement of Countryblock and IPblocklist by providing the same functionality in one package.
Administrators can manage blocking using one of the blocking functions available in the ET Firewall software.
Suspicious traffic sent to your network can be prevented using an anti-spoofing feature that is easy for administrators to configure.
The firewall checks every traffic. If a spoofing attempt enters the network and originates from an IP address that is detected to be spoofed, traffic from that source will be prevented from entering.
Prevent traffic from bogon networks. ET Firewall can be set to show fake traffic or unused subnets that have been hijacked for malicious purposes.
When an IPsec connection is enabled, the firewall automatically adds certain rules to make the connection work properly.
Time-based rules allow the ET Firewall to be activated during certain days and/or timescales.
The schedule must be defined before it can be used on firewall rules. Schedules are defined in a special menu, and each schedule can contain multiple timeframes.
To create firewall rules using a specific schedule, create a new rule on the desired interface.
If needed, you can restrict your network connection based on certain rules.
This option determines how many total source IP addresses can be connected simultaneously for this rule.
To restrict access on a per-host connection, use this setting. This value can limit the rule to a specific number of connections per source host, not the total connection as a whole.
This setting works similarly to setting the maximum number of connections per host, but checks only status entries rather than tracking if a connection was established successfully.