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

Local Networks No Longer Being Propagated to AWS VPC Route Table

Hello,

After updating the UTM SG105 to 9.508-10 this morning, we can no longer connect to our AWS instances (we have a VPC with Private Subnet only and Hardware VPN setup). Everything was working perfectly fine before the update for the past one year.

One thing that we noticed was that all our local networks (that were defined under Site-to-Site>Amazon VPC>Setup>Route Propagation) were no longer being propagated to AWS VPC (as we could see under Route Tables>Route tab of the VPC earlier).

Did Sophos change anything specific after this update that we need to look into?

Thanks!



This thread was automatically locked due to age.
Parents Reply
  • Glad you got it up in running we really rely on these site to site things..

    One thing I have noticed using multiple ASN.  

     

    --If you have the same local networks on multiple ASN -- It will only propogate those routes to the first ASN. 

     

    So I am connecting to east coast and west coast and my BGP routes are only showing up in one region. other region shows 0..

    Not sure if that is just a bug in my config but doesn't seem right.

    Using static routes in that region instead.

Children