Tom, Can you please elaborate how the outbound filter with the community tag of no-export would help... as I'm still not too clear what it will achieve.
And sorry for the stupid question... Thanks again. Best Regards, Hunt Lee WebCentral ""Tom Martin"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Hunt, You are correct, there is nothing filtering the routes entering from Router B, without local preference set higher on 10.1.1.1 (Router A?) for the routes, nothing will prevent AS 202 from being used for other destinations as well. More confusing to me is the configuration. I read the question as if Router B should only be used for packets _originating_ from AS 202, which should use the T1 connection. In this case an outbound filter would be appropriate, along with a community tag of no-export. Even if this the reverse is true (which the configuration seems to indicate), the as-path access-list is only setting local preference for the AS 300 destination! It seems like the following access-list should have been used: ip as-path access-list 1 permit ^202$ Then again, perhaps I have just totally misunderstood the question. Either way, I hope that this helps. - Tom Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=35459&t=35459 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
