This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BGP routing issue with AWS VPC

We upgraded to V19 and I imported the XML file to create the STS VPN. The tunnels come up and the BGP routes are added to the routing table. The issue is with us working with a vendor on the VPM tunnel they have the same IP network setup on their side that we have on our side. I can narrow down the IP addresses on both sides of the tunnels in the FW rules, but it is still trying to route traffic to the tunnels and this creates connectivity issues to our devices.

I can give the example that we both have 172.30.0.0/16 networks. Their traffic is going from 172.30.5.148 to another network we have 192.168.0.9. But we have an office that has a device at 172.30.12.20. This device can reach everywhere, the return packets are looking for the IP address in the VPN tunnel. Is there a way to look at this routing issue as far as dealing with BGP?  Is there a way to NAT the IP addresses?

Thank you,



Edited TAGs
[edited by: Erick Jan at 4:44 AM (GMT -8) on 15 Nov 2022]