Comments
-
Thank you for the assistance
-
My apologies on the previous thread. I had added a # "usually add those symbols as bullet points" and came out as bolded. Wanted to clarify that I wasn't implying anything like typing in CAPS, if you know what I mean. - Do you mind confirming internally if the NAT Policy is not supported for route-based VPNs?
-
My apologies but the documentation does not state that dynamic routing is not supported. It states::(This is an example where the Tunnel Interface is an Unnumbered interface without a borrowed interface IP. This is used when Advanced Routing is not needed and only static routes are used for remote networks.)) * It states…
-
Thank you for the update. Will be trying no NAT and recalculate. What's odd is that BGP does come up and routes are being exchanged on both ends. This should be considered going forward - which is the reason why most technologies are going this route to allow multicast routing over a GRE tunnel. I appreciate the response…
-
My apologies for the confusion but wanted to provide as much as data as possible. WAN link is static configured with a /28. Default route to the ISP provider. The other side of the tunnel is AWS - As far as control? Protocols and IPsec proposals as well as BGP configurations. Please note that all three are up; IPsec, GRE…
-
No response? Please your thoughts are valuable here! PDF Documentation doesnt talk about any of this topic