PIX 515e appena scartato non lo pingo...

[giankyfava]

Ho appena montato un nuovo PIX 515e e riesco ad accederci solo da console. Non riesco a pingarlo in nessuna maniera... premetto che cavi, sk rete del pc, classi di indirizzi e subnet sono a posto, le interfacce sono entrambe abilitate. Il PIX risponde alle richieste arp, ma su diversi pc fa sempre la stessa cosa: non risponde al ping. Quale può essere il problema? Grazie.

[giankyfava]

Ecco un dump della configurazione del PIX in questione:

Codice: Seleziona tutto

interface ethernet0 auto

interface ethernet1 auto

nameif ethernet0 outside security0

nameif ethernet1 inside security100

enable password 2KFQnbNIdI.2KYOU encrypted

passwd 2KFQnbNIdI.2KYOU encrypted

hostname pixfirewall

domain-name mediavalle.it

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

access-list acl_out permit icmp any any 

access-list acl_out permit tcp any host 62.123.96.59 eq www 

access-list acl_out permit tcp any host 62.123.96.59 eq https 

access-list 50 permit ip 192.168.168.0 255.255.255.0 10.10.10.0 255.255.255.0 

pager lines 24

mtu outside 1500

mtu inside 1500

ip address outside 62.123.96.58 255.255.255.248

ip address inside 192.168.168.250 255.255.255.0

ip audit info action alarm

ip audit attack action alarm

no failover

failover timeout 0:00:00

failover poll 15

no failover ip address outside

no failover ip address inside

pdm history enable

arp timeout 14400

global (outside) 1 interface

nat (inside) 0 access-list 50

nat (inside) 1 0.0.0.0 0.0.0.0 0 0

static (inside,outside) 192.168.168.50 62.123.96.59 netmask 255.255.255.255 0 0 

access-group acl_out in interface outside

route outside 0.0.0.0 0.0.0.0 62.123.96.57 1

timeout xlate 3:00: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 

http server enable

http 192.168.168.0 255.255.255.0 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 medium esp-des esp-sha-hmac 

crypto map castelnuovo 20 ipsec-isakmp

crypto map castelnuovo 20 match address 50

crypto map castelnuovo 20 set peer 62.123.230.40

crypto map castelnuovo 20 set transform-set medium

crypto map castelnuovo interface outside

isakmp enable outside

isakmp key ******** address 62.123.230.40 netmask 255.255.255.255 

isakmp policy 9 authentication pre-share

isakmp policy 9 encryption des

isakmp policy 9 hash sha

isakmp policy 9 group 1

isakmp policy 9 lifetime 86400

telnet timeout 5

ssh timeout 5

console timeout 0

terminal width 80

[smaikol]

prova a mettere in fondo ad acl_out un permit ip any any.
tieni conto che di default le acl hanno un deny ip any any implicito.

fammi sapere
ciao

[giankyfava]

...risolto... si trattava di un PIX SOLO FAILOVER... ovvero se non connesso ad uno con licensa restricted normale non utilizzabile...

[TheIrish]

[Renato.Efrati]

...risolto... si trattava di un PIX SOLO FAILOVER... ovvero se non connesso ad uno con licensa restricted normale non utilizzabile...

dagli il comando failover active e vedrai ke funzioan tutto (lo forzi a diventare il pix active in un sistema failover)