Pix506e Access Rules Help

[judgestone]

I finally got my Pix to talk to my DLink Layer 3 switches VLANs and all VLANs can talk to each other and access the internet. Here is my problem.

-- We have two locations, each has a pix firewall. I have setup each location with a DLink Layer 3 switch with vlans. The two Pix's are connected through a site to site VPN. As long as you are on the default subnet, you can talk between both locations. If you are on any VLAN on either switch, the most you can do is talk to each other VLAN on the switch and connect to the internet; but cannot connect to any other VLAN on the other switch or connect to the other Pix directly.

Here is the setup:

Location 1 - Pix with outside interface - 209.XXX.XXX.XXX, inside interface 10.10.60.X, with a DLink Layer 3 switch connected to it with a default VLAN interface 10.10.60.254. The switch contains other VLANs, 10.10.66.X, 10.10.67.X, 10.10.68.X, and 10.10.69.X

Again all 66-69 can ping each other and the 60 interface and get to the internet no problem.

Location 2 - Pix with outside interface - 70.XX.XX.XX, inside interface 10.10.62.X, with a DLink Layer 3 switch connected to it with a default VLAN of 10.10.60.254. The switch contains other VLANs, 10.10.63.X, 10.10.64.X, and 10.10.65.X.

Again, 63-65 can ping each other and the 62 interface and get to the internet no problem.

They connected through a VPN with the 70 allowing connections from the 209 site.

I just want to be able to ping 10.10.63.X in location 2 from a 10.10.68.X in location 1 and so on. I cannot get the locations to talk. I thought it was a default gateway problem, but that doesn't seem to be it.

I have tried every concoction of rules and have yet to get the right one.

Any help in this matter will be greatly appreciated.

 

[judgestone]

Sorry Should Read:

Location 2 - Pix with outside interface - 70.XX.XX.XX, inside interface 10.10.62.X, with a DLink Layer 3 switch connected to it with a default VLAN of 10.10.62.254. The switch contains other VLANs, 10.10.63.X, 10.10.64.X, and 10.10.65.X.

 

[lgarner]

Check the networks listed in the crypto ACL and the ACL for identity NAT to be sure that all interesting traffic is passed through the tunnel.

 

[judgestone]

This is just from the Pix at Location 1 10.10.60.1 Which is the NorthShore and we have another one at the SouthShore which is 10.10.62.1

Are you refering to this entry:

access-list inside_outbound_nat0_acl permit ip 10.10.60.0 255.255.255.0 192.168.60.0 255.255.255.192
access-list inside_outbound_nat0_acl permit ip 10.10.60.0 255.255.255.0 IMC 255.255.255.0
access-list inside_outbound_nat0_acl permit ip 10.10.60.0 255.255.255.0 SouthShore 255.255.255.0
access-list outside_cryptomap_20 permit ip 10.10.60.0 255.255.255.0 IMC 255.255.255.0

or

access-list outside_cryptomap_40 permit ip 10.10.60.0 255.255.255.0 SouthShore 255.255.255.0

or better off with the external ips being XX

Building configuration...
: Saved
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password XXXXXXX encrypted
passwd XXXXXX encrypted
hostname XXXX
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
names
name 192.168.1.0 XXXX
name 192.168.5.0 vlan5
name 10.10.62.0 SouthShore
object-group service FACTS tcp
port-object range 20000 20999
access-list inside_outbound_nat0_acl permit ip 10.10.60.0 255.255.255.0 192.168.60.0 255.255.255.192
access-list inside_outbound_nat0_acl permit ip 10.10.60.0 255.255.255.0 XXX 255.255.255.0
access-list inside_outbound_nat0_acl permit ip 10.10.60.0 255.255.255.0 SouthShore 255.255.255.0
access-list outside_cryptomap_20 permit ip 10.10.60.0 255.255.255.0 XXX 255.255.255.0
access-list outside_access_in remark Ping
access-list outside_access_in permit tcp any any
access-list outside_cryptomap_40 permit ip 10.10.60.0 255.255.255.0 SouthShore 255.255.255.0
access-list vlan3_access_in permit tcp interface vlan2 any
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 209.XXX.XXX.XXX 255.255.255.252
ip address inside 10.10.60.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool RemoteUsers 192.168.60.10-192.168.60.40
pdm location 192.168.60.0 255.255.255.192 outside
pdm location XXX 255.255.255.0 outside
pdm location SouthShore 255.255.255.0 outside
pdm location 10.10.68.0 255.255.255.0 inside
pdm location 10.10.66.0 255.255.255.0 inside
pdm location 10.10.67.0 255.255.255.0 inside
pdm location 10.10.69.0 255.255.255.0 inside
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
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 209.177.204.245 1
route inside 10.10.66.0 255.255.255.0 10.10.60.254 1
route inside 10.10.67.0 255.255.255.0 10.10.60.254 1
route inside 10.10.68.0 255.255.255.0 10.10.60.254 1
route inside 10.10.69.0 255.255.255.0 10.10.60.254 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
http server enable
http 10.10.60.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community XXXXXXXX
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
sysopt connection permit-pptp
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
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 69.XX.XX.XX
crypto map outside_map 20 set transform-set ESP-DES-MD5
crypto map outside_map 40 ipsec-isakmp
crypto map outside_map 40 match address outside_cryptomap_40
crypto map outside_map 40 set peer 70.XX.XX.XXX
crypto map outside_map 40 set transform-set ESP-3DES-MD5
crypto map outside_map interface outside
isakmp enable outside

Again, I want the 10.10.66-69 to be able to talk to the 10.10.62.1 and 10.10.63-65 that I have configured on the 10.10.62.1 pix

All vlans at either site can ping each other on the switch, ping the switch and pix itself, and get out to the internet; but cannot ping across the VPN? as you could if you were on the default 10.10.60.X or 10.10.62.X subnet with the Pix's as your default gateways.

 

[judgestone]

Sorry for a cross post, I will direct this post to the Pix Forum and on it I have included both configs for the northshore 10.10.60.1, and southshore 10.10.62.1.

http://www.tek-tips.com/viewthread.cfm?qid=1293543&page=1