Get a demo
I hereby consent to the processing of my personal data specified herein by CROC, for the purposes and within the scope set forth by the Personal Data Protection legislation of the Russian Federation, in conjunction with the activities performed and for an indefinite term.
Preferred communication method
Get a quote
I hereby consent to the processing of my personal data specified herein by CROC, for the purposes and within the scope set forth by the Personal Data Protection legislation of the Russian Federation, in conjunction with the activities performed and for an indefinite term.
Preferred communication method
Try for free
I hereby consent to the processing of my personal data specified herein by CROC, for the purposes and within the scope set forth by the Personal Data Protection legislation of the Russian Federation, in conjunction with the activities performed and for an indefinite term.
Preferred communication method
Know about updates

Route Propagation feature and route prioritization in CROC Cloud

16.07.2021 2 minutes 100

CROC Cloud now supports Route Propagation from a VPN gateway. In addition, we have modified the route lookup behavior for route tables that are explicitly associated with a subnet.

Now, let’s talk about these innovations in more detail. When Route Propagation is enabled, routes for VPN connections, which are obtained over BGP, are automatically added to the selected route table. Route Propagation can only be enabled for one route table.

When it is disabled, BGP routes are not added to any route table and thus do not impact the packets routing from instances in this VPC. However, if the VPC is used as a cloud hub, then traffic between VPNs connected to the VPC is routed using BGP as before, regardless of the Route Propagation option.

By default, Route Propagation for VPC is disabled, and you need to enable it explicitly. You can do this on the VPC page of the web interface by editing the Route Propagation property. In addition, you can enable and disable Route Propagation, using the EnableVgwRoutePropagation and DisableVgwRoutePropagation API methods (see the documentation).

The route obtained over BGP is installed to the selected route table according to the generally accepted best route selection rules. Moreover, if a suitable route for a packet is not found in the route table associated with the subnet, then the route lookup is now stopped and the packet is discarded. For details on the route propagation and route selection rules, see the documentation.

Mentioned services

  1. CROC Public Cloud

Don't miss the most important, interesting and helpful posts of the week

Success

scrollup