-
Notifications
You must be signed in to change notification settings - Fork 3
Setup Always on VPN using RAS
Richard "Dick" Tracy edited this page Dec 16, 2022
·
2 revisions
This checklist is to be used during the networking configuration. Values that are prefilled in can be used, but they can be changed if needed; make sure you read the comments.
| Name | Values | Comment |
|---|---|---|
| Lab Name | Lab | |
| Domain Name | It is best to create a unique domain | |
| Azure Hub Name | Lab-Hub-Subnet1 | |
| Azure Hub CIDR | 10.10.0.0/16 | |
| Azure Hub Subnet 1 | 10.10.0.0/24 | Specify a space within Hub's CIDR |
| Azure Hub Gateway | 10.10.200.0/26 | Specify a space within Hub's CIDR Subnet but does not conflict with subnet 1 |
| Azure Spoke Name | Lab-Spoke-Subnet1 | |
| Azure Spoke CIDR | 10.20.0.0/16 | |
| Azure Spoke Subnet 1 | 10.20.0.0/24 | Specify space within Spoke's |
| Azure Spoke Subnet 2 | 10.20.1.0/27 | Bastion Subnet |
| Azure VPN ASN Port | 65010 | |
| IPSec Shared Key | This will be generated when setting up VYOS router. | |
| Azure Gateway Public IP | This can be retrieved once a gateway has been created in Azure. | |
| Home Public IP | The home network where the device connected to will be hosting Hyper-V guests, go to: https://ipinfo.io/json . | |
| Hyper-V Subnet 1 | 10.100.1.0/24 | Cannot conflict with Azure subnets |
| Hyper-V Subnet 2 | 10.100.2.0/24 | Cannot conflict with Azure subnet |
| Azure VM: Domain | 10.20.0.1 | Use this to configure Azure |
| Controller IP | subnets internal DNS. If multiple DC's are created, each IP will need to be added. |