Replies: 1 comment
-
|
Duplicate discussion |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
While reviewing the Landing Zone diagrams related to HUB routing, I noticed that the route table rt-region-hub-ingress contains two entries pointing to the nfw-region-hub-int IP address, listed right after the 0.0.0.0/0 route.
I’ve also seen the same pattern in HUB A, HUB B, and HUB C.
My question is:
Wouldn’t those additional routes be redundant?
From a routing perspective, the 0.0.0.0/0 entry should already forward all traffic to the nfw-region-hub-int, so it’s unclear why the more specific routes are needed when they use the same next hop.
If those two routes were removed, would the routing still operate correctly, since all traffic would still be captured by the 0.0.0.0/0 entry?
Is there any specific design requirement or use case that justifies keeping them, or could they simply be included for illustrative purposes in the diagram?
Thanks in advance for any clarification.
Beta Was this translation helpful? Give feedback.
All reactions