Skip to content

Commit cc90386

Browse files
Merge pull request #247666 from wtnlee/RIroutename
RIupdate
2 parents b134350 + c94d905 commit cc90386

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ When routing intent is enabled on the hub, static routes corresponding to the co
148148
| Route Name | Prefixes | Next Hop Resource|
149149
|--|--|--|
150150
| _policy_PrivateTraffic | 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12| Azure Firewall |
151-
_policy_InternetTraffic| 0.0.0.0/0| Azure Firewall |
151+
| _policy_PublicTraffic| 0.0.0.0/0| Azure Firewall |
152152

153153
> [!NOTE]
154154
> Any static routes in the defaultRouteTable containing prefixes that aren't exact matches with 0.0.0.0/0 or the RFC1918 super-nets (10.0.0.0/8, 192.168.0.0/16 and 172.16.0.0/12) are automatically consolidated into a single static route, named **private_traffic**. Prefixes in the defaultRouteTable that match RFC1918 supernets or 0.0.0.0/0 are always automatically removed once routing intent is configured, regardless of the policy type.
@@ -166,7 +166,7 @@ Enabling routing intent on this hub would result in the following end state of t
166166
| Route Name | Prefixes | Next Hop Resource|
167167
|--|--|--|
168168
| _policy_PrivateTraffic | 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12| Azure Firewall |
169-
_policy_InternetTraffic| 0.0.0.0/0| Azure Firewall |
169+
| _policy_PublicTraffic| 0.0.0.0/0| Azure Firewall |
170170
| private_traffic | 40.0.0.0/24, 10.0.0.0/24, 50.0.0.0/24| Azure Firewall |
171171

172172
#### Other methods (PowerShell, REST, CLI)
@@ -180,14 +180,14 @@ For example, consider the scenario where the defaultRouteTable has the following
180180
| firewall_route_ 1 | 10.0.0.0/8|Azure Firewall |
181181
| firewall_route_2 | 192.168.0.0/16, 10.0.0.0/24 | Azure Firewall|
182182
| firewall_route_3 | 40.0.0.0/24| Azure Firewall|
183-
to_internet | 0.0.0.0/0| Azure Firewall |
183+
| to_internet | 0.0.0.0/0| Azure Firewall |
184184

185185
The following table represents the final state of the defaultRouteTable after routing intent creation succeeds. Note that firewall_route_1 and to_internet was automatically removed as the only prefix in those routes were 10.0.0.0/8 and 0.0.0.0/0. firewall_route_2 was modified to remove 192.168.0.0/16 as that prefix is an RFC1918 aggregate prefix.
186186

187187
| Route Name | Prefixes | Next Hop Resource|
188188
|--|--|--|
189189
| _policy_PrivateTraffic | 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12| Azure Firewall |
190-
| _policy_InternetTraffic| 0.0.0.0/0| Azure Firewall |
190+
| _policy_PublicTraffic| 0.0.0.0/0| Azure Firewall |
191191
| firewall_route_2 | 10.0.0.0/24 | Azure Firewall|
192192
| firewall_route_3 | 40.0.0.0/24| Azure Firewall|
193193

0 commit comments

Comments
 (0)