From: kumara.shunmugam@wipro.com
Date: Thu Aug 04 2005 - 10:47:42 GMT-3
Thanks a Lot Scott.. I have already done the same. I have excluded the local subnet from the ACL and included only the subnets which are behind my R6 router. (only 167.1.x.x) . It worked. My BGP is happy now with his peering!!
Thanks once again!
Regards
Shunmugam
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Thursday, August 04, 2005 5:43 AM
To: Kumara Guru Shunmugam L (WI01 - Services); ccielab@groupstudy.com
Subject: RE: IEWB Lab14 TASK 5.22 NAT
Your observations are correct. The "ip nat inside|outside" commands need to
be placed on whatever logical or physical interface that the packets
actually traverse. That interface-based processing is what will or will not
generate a translation.
Layer 3 commands like the 'ip nat' command are not inherited by
subinterfaces or by virtual interfaces.
As for your peering and such (I haven't seen their lab, mind you) you can be
more specific in your source-list command set as to which things do or do
not get translated! If you do translate your BGP session, don't do
authentication on it and remember to peer to the new/translated address
instead of the native one!
HTH,
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
kumara.shunmugam@wipro.com
Sent: Thursday, August 04, 2005 7:29 AM
To: ccielab@groupstudy.com
Subject: IEWB Lab14 TASK 5.22 NAT
Hi guys
This "IP NAT OUTSIDE " is applied on physical ATM interface rather than
Appling it to the ATM Dialer interface (PPPoA). If we apply it in ATM
physical interface as per the solution guide, the NAT will not happen. Becoz
there is no IP address directly bounded with ATM interface... The IP is
assigned at
Dialer1 Interface here. But when apply the same in Dialer 1 with Dialer1
interface as an NAT overload option, the things smooth... But after some
while, the BGP peering get lost between R6 and BB1 due to some TCP 179 port
translation issues. ... When we apply this in physical interfaces,, there
in no debug ip nat output also...Ideally, we should give an interface with
IP address as a overload interface if am correct...
Any inputs will be appreciated
Shun
Confidentiality Notice
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain confidential or privileged information. If you are not the intended
recipient, please notify the sender at Wipro or Mailadmin@wipro.com
immediately and destroy all copies of this message and any attachments.
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:18 GMT-3