Skip to content

Commit 9821eaf

Browse files
authored
Article integrity fixes for AI readiness
1 parent be57802 commit 9821eaf

1 file changed

Lines changed: 19 additions & 19 deletions

File tree

articles/storage/files/storage-files-configure-p2s-vpn-linux.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Configure a point-to-site VPN on Linux for Azure Files
3-
description: Learn how to configure a point-to-site (P2S) virtual private network (VPN) on Linux to mount your Azure file shares directly on premises.
2+
title: Configure a Point-to-Site VPN on Linux for Azure Files
3+
description: Learn how to configure a point-to-site virtual private network (VPN) on Linux to mount your Azure file shares directly on premises.
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: how-to
7-
ms.date: 05/09/2024
7+
ms.date: 01/14/2026
88
ms.author: kendownie
99
ms.custom:
1010
- devx-track-azurecli
@@ -13,9 +13,9 @@ ms.custom:
1313
# Customer intent: As a Linux system administrator, I want to configure a point-to-site VPN to connect to Azure file shares, so that I can securely access and mount my Azure file shares directly from my on-premises environment.
1414
---
1515

16-
# Configure a point-to-site (P2S) VPN on Linux for use with Azure Files
16+
# Configure a point-to-site VPN on Linux for use with Azure Files
1717

18-
You can use a point-to-site (P2S) virtual private network (VPN) connection to mount your Azure file shares from outside of Azure, without sending data over the open internet. A point-to-site VPN connection is a VPN connection between Azure and an individual client. To use a P2S VPN connection with Azure Files, you need to configure a P2S VPN connection for each client that wants to connect. If you have many clients that need to connect to your Azure file shares from your on-premises network, you can use a site-to-site (S2S) VPN connection instead of a point-to-site connection for each client. To learn more, see [Configure a site-to-site VPN for use with Azure Files](storage-files-configure-s2s-vpn.md).
18+
You can use a point-to-site virtual private network (VPN) connection to mount your Azure file shares from outside of Azure, without sending data over the open internet. A point-to-site VPN connection is a VPN connection between Azure and an individual client. To use a point-to-site VPN connection with Azure Files, you need to configure a point-to-site VPN connection for each client that wants to connect. If you have many clients that need to connect to your Azure file shares from your on-premises network, you can use a site-to-site VPN connection instead of a point-to-site connection for each client. To learn more, see [Configure a site-to-site VPN for use with Azure Files](storage-files-configure-s2s-vpn.md).
1919

2020
We strongly recommend that you read [Azure Files networking overview](storage-files-networking-overview.md) before continuing with this article for a complete discussion of the networking options available for Azure Files.
2121

@@ -37,7 +37,7 @@ The article details the steps to configure a point-to-site VPN on Linux to mount
3737

3838
## Prerequisites
3939

40-
- The most recent version of the Azure CLI. For information on how to install the Azure CLI, see [Install the Azure PowerShell CLI](/cli/azure/install-azure-cli) and select your operating system. If you prefer to use the Azure PowerShell module on Linux, you may. However, the instructions below are for Azure CLI.
40+
- The most recent version of the Azure CLI. For information on how to install the Azure CLI, see [Install the Azure CLI](/cli/azure/install-azure-cli) and select your operating system. If you prefer to use the Azure PowerShell module on Linux, you may. However, the instructions below are for Azure CLI.
4141

4242
- An Azure file share you'd like to mount on-premises. Azure file shares are deployed within storage accounts, which are management constructs that represent a shared pool of storage in which you can deploy multiple file shares. You can learn more about how to deploy Azure file shares and storage accounts in [Create an Azure file share](storage-how-to-create-file-share.md).
4343

@@ -56,19 +56,19 @@ sudo apt install strongswan strongswan-pki libstrongswan-extra-plugins curl libx
5656
INSTALL_DIR="/etc/"
5757
```
5858

59-
If the installation fails or you get an error such as **EAP_IDENTITY not supported, sending EAP_NAK**, you might need to install extra plugins:
59+
If the installation fails or you get an error such as `EAP_IDENTITY not supported, sending EAP_NAK`, you might need to install extra plugins:
6060

6161
```bash
6262
sudo apt install -y libcharon-extra-plugins
6363
```
6464

6565
### Deploy a virtual network
6666

67-
To access your Azure file share and other Azure resources from on-premises via a Point-to-Site VPN, you must create a virtual network, or VNet. You can think of the P2S VPN connection create as a bridge between your on-premises Linux machine and this Azure virtual network.
67+
To access your Azure file share and other Azure resources from on-premises via a point-to-site VPN, you must create a virtual network. You can think of the point-to-site VPN connection as creating a bridge between your on-premises Linux machine and this Azure virtual network.
6868

6969
The following script creates an Azure virtual network with three subnets: one for your storage account's service endpoint, one for your storage account's private endpoint, which is required to access the storage account on-premises without creating custom routing for the public IP of the storage account that may change, and one for your virtual network gateway that provides the VPN service.
7070

71-
Remember to replace `<region>`, `<resource-group>`, and `<desired-vnet-name>` with the appropriate values for your environment.
71+
Replace `<region>`, `<resource-group>`, and `<desired-vnet-name>` with the appropriate values for your environment.
7272

7373
```bash
7474
REGION="<region>"
@@ -148,12 +148,12 @@ The Azure virtual network gateway is the service that your on-premises Linux cli
148148
- A public IP address that identifies the gateway to your clients wherever they are in the world.
149149
- The root certificate you created earlier that is used to authenticate your clients
150150

