Is security policy required to permit packets between the local zone and the zone where the heartbeat interface resides

2

USG6000 must require, but USG9500 does not.

Other related questions:
Whether a security policy shall be configured between the zone where the heartbeat interface resides and Local zone
If remote is not set when heartbeat interfaces are configured, the heartbeat packets are encapsulated into VRRP packets, and the device that has no security policy can properly process the heartbeat packets. If remote is set when heartbeat interfaces are configured, the heartbeat packets are encapsulated into UDP packets, and a correct security policy needs to be configured for the interzone between the Local zone and the security zone where the heartbeat interfaces reside, which enables the device to properly send and receive the heartbeat packets.

Assigning a VLANIF interface to a security zone
Perform as follows to assign a VLANIF interface to a security zone on the USG: [FW] vlan 10 [FW-vlan-10] quit [FW] interface Vlanif 10 [FW-Vlanif10] quit [FW] interface GigabitEthernet 0/0/1 [FW-GigabitEthernet0/0/1] portswitch [FW-GigabitEthernet0/0/1] port link-type trunk [FW-GigabitEthernet0/0/1] port trunk permit vlan 10 [FW-GigabitEthernet0/0/1] quit [FW] firewall zone name trust1 [FW-zone-trust1] set priority 10 [FW-zone-trust1] add interface Vlanif 10 [FW-zone-trust1] quit

Create a security zone and add interfaces into the security zone on an AR router
A router considers that data flows occurring within a security zone are trustful and therefore no security policy needs to be implemented. If data flows occur between different security zones, the security check function of the firewall is triggered, and corresponding policy is implemented. To configure firewall services, create relevant security zones and specify priorities for the security zones so as to determine deployment of security services according to the priorities between different security zones. The specified priorities cannot be modified; otherwise, other configuration cannot be performed. Different security zones have different priorities. The larger the value, the higher the priority of a zone. After a security zone is created, interfaces must be added to the zone to activate the firewall. The specific configuration procedure is as follows: 1. Run the system-view command to access the system view. 2. Run the firewall zone zone-name command to create a security zone. By default, no security zone is created on the router. 3. Run the priority security-priority command to configure a priority for the security zone. 4. Run the quit command to access the system view. 5. Run the interface interface-type interface-number command to access the interface view. 6. Run the zone zone-name command to add interfaces to the security zone.//Each security zone can contain multiple interfaces, but an interface can be added to one zone only. Note: The router will automatically create a security zone named Local which has the highest priority. This security zone cannot be deleted or contain any interface, and its priority cannot be modified. To apply the firewall functions to the control packets which are reported to this router, the Local security zone may be used. For details about the commands for creating a security zone and adding interfaces into the security zone as well as creating an interzone, see the URL: The AR router creates a security domain and adds the interface to the security zone.

Assigning a firewall interface to the Local zone
You cannot assign a firewall interface to the Local zone.

Assigning an Eth-Trunk interface to a security zone
If the Eth-Trunk interface of the USG is a Layer 3 interface, you need to assign the Eth-Trunk interface to a security zone. [FW]firewall zone untrust [FW-zone-untrust]add interface Eth-Trunk

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top