[nsp] Easy VPN problem

[Mati Gil]

Have you tried applying "crypto map mapacliente" on ATM0 and ATM0.1
interfaces too?
Can you take a "show crypto ipsec sa"?
saludos,
Mati

-----Mensaje original-----
De: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net]En nombre de Roberto Bazan
Sancho
Enviado el: jueves, 18 de diciembre de 2003 9:28
Para: cisco-nsp at puck.nether.net
Asunto: RE: [nsp] Easy VPN problem


When I establish the tunnel i get the next:

When I make a ping

Haciendo ping a 192.168.8.224 con 32 bytes de datos:

Respuesta desde 80.38.212.248: bytes=32 tiempo=307ms TTL=254
Respuesta desde 80.38.212.248: bytes=32 tiempo=314ms TTL=254
Respuesta desde 80.38.212.248: bytes=32 tiempo=401ms TTL=254

but i don't run any TCP service, for example, i can't make a telnet to
192.168.8.224, and it's a telnet sever.

inet#sh crypto isakmp sa
  f_vrf/i_vrf   dst            src             state       conn-id slot
       /        80.38.212.248   212.75.161.161  QM_IDLE               1
0


I've configured to try:
no ip route-cache
no ip mroute-cache
but i get the same result.


Any Suggestion?

Thank you in advace

-----Mensaje original-----
De: Streiner, Justin [mailto:streiner at stargate.net]
Enviado el: jueves, 18 de diciembre de 2003 2:23
Para: andrew2 at one.net
CC: Roberto Bazan Sancho; cisco-nsp at puck.nether.net
Asunto: RE: [nsp] Easy VPN problem


On Wed, 17 Dec 2003 andrew2 at one.net wrote:

> Just a stab in the dark, but:
>
> no ip route-cache
> no ip mroute-cache
>
> Might do the trick for you.

Note that this also causes the router to process-switch every packet
crossing these interfaces.  You may end up saturating the CPU.  It's
certainly worth a try, but be careful.

jms

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/