Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Pix 501 NAT question 1

Status
Not open for further replies.

Rookcr

MIS
Aug 12, 2002
325
US
Good morning.

I have purchased a Pix 501 for my home network. I have 2 questions.

My network consists of a QWEST DSL wireless modem. It has an external IP assigned by Qwest. I then have a DMZ for lack of better terms for my wireless enviroment. It hands out addresses in a subnet 192.168.x.x and then I have the PIX with a static address on the external interface in the 192.168.x.x

On the inside of the pix I use a 192.168.y.y address. This is where I have a Microsoft SBS running IAS.

I have the QWEST router set to dump all traffic to the external interface of the PIX.

Now that we are done with the background here are my 2 questions.

When I connect via the VPN it does request authentication and I authenticate from my IAS server correctly which is on the inside of the PIX, 192.168.y.y

Question #1. Once connected I am unable to remote desktop or VNC to the SBS server or any other workstation. Any ideas since I am able to pass traffic to authenticate.

Question #2. When I get connected it kills all the connections to my local drives at work. My outlook goes off line as well as my network drive. Once again any ideas?

Thanks for your help.

 
Post your config. Also If you are using Windows client to authenticate you will need to adjust in the properties to not use the connect as your default gateway. However, if your internal work network matches your internal at home you will have problems.
 
Normally from a remote site throught the DSL. Now when I use my laptop and then connect while sitting in the 192.168.x.x I am able to authenticate and RDP. When I am outside of it all I am ablke to authenticate but not RDP.
 
Network Ghost,

It will be about 3 hours before I post the config as I will need to run home and grab it. As far as netowrks,

I am on a 192.168.2 at work

At home the Wireless DMZ is a 192.168.99
Inside the Pix is 192.168.100

When I VPN using the cisco Pix client I am set up as a 172.16.1.1

On my work network Outside the routers are 172.17 addresses.
 
Thanks for all of the help so far. I will try to post my config later tonight.
 
Here is my config:

PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password encrypted
passwd encrypted
hostname hpix
domain-name home.local
fixup protocol dns
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol pptp 1723
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
name 172.16.1.0 vpnclient
name 192.168.100.0 home.local
access-list outside_cryptomap_dyn_10 remark VPN Client
access-list outside_cryptomap_dyn_10 permit ip home.local 255.255.255.0 vpnclient 255.255.255.0
access-list is_splitTunnelAcl permit ip home.local 255.255.255.0 any
access-list inside_nat0_outbound permit ip home.local 255.255.255.0 172.17.1.0 255.255.255.0
access-list inside_outbound_nat0_acl permit ip any vpnclient 255.255.255.248
access-list outside_cryptomap_dyn_20 permit ip any vpnclient 255.255.255.248
pager lines 24
logging on
logging timestamp
logging trap informational
mtu outside 1500
mtu inside 1500
ip address outside 192.168.99.2 255.255.255.0
ip address inside 192.168.100.1 255.255.255.0
ip verify reverse-path interface outside
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnclient 172.16.1.1-172.16.1.5
pdm location vpnclient 255.255.255.0 outside
pdm location vpnclient 255.255.255.0 inside
pdm location home.local 255.255.255.255 inside
pdm location 192.168.2.0 255.255.255.0 inside
pdm location 192.168.100.99 255.255.255.255 inside
pdm location vpnclient 255.255.255.255 inside
pdm location 192.168.100.10 255.255.255.255 inside
pdm location 216.81.143.96 255.255.255.240 outside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 192.168.99.1 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
aaa-server partnerauth protocol radius
aaa-server partnerauth max-failed-attempts 3
aaa-server partnerauth deadtime 10
aaa-server partnerauth (inside) host 192.168.100.10 timeout 10
aaa authentication telnet console partnerauth LOCAL
aaa authentication enable console partnerauth LOCAL
http server enable
http home.local 255.255.255.0 inside
http vpnclient 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection tcpmss 1100
sysopt connection permit-ipsec
sysopt connection permit-pptp
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map_1 20 match address outside_cryptomap_dyn_20
crypto dynamic-map outside_dyn_map_1 20 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map_1 65535 ipsec-isakmp dynamic outside_dyn_map_1
crypto map outside_map_1 client authentication partnerauth LOCAL
crypto map outside_map_1 interface outside
isakmp enable outside
isakmp policy 10 authentication rsa-sig
isakmp policy 10 encryption des
isakmp policy 10 hash sha
isakmp policy 10 group 1
isakmp policy 10 lifetime 86400
isakmp policy 30 authentication pre-share
isakmp policy 30 encryption 3des
isakmp policy 30 hash md5
isakmp policy 30 group 2
isakmp policy 30 lifetime 86400
vpngroup home idle-time 1800
vpngroup xy address-pool vpnclient
vpngroup xy dns-server 192.168.
vpngroup xy default-domain home.local
vpngroup xy idle-time 1800
vpngroup xy password
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh timeout 5
management-access inside
console timeout 0
dhcpd address 192.168.100.100-192.168.100.110 inside
dhcpd dns 205.171.3.65 216.81.128.201
dhcpd lease 36000
dhcpd ping_timeout 750
username name password xxxx encrypted privilege 15
terminal width 80
 
Add nat traversal support. If you are located on a nated network and try to connect thru vpn you need that activated.

isakmp nat-traversal 20

Btw, do you have a device that nat´s before the pix?

 
Yes, I have a device that NAT's before the pix. It is what creates my .99 subnet. It has a DMZ option that all traffic destined from the web to the outside interface of it be dumped to a specific address, which I designated as the PIX outside interface.


Internet - DSLRouter-Wireless Subnet(.99) - Pix - Network with IAS server.

The DSL Wireless has the DMZ feature that pushes all traffic to a specific interface (My Pix External)
 
aha,

ok thx :) Well i think the traversal command will solve your problem.
 
Boymarty24.

Thanks. worked perfectly.

So it still kicks me off of the network I am on when I connect to my home network. I use the Cisco VPN client for XP

Thanks
 
Have you gotten this working yet? If not, I would suggest adding:

vpngroup xy split-tunnel outside_cryptomap_dyn_10

What this should do is allow split tunneling to the VPN client. It lets the VPN client know that it has to split the traffic determined in the ACLs to go over the VPN, but then everything else should use the regular internet connection.

Maybe it's just me, but the ACLs seemed kinda of messy and confusing...I didn't look really in depth, but I think you could probably do what you want with only two ACLs instead of five.

Please let us know if it's up and running. :-D

Ben Jitima
 
Ben,

I added the Split tunnel ACL and works great. Since I don't mess with the PIX much what ACLS would you suggest keeping or getting rid of.
 
As far as I can tell, these changes should all be safe. Make sure you create a backup of your config before you make the changes though. I'm pretty sure that the inside_nat0_outbound ACL with your work IP being permitted is unneccessary because the VPN client should be assigning your work computer an IP address from the defined IP pool that is allowed by the other ACLs.

Let me know if this works and if you have any other questions.

Ben Jitima
jitima2@marshall.edu

** keep
XX delete

** access-list outside_cryptomap_dyn_10 remark VPN Client
** access-list outside_cryptomap_dyn_10 permit ip home.local 255.255.255.0 vpnclient 255.255.255.0
XX access-list is_splitTunnelAcl permit ip home.local 255.255.255.0 any
XX access-list inside_nat0_outbound permit ip home.local 255.255.255.0 172.17.1.0 255.255.255.0
** access-list inside_outbound_nat0_acl permit ip any vpnclient 255.255.255.248
XX access-list outside_cryptomap_dyn_20 permit ip any vpnclient 255.255.255.248

** nat (inside) 0 access-list inside_outbound_nat0_acl
** nat (inside) 1 0.0.0.0 0.0.0.0 0 0

** crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
** crypto dynamic-map outside_dyn_map_1 20 match address outside_cryptomap_dyn_20
** crypto dynamic-map outside_dyn_map_1 20 set transform-set ESP-3DES-MD5
XX crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
** crypto map outside_map_1 65535 ipsec-isakmp dynamic outside_dyn_map_1
** crypto map outside_map_1 client authentication partnerauth LOCAL
** crypto map outside_map_1 interface outside


** vpngroup xy split-tunnel outside_cryptomap_dyn_10
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top