ip tcp intercept + nat

From: Ovidiu Neghina (o.neghina@gmail.com)
Date: Thu May 24 2007 - 16:43:01 ART

• Next message: John Gibson: "Re: IPv6 anycast vs. proxy arp best practice? No need for IPv6"
• Previous message: spduo: "Re: path mtu discovery is considered legacy?"
• Next in thread: Vince Mashburn: "Re: ip tcp intercept + nat"
• Maybe reply: Vince Mashburn: "Re: ip tcp intercept + nat"
• Maybe reply: Ovidiu Neghina: "Re: ip tcp intercept + nat"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi dear all
Thank you for answers related to Frame Relay interface.
I have another question

for this simple topology
----------LAN server ------------R1------outside interface

where we have configured on R1 static nat of LAN server to outside
interface in the command
ip tcp intercept list 199
199 should reference the inside local ip address (LAN) and not inside global
address (outside interface) because of order of operation in nat .
always first nat then tcp intercept.
please correct me if i am wrong . i am having problems with a lab .

Thank you,

Ovidiu

• Next message: John Gibson: "Re: IPv6 anycast vs. proxy arp best practice? No need for IPv6"
• Previous message: spduo: "Re: path mtu discovery is considered legacy?"
• Next in thread: Vince Mashburn: "Re: ip tcp intercept + nat"
• Maybe reply: Vince Mashburn: "Re: ip tcp intercept + nat"
• Maybe reply: Ovidiu Neghina: "Re: ip tcp intercept + nat"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:22 ART