Yeah no i get that, i know you can only filter out the exact ranges that are advertised but my video specifically said the 2.255.255.255 notation would not work with auto-rp for some reason it had to be done separately like it was IOS weird behaviour. Besides i'm not talking about the mapping agent, i am the RP and advertising myself for these ranges.
Alef On Jun 21, 2011, at 6:12 PM, Max wrote: > On 6/21/2011 3:22 AM, Alef wrote: >> Hi, >> Why doesn't auto-rp handle 2.255.255.255 properly for encompassing >> 228.0.0.0/8 and 230.0.0.0/8 ? it advertises out 228 /7 and 229 /7 ? >> is this behaviour only with this mask specifically, as other wildcards don't >> seem to be a problem? >> >> alef >> >> >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> >> Are you a CCNP or CCIE and looking for a job? Check out >> www.PlatinumPlacement.com > hello, > > 2.255.255.255 will correctly match 228.0.0.0/8 and 230.0.0.0/8 in an ACL, but > for auto-rp you need to specify each subnet/group individually in your filter > on the mapping agent for it to work properly. you can only filter what your > RP is advertising, it has to be an exact match, ranges don't work. > > thanks > max _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