151-
Remember to replace `<desired-vpn-name-here>` with the name you would like for these resources.
151+
Replace `<desired-vpn-name-here>` with the name you would like for these resources.
152152

153153
> [!NOTE]
154154
> Deploying the Azure virtual network gateway can take up to 45 minutes. While this resource is being deployed, this bash script blocks the deployment from being completed.
155155
>
156-
> P2S IKEv2/OpenVPN connections aren't supported with the **Basic** SKU. This script uses the **VpnGw1** SKU for the virtual network gateway.
156+
> Point-to-site IKEv2/OpenVPN connections aren't supported with the **Basic** SKU. This script uses the **VpnGw1** SKU for the virtual network gateway.
157157
158158
```azurecli
159159
VPN_NAME="<desired-vpn-name-here>"
@@ -174,7 +174,7 @@ az network vnet-gateway create \
174174
--public-ip-addresses $PUBLIC_IP_ADDR \
175175
--location $REGION \
176176
--sku "VpnGw1" \
177-
--gateway-typ "Vpn" \
177+
--gateway-type "Vpn" \
178178
--vpn-type "RouteBased" \
179179
--address-prefixes "172.16.201.0/24" \
180180
--client-protocol "IkeV2" > /dev/null
@@ -208,17 +208,17 @@ sudo cp "${INSTALL_DIR}ipsec.conf" "${INSTALL_DIR}ipsec.conf.backup"
208208
sudo cp "Generic/VpnServerRoot.cer_0" "${INSTALL_DIR}ipsec.d/cacerts"
209209
sudo cp "${USERNAME}.p12" "${INSTALL_DIR}ipsec.d/private"
210210
211-
sudo tee -a "${installDir}ipsec.conf" <<EOF
211+
sudo tee -a "${INSTALL_DIR}ipsec.conf" <<EOF
212212
conn $VIRTUAL_NETWORK_NAME
213213
keyexchange=$VPN_TYPE
214214
type=tunnel
215215
leftfirewall=yes
216216
left=%any
217217
leftauth=eap-tls
218218
leftid=%client
219-
right=$vpnServer
220-
rightid=%$vpnServer
221-
rightsubnet=$routes
219+
right=$VPN_SERVER
220+
rightid=%$VPN_SERVER
221+
rightsubnet=$ROUTES
222222
leftsourceip=%config
223223
auto=add
224224
EOF
@@ -231,10 +231,10 @@ sudo ipsec up $VIRTUAL_NETWORK_NAME
231231

232232
## Mount Azure file share
233233

234-
After setting up your Point-to-Site VPN, you can mount your Azure file share. See [Mount SMB file shares to Linux](storage-how-to-use-files-linux.md) or [Mount NFS file share to Linux](storage-files-how-to-mount-nfs-shares.md).
234+
After setting up your point-to-site VPN, you can mount your Azure file share. See [Mount SMB file shares to Linux](storage-how-to-use-files-linux.md) or [Mount NFS file share to Linux](storage-files-how-to-mount-nfs-shares.md).
235235

236236
## See also
237237

238238
- [Azure Files networking overview](storage-files-networking-overview.md)
239-
- [Configure a Point-to-Site (P2S) VPN on Windows for use with Azure Files](storage-files-configure-p2s-vpn-windows.md)
240-
- [Configure a Site-to-Site (S2S) VPN for use with Azure Files](storage-files-configure-s2s-vpn.md)
239+
- [Configure a point-to-site VPN on Windows for use with Azure Files](storage-files-configure-p2s-vpn-windows.md)
240+
- [Configure a site-to-site VPN for use with Azure Files](storage-files-configure-s2s-vpn.md)

0 commit comments

Comments
 (0)