RE: 3640 SNAT cannot use TCP to talk to peers, not compatible

From: John Gibson (johngibson1541@yahoo.com)
Date: Mon Jul 09 2007 - 11:56:18 ART

• Next message: Djerk Geurts: "RE: Funky acl question-Check if this is correct"
• Previous message: Amit Kohli: "RE: Funky acl question-Check if this is correct"
• Maybe in reply to: Antonio Soares: "RE: 3640 SNAT cannot use TCP to talk to peers, not compatible"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

It crashed my 3640. System reboots itself.

Also if console shows "%NAT: System busy. Try later"
when I try to "wr", the SNAT config in running will be
removed by the system by itself.

My 2600XM with 12.4 is much much stable to do SNAT.

I am watching packet drops.

SNAT doesn't prevent packet drops. Packet drops
are dominated by routing convergence, right ?

If outgoing packet is sent by primary nat router,
then primary router goes down then if the return
packet is not routed to the backup
nat router SNAT can't improve anything. The next
outgoing packet (TCP resend) can trigger regular
NAT entry any ways in the backup nat router.

• Next message: Djerk Geurts: "RE: Funky acl question-Check if this is correct"
• Previous message: Amit Kohli: "RE: Funky acl question-Check if this is correct"
• Maybe in reply to: Antonio Soares: "RE: 3640 SNAT cannot use TCP to talk to peers, not compatible"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:40 ART