Pix ACL and VPN


I have a VPN that i want to filter traffic

Here's the config.  I removed the sysopt connection permit-ipsec so i can filter what i want
So i want the only access to to be on the host with rdp

My concern is that this ACL is on the ougoing interface and is mixed with the other ACL group of the outside interface so even if somebody is not coming from the VPN, he might spoof the network and gain access.

And later on i want to add a couple of other VPN so i will have to create an access-list for every VPN

Is there another way to do this ?


PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
domain-name ciscopix.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
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
access-list fromnet permit icmp any any echo-reply
access-list fromnet permit tcp eq 3389
access-list inside_outbound_nat0_acl permit ip
access-list outside_cryptomap_20 permit ip
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside
ip address inside
ip audit info action alarm
ip audit attack action alarm
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
access-group fromnet in interface outside
route outside 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 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
ntp server source outside prefer
http server enable
http inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto map outside_map 20 ipsec-isakmp
crypto map outside_map 20 match address outside_cryptomap_20
crypto map outside_map 20 set peer
crypto map outside_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map interface outside
isakmp enable outside
isakmp key ******** address netmask no-xauth no-config-mode
isakmp identity address
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address inside
dhcpd dns
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd enable inside
terminal width 80

Who is Participating?
Probably not with what you have.
In my opinion, you're worrying about nothing.
Nobody can spoof the 192.168.x.x network because it always encrypted and gets decrypted first. It would have to be awfully sophisticated of an attack.
Keep the sysopt enabled because this only affect the outside interface, not the inside and keeps your outside acl clean and easy to manage
What you can do is create a restrictive acl on the inside interface going out
 access-list inside_going_out permit tcp host eq rdp
 access-list inside_going_out deny ip
 access-list inside_going_out permit ip any any
access-group inside_going_out in interface inside

lrmoore is right - that would be a crazy attack.
What you need to do if you want to filter traffic is create a traffic filter - this will restrict traffic on the VPN tunnel-group to the networks/addresses you specify:
As far as I know this command is not available in PIX software 6.x. You will need to upgrade to 7.x if you're running a PIX 501 or 506, or 8.x if you're running a PIX 515 or above.
fox54Author Commented:

I check that out and i tought it was working but in fact it seems that it does not work

Strange enough it blocks ICMP traffic but i can still web-browse the server at from the network

Can the version of the pix have an effect on this ?
it could be.
Latest is 6.3(5)
Unless you have 515 or bigger, then you can upgrade all the way to 8.0(4) which implements a lot of ways to create restrictive acls for VPN's.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.