Static IP for VPN connections

[afrugone]

I´d like to know if it's possible to assign a static IP address to remote to VPN users, tha´s assign the same IP any time a specific user log in to the VPN, if so please sho me a sample configuration.

Thanks
Alfredo Frugone

 

[tbissett]

Maybe... If you use a RADIUS server, try specifying a return list attribute of Framed-IP-Address with the IP you want the user to have.

I do not believe you can specify a static IP with the PIX local user database.

Someone please correct me if I am wrong

 

[jdeaner]

Why do you need to assign static IP's? Also, how many VPN users? if it is small, try using a smaller pool if you need to pinpoint IP's. We have a problem here with sending mail in exchange through VPN. What we do is put the first 5/10 IP's of the pool into the "allow" range to send mail in exchange 5.5. The PIX grabs the bottom IP's first. We never have more than 5 VPN's at a time and this works for a couple of months until the IP's switch. I'm not an expert but I hope this helps.

 

[afrugone]

Thanks for answering to my question, regarding why I need to do that, it's because we have an application that needs to identify the IP and host of the client, so I need each time a specific users login in my network it must have the same IP, and we need only 3 users, so if it's possible to assign pools of 1 IP to each login it's ok, so please explain me how to asign different pools to each login, for your ref this is my curent set up:

PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 intf2 security10
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pix-vpn
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
names
access-list 101 permit ip any any
pager lines 24
logging on
logging console critical
logging buffered critical
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
mtu outside 1500
mtu inside 1500
mtu intf2 1500
ip address outside 200.20.20.20 255.255.255.0
ip address inside 10.10.11.1 255.0.0.0
ip address intf2 127.0.0.1 255.255.255.255
ip audit info action alarm
ip audit attack action alarm
ip local pool bigpool 10.10.11.2-10.10.11.12
pdm history enable
arp timeout 14400
global (outside) 1 200.20.20.5
nat (inside) 0 access-list 101
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 200.20.20.1 1
route inside 164.96.1.0 255.255.255.0 10.10.10.1 1
route inside 164.96.2.0 255.255.255.0 10.10.10.1 1
route inside 172.20.0.0 255.255.0.0 10.10.10.1 1
route inside 172.20.6.0 255.255.255.0 10.10.10.1 1
route inside 172.25.0.0 255.255.0.0 10.10.10.1 1
route inside 172.27.12.0 255.255.255.0 10.10.10.1 1
route inside 172.27.13.0 255.255.255.0 10.10.10.1 1
route inside 172.27.17.0 255.255.255.0 10.10.10.1 1
route inside 172.27.110.0 255.255.255.0 10.10.10.1 1
route inside 172.27.111.0 255.255.255.0 10.10.10.1 1
route inside 200.6.0.0 255.255.255.0 10.10.10.1 1
route inside 200.6.64.0 255.255.255.0 10.10.10.1 1
route inside 200.6.69.0 255.255.255.0 10.10.10.1 1
route inside 200.6.75.0 255.255.255.0 10.10.10.1 1
route inside 200.6.76.0 255.255.255.0 10.10.10.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 si
p 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
sysopt connection permit-pptp
no sysopt route dnat
crypto ipsec transform-set myset esp-des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap client configuration address initiate
crypto map mymap client configuration address respond
crypto map mymap interface outside
isakmp enable outside
isakmp key ******** address 0.0.0.0 netmask 0.0.0.0
isakmp identity address
isakmp client configuration address-pool local bigpool outside
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption des
isakmp policy 10 hash md5
isakmp policy 10 group 1
isakmp policy 10 lifetime 86400
isakmp policy 20 authentication rsa-sig
isakmp policy 20 encryption des
isakmp policy 20 hash sha
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup vpnall address-pool bigpool
vpngroup vpnall idle-time 1800
vpngroup vpnall password ********
vpngroup mece_1 idle-time 1800
telnet 10.10.10.59 255.255.255.255 inside
telnet 10.10.10.19 255.255.255.255 inside
telnet 10.10.10.29 255.255.255.255 inside
telnet 10.10.10.69 255.255.255.255 inside
telnet 10.10.0.0 255.255.0.0 inside
telnet timeout 5
ssh timeout 5
vpdn group 1 accept dialin pptp
vpdn group 1 ppp authentication pap
vpdn group 1 ppp authentication chap
vpdn group 1 ppp authentication mschap
vpdn group 1 ppp encryption mppe auto
vpdn group 1 client configuration address local bigpool
vpdn group 1 pptp echo 60
vpdn group 1 client authentication local
vpdn username vpnall password ********
vpdn enable outside
terminal width 80
Cryptochecksum:6c0f9b90686b3ea7c6562020e85ae286

 

[jdeaner]

I'm not 100% sure about the static IP's on the PIX. I don't think it can be done either.

 

[jdeaner]

static ip's are possible with access lists. check out ciso's web site:

http://www.cisco.com/en/US/customer...aintenance_guide_chapter09186a008007da0d.html

 

[dopehead]

Just do different vpngroup with different pools attached, with just one ip in each like so :

vpngroup vpn1 address-pool pool1
vpngroup vpn1 idle-time 1800
vpngroup vpn1 password ********

vpngroup vpn2 address-pool pool2
vpngroup vpn2 idle-time 1800
vpngroup vpn2 password ********