Skip to content

Commit 9748ae1

Browse files
committed
fixed acro
1 parent 1c3c938 commit 9748ae1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-wan/how-to-routing-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -302,7 +302,7 @@ Using the sample VPN configuration and VPN site from above, create firewall rule
302302

303303
### Performance
304304

305-
Configuring private routing policies with Encrypted ExpressRoute routes VPN ESP packets through the next hop security appliance deployed in the hub. As a result, you can expect Encrypted ExpressRoute VPN tunnel throughput of around 1 Gbps in both directions (inbound from on-premises and outbound from Azure). To maximize VPN tunnel throughput, consider the following deployment optimizations:
305+
Configuring private routing policies with Encrypted ExpressRoute routes VPN ESP packets through the next hop security appliance deployed in the hub. As a result, you can expect Encrypted ExpressRoute maximum VPN tunnel throughput of 1 Gbps in both directions (inbound from on-premises and outbound from Azure). To achieve the maximum VPN tunnel throughput, consider the following deployment optimizations:
306306

307307
* Deploy Azure Firewall Premium instead of Azure Firewall Standard or Azure Firewall Basic.
308308
* Ensure Azure Firewall processes the rule that allows traffic between the VPN tunnel endpoints (192.168.1.4 and 192.168.1.5 in the example above) first by making the rule have the highest priority in your Azure Firewall policy. For more information about Azure Firewall rule processing logic, see [Azure Firewall rule processing logic](../firewall/rule-processing.md#rule-processing-using-firewall-policy).

0 commit comments

Comments
 (0)