SonicOS/X 7 IPSec VPN
- SonicOS and SonicOSX 7 IPSec VPN
- IPSec VPN Overview
- Site to Site VPNs
- VPN Auto Provisioning
- Rules and Settings
- Advanced
- DHCP over VPN
- L2TP Servers and VPN Client Access
- AWS VPN
- SonicWall Support
Route Propagation
Additional steps need to be taken to ensure connections can be made to and from resources on subnets within a particular VPC. You must also propagate the connections to the route table that is used for the subnet of interest. Three ways can be used to enable propagation to the route tables in a VPC.
-
When Creating the VPN Connection
If the firewall detects that route propagation is disabled for one or more route tables within a VPC, the popup dialog includes a checkbox allowing you to specify that Route Propagation should be enabled for all route tables within that VPC. However, this is not a a consistent approach; it does allows propagation for some route tables and not others.
-
Using checkboxes for each route table
After a VPN connection has been established, expanding a row in the VPC table on the AWS VPN page reveals all of the subnets in that VPC, organized by route table. Each route table row includes a checkbox that can be used to enable or disable propagation for that particular route table and the subnets it governs.
-
On the AWS Console
The subnets for each VPC can be viewed on the subnets page under the VPC Dashboard on the AWS Console. Selecting a subnet identifies the governing route table and provides a hyperlink so that you can jump to the relevant page.
Otherwise, you can navigate to the Route Table page and use the filter to narrow the search by VPC or subnet.
To enable or disable route propagation to a specific route table
- Select the route table in question.
- Click the Route Propagation tab.
- Click Edit.
- Check or uncheck the Propagate box as appropriate.
- Click Save to commit your changes.
Was This Article Helpful?
Help us to improve our support portal