- Mais recentes
- Mais votos
- Mais comentários
You shouldnt have overlapping static routes with multiple VPN tunnels terminating on same VGW.
You will see weird behaviors like this and the AWS VPN tunnel selecting logic for Egressing out of VPC cannot be controlled in such scenarios This might be expected with the overlapping static routes you have in place.
Is there a reason why you have Overlapping network routes routed via Different Tunnels in the first place ? Maybe it will help if you can clearly specify the routes added via Each of the Three VPNs. VPN-A: Static route ? VPN-B: Static route ? VPN-C: Static route ?
SKKASHAN, thank you for taking the time to respond. Here are the routes. Please note that the local and remote network CIDR defined for the tunnel is the same as the static route.
VPN A AWS Subnet: 172.31.30.0/24 with route to Remote Subnet 10.38.100.0/24
VPNB AWS Subnet: 172.31.30.0/24 with route to Remote Subnet: 10.51.100.0/24
VPNC (troublemaker) AWS Subnet: 172.31.30.110/32 with route to Remote Subnet: 10.200.10.41/32
We have a subnet in AWS reserved for DataAnalytics, and those systems need to communicate with multiple remote sites to collect data. VPNA and VPNB go to our on-prem datacenters, and VPNC goes to a 3rd party remote site that we do not control. They only wanted to tunnel a single IP from their site for the sake of security.
Any help is appreciated!
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 2 anos
Are you using Policy based VPN or route based VPN?
Thanks for taking the time to review my question Tushar_J. All 3 are static route based.