From: Michael Wynston (wynnet@xxxxxxx)
Date: Tue Dec 21 1999 - 21:55:57 GMT-3
Ok,
Looks good but...
R2 has DLSW local peer id 32.6.2.2 and a remote peer 32.6.20.5 router R5
R2 has to pass through R4 a NAT router to get to R5
R5 is running in promiscuous mode DLSW and a local peer id of 172.16.8.5
Problem
1) NAT works easily with DLSW if R2 is promiscuous and R5 initiates to R2.
If R5 is promiscuous and R2 initiates then the NAT router does not work
dynamically.
32.6.5.5 is an address in the NAT pool not a real device.
Solution:
Create a static translation for 172.16.8.5:2065, 2067 to 32.6.20.5:2065,
and 2067.
Remove the address 32.6.20.5 dynamic translation pool to prevent
conflicts.
2) 172.16.8.5 tries to send its own TCP connection to 32.6.2.2 in response
to the request.
It cannot initiate a new connection out to pair with the one coming in.
Solution:
Recreate the NAT pool and allow 172.16.8.5 to translate out to 32.6.20.5
Connection comes up and can be initiated in both directions.
Agree?
I have working configs that do this and I tried it without the static and
dynamic NAT and only combined does it allow the connection both ways. Any
suggestions?
Michael Wynston
Phone(908)413-5813
Fax (732)549-4271
email: wynnet@msn.com
CCSI, CCNP, CCNA, MCSE, MCT
CCIE on Jan 8,9 in RTP second try
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Stanislav Sinyagin
Sent: Tuesday, December 21, 1999 3:20 AM
To: kongck; ccielab@groupstudy.com
Subject: Re: NAT advertizing contest
----- Original Message -----
From: kongck <kongck@rocketmail.com>
To: Stanislav Sinyagin <SSinyagin@mtu.ru>; <ccielab@groupstudy.com>
Sent: Tuesday, December 21, 1999 04:03
Subject: Re: NAT advertizing contest
>
> pay attention to DLSW with NAT,
> look at http://www.cisco.com/warp/customer/697/6.html
>
Wow! Thanks, that's a very important issue.
Stan
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:59 GMT-3