If you want to limit the route on the client, you should add a route on the client instead of the Azure virtual network. In fact, you can find the route of the VPN client in the file VpnSettings.xml
of the folder Generic from VPN client downloaded folder.
The file VpnSettings.xml
will like this:
<?xml version="1.0"?>
<VpnProfile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<VpnServer>azuregateway-xxxxx-xxx.vpn.azure.com</VpnServer>
<VpnType>SSTP</VpnType>
<CaCert>xxxxx</CaCert>
<Routes>10.0.0.0/16</Routes>
<Auth>EAPTLS</Auth>
<VnetName>example-network</VnetName>
<VnetId>06e10077-xxxx-xxxx-84d6-5aa4db8b6752</VnetId>
<ServerCertRootCn>DigiCert Global Root CA</ServerCertRootCn>
<ServerCertIssuerCn>DigiCert Global Root CA</ServerCertIssuerCn>
<VpnClientAddressPool>192.168.100.0/24</VpnClientAddressPool>
<AadIssuer />
<AadTenant />
<AadAudience />
<CustomDnsServers />
</VpnProfile>
You could try to modify the route to <Routes>10.50.51.0/26,10.50.51.64/26</Routes>
then you could reinstall the VPN client package like VpnClientSetupAmd64.exe
.
In addition, you can use an Azure network security group to filter network traffic to
and from
Azure resources in an Azure virtual network.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…