on 03-06-2015 03:18 PM
I was needing two WEBVPN group policies, one for business users the other for SCADA users. The business and SCADA servers are on separate networks. The goal was to set VPN split tunneling for its respective network.
Following are the steps I took to make this work.
Router WEBVPN configuration.
webvpn gateway WTP_SSL_VPN
hostname wtp2901.companydomain.com
ip address xxx.xxx.xxx.xxx port 8443
ssl encryption rc4-md5
ssl trustpoint GoDaddySecureCA
inservice
!
webvpn context WTP_SSL_VPN
secondary-color white
title-color #CCCC66
text-color black
aaa authentication list WTPVPN
gateway WTP_SSL_VPN
max-users 10
!
ssl authenticate verify all
inservice
!
policy group BUSINESS
functions svc-enabled
svc address-pool "poolVPN" netmask 255.255.255.255
svc keep-client-installed
svc split dns "companydomain.com"
svc split include 192.168.20.0 255.255.255.0
svc split include 192.168.21.0 255.255.255.0
svc dns-server primary 192.168.20.20
!
policy group SCADA
functions svc-enabled
svc address-pool "poolVPN" netmask 255.255.255.255
svc keep-client-installed
svc split dns "companydomain.com"
svc split include 192.168.11.0 255.255.255.0
svc split include 192.168.12.0 255.255.255.0
!
policy group default_policy
functions svc-enabled
svc address-pool "poolVPN" netmask 255.255.255.255
svc keep-client-installed
svc split include 192.168.21.0 255.255.255.0
default-group-policy default_policy
!
end
Hello Rusty!
Why you didn't configure default-group-policy for webvpn context, like this:
webvpn context NAME
...
default-group-policy POLICY_NAME
...
I think this should be done to split user's accessible networks. Am i right ?
That may have been a better way of doing it but the way I did it does work.
When a business user logs into the VPN, all he/she has access to is the business networks, 192.168.20.0/24 and 192.168.21.0/24. When a SCADA engineer logs into the VPN, all he/she has access to is the SCADA networks, 192.168.11.0/24 and 192.168.12.0/24.
The default group policy is only used in the event the NPS service is not reachable. An administrator VPN log in is enable on the router and is only used when NPS service is not available. This log in only has access to the local business network, 192.168.21.0/24.
Hi Rusty,
Could you mind explaining how you have configured the below? I know it is definitely not using terminal -
I am also trying to setup multiple profiles and I could not get it working. CLI configs for the above would be much helpful.
Thanks,
Rijath Mohammed
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: