[nsp] Fwd: [nsp] RTR and NAT (fwd)

From: Kui Zhang (kzhang@cisco.com)
Date: Thu Nov 30 2000 - 18:44:41 EST


> >Resent-Date: Mon, 27 Nov 2000 12:58:30 -0500
> >From: Scott.Keoseyan@BroadWing.com
> >To: cisco-nsp@puck.nether.net
> >Date: Mon, 27 Nov 2000 11:55:39 -0600
> >X-Mailer: Internet Mail Service (5.5.2650.21)
> >Subject: [nsp] RTR and NAT
> >Resent-From: cisco-nsp@puck.nether.net
> >X-Mailing-List: <cisco-nsp@puck.nether.net> archive/latest/4384
> >X-Loop: cisco-nsp@puck.nether.net
> >Resent-Sender: cisco-nsp-request@puck.nether.net
> >
> >hello all!
> >
> >Does anyone know if RTR probe messages will survive NAT?

It depends on the types of RTR(now called Service Assurance Agent) operation.

For those RTR operation types that do not require RTR control message, e.g.,
ICMP, UDP Echo (to standard UDP echo port 7), TCP connect operation (to
wellknown TCP ports), HTTP, it should work with NAT.

For some RTR operations, e.g., jitter, it sends a control message to the
target before the actual measurement packet(to enable the RTR responder on the
target). The destination IP address is also embedded in the control message.
This won't work with NAT.

Cheers,

.kui

> >
> >--
> > Scott A. Keoseyan (sak@broadwing.com)
> > Principal Engineer - Lab Services
> > B R O A D W I N G Inc.*
> > 1881 Campus Commons, Suite 210
> > Reston, Virginia 20191
> > (703)391-1831 - (FAX)391-1810
> > http://www.broadwing.com/ccielab
> >
> >
> >* Company name mentioned for identification purposes only.
> > These ramblings are my own opinions
>
>
>



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:22 EDT