Newsgroup: it.comp.reti.cisco
Titolo: Help Config. Pix

Ciao a tutti,
stò cercando di configurare per la prima volta un pix per un cliente, che
riesce a pingare le mie macchine interne. Mentre io pur pingando dal pix il
suo ip pubblico non riesco a vedere le macchiene interne.
La negozazione IKE funziona correttamente.
Vui posto sotto la conf. sperando che qualcuno possa darmi qualche dritta,
grazie tante in anticipo.
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password *** encrypted
passwd *** encrypted
hostname mia-azienda
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 10.0.0.0 cliente
access-list inside_nat0_outbound permit ip 172.20.44.0 255.255.255.240
cliente 255.
0.0.0
access-list outside_cryptomap_20 permit ip 172.20.44.0 255.255.255.240
cliente 255.
0.0.0
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside ip-pubblco-mia-azineda 255.255.255.240
ip address inside 172.20.44.1 255.255.255.240
ip audit info action alarm
ip audit attack action alarm
pdm location 172.20.44.0 255.255.255.240 inside
pdm location cliente 255.0.0.0 outside
pdm location ip-pubblico-cliente 255.255.255.255 outside
pdm location cliente 255.0.0.0 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 enel
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 172.20.44.0 255.255.255.240 0 0
route outside 0.0.0.0 0.0.0.0 gateway-mia-azienda 1
route outside cliente 255.0.0.0 ip-pubblico-cliente
route outside ip-pubblico-cliente 255.255.255.255 gateway-mia-azienda 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 RADIUS protocol radius
aaa-server LOCAL protocol local
aaa authentication ssh console LOCAL
http server enable
http 172.20.44.0 255.255.255.240 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
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 ip-pubblico-cliente
crypto map outside_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map interface outside
isakmp enable outside
isakmp key ******** address ip-pubblico-cliente netmask 255.255.255.255
no-xauth no-conf
ig-mode
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 172.20.44.2-172.20.44.12 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:****
: end
--------------------------------
Inviato via 
http://arianna.libero.it/usenet/

 route outside ip-pubblico-cliente 255.255.255.255 gateway-mia-azienda 1
prima di tutto, ti serve solo la prima route con il default gateway 
della tua linea, poiche' il pix sa gia' che per raggiungere la lan del 
cliente deve utilizzre il tunnel ipsec (grazie alla acl 
"outside_cryptomap_20")
secondo proverei a verificare le acl del pix o router dall'altra parte
sull'esterna potrebbe non essere abilitato il ping (icmp echo) oppure 
sull'interfaccia interna potrebbe non essere abilitata la risposta (icmp 
echo-reply).