brasslan
asked on
Modify Pix VPN for windows domain authentication.
I've got a number of people that VPN into our PIX firewall to get to our local network. Below is a sample of my VPN setup. Right now you can see that everyone connects to the VPN using the same username and password. I need to change this config so that the users must have a valid username and password on our windows domain controller (10.50.100.200) in order to create the VPN tunnel. Can you tell me how to modify my config? Is it possible to use windows domain authentication before creating the tunnel?
sysopt connection permit-ipsec
crypto ipsec transform-set myset esp-3des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap interface outside
isakmp enable outside
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup brasslanvpn address-pool vpnpool
vpngroup brasslanvpn dns-server 10.50.100.200
vpngroup brasslanvpn default-domain domain.com
vpngroup brasslanvpn split-tunnel allow-internet
vpngroup brasslanvpn idle-time 1800
vpngroup brasslanvpn password ******
sysopt connection permit-ipsec
crypto ipsec transform-set myset esp-3des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap interface outside
isakmp enable outside
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup brasslanvpn address-pool vpnpool
vpngroup brasslanvpn dns-server 10.50.100.200
vpngroup brasslanvpn default-domain domain.com
vpngroup brasslanvpn split-tunnel allow-internet
vpngroup brasslanvpn idle-time 1800
vpngroup brasslanvpn password ******
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Assuming you already have the crypto and isakmp stuff set up in the configuration, here are the commands for local VPN user authentication:
---------------
aaa-server LOCAL protocol local
ip local pool ippool 10.1.1.1-10.1.1.100
vpngroup vpnusers address-pool ippool
vpngroup vpnusers dns-server 192.168.1.200
vpngroup vpnusers wins-server 192.168.1.201
vpngroup vpnusers default-domain yourdomain.com
vpngroup vpnusers split-tunnel splitTunnelAcl
vpngroup vpnusers idle-time 86400
vpngroup vpnusers password <group_password>
username johndoe password <whatever> privilege 2
access-list splitTunnelAcl permit ip 192.168.1.0 255.255.255.0 any
--------------
The two lines with the references to split tunneling are optional if you want your users to be cut off from the Internet when they are in a VPN session. However, because the 6.x code doesn't support "hairpinning", you will need to implement split tunneling if you want your VPN users to get to the Internet while in a tunnel. In the split tunnel ACL, you specify the network(s) behind as the source of the ACL when you want those networks to be encrypted and sent down the tunnel. Always seemed backwards to me, but that's the way it is...
You can add as many usernames as you like (privilege level 2 is a default). You can just put in:
username johndoe password mypassword
The VPN users will be assigned an IP address from "ippool" and be assigned the specified dns and wins server entries.
---------------
aaa-server LOCAL protocol local
ip local pool ippool 10.1.1.1-10.1.1.100
vpngroup vpnusers address-pool ippool
vpngroup vpnusers dns-server 192.168.1.200
vpngroup vpnusers wins-server 192.168.1.201
vpngroup vpnusers default-domain yourdomain.com
vpngroup vpnusers split-tunnel splitTunnelAcl
vpngroup vpnusers idle-time 86400
vpngroup vpnusers password <group_password>
username johndoe password <whatever> privilege 2
access-list splitTunnelAcl permit ip 192.168.1.0 255.255.255.0 any
--------------
The two lines with the references to split tunneling are optional if you want your users to be cut off from the Internet when they are in a VPN session. However, because the 6.x code doesn't support "hairpinning", you will need to implement split tunneling if you want your VPN users to get to the Internet while in a tunnel. In the split tunnel ACL, you specify the network(s) behind as the source of the ACL when you want those networks to be encrypted and sent down the tunnel. Always seemed backwards to me, but that's the way it is...
You can add as many usernames as you like (privilege level 2 is a default). You can just put in:
username johndoe password mypassword
The VPN users will be assigned an IP address from "ippool" and be assigned the specified dns and wins server entries.
ASKER
You can see my crypto and ISAKMP setup in the original question. The only thing that I didn't have that you mentioned was a username and password listed in the pix. I added this and it still let me create the tunnel without knowing the username and password. With further research on the net I found that I also needed to add this line.
crypto map mymap client authentication LOCAL
The only question that I have left is for lrmoore, I got an e-mail saying that you posted to this question about 45 min after batry_boy's last post, but I don't see anything here. Did you post something? Did it disappear?
crypto map mymap client authentication LOCAL
The only question that I have left is for lrmoore, I got an e-mail saying that you posted to this question about 45 min after batry_boy's last post, but I don't see anything here. Did you post something? Did it disappear?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I won't have time to set this up for a couple of weeks, but with the link that batry provided I shouldn't have a problem.
To tell you the truth, I didn't read that link until lrmoore posted and deleted and reposted his comment :-). I didn't click the link because the RADIUS software that I've used in the past had to be purchased and the tech budget is too tight for more software. But after lrmoore's posting the exact same link (almost) I figured it would be worth a read. I'm glad I did, now I know that I don't have to purchase anything else.
100 pts for lrmoore for telling me that batry was right. (sorry batry) :-) hehe
To tell you the truth, I didn't read that link until lrmoore posted and deleted and reposted his comment :-). I didn't click the link because the RADIUS software that I've used in the past had to be purchased and the tech budget is too tight for more software. But after lrmoore's posting the exact same link (almost) I figured it would be worth a read. I'm glad I did, now I know that I don't have to purchase anything else.
100 pts for lrmoore for telling me that batry was right. (sorry batry) :-) hehe
You are too kind, sir, but have learned a valuable lesson - follow the links...you never know what's on the other side!
ASKER
I think I can also setup a list of user names and passwords inside of the pix, can't I? Then if I want to remove vpn access, I can remove their username from the config. Probably not as nice as a Radius setup but still doable on my scale. Right now we will only have 3 to 5 people with VPN access.
Do you know the code for that?