From: Justin Fu (justin_fu@xxxxxxxxxxxxxxx)
Date: Sat Jan 27 2001 - 00:09:14 GMT-3
Hello,
Other substitution in 12.0 above, u may use the prefix list to
accomplish what u want.
for instance, " ip prefix-list MY_LIST seq 5 permit 10.10.10.0/24"
then apply into ur route-map sentence..
like," match ip adress prefix-list", if u insist to use extended
access-list ,
it works with this syntax " access-list 100 permit ip 10.10.10.0
0.0.0.255 host 0.0.0.255"
wish it may help.
Justin Fu
Adrian Chew wrote:
> Michael,
>
> The documentation CD seems to indicate extended access-list support in 12.0,
> but I can't get it to work. Supposedly its...
>
> access-list 101 permit ip host 10.10.10.0 host 255.255.255.0 <- doesn't work
> for me
>
> I can't figure out why anyone would even want to use an extended access-list
> when the same can be achieved via...
>
> access-list 1 permit ip host 10.10.10.0 0.0.0.255 <- confirmed working
>
> If you want to get fancy and track stuffs, ie. if you want to only advertise
> the default conditionally, the way to do is is via the route-map...
>
> route-map defaultadvertise permit 10
> match ip address 1
> match ip next-hop 2 or match interface lo0
>
> Thus not only does the route need to be in the routing table, but the next
> hop has to match too. Pretty cool huh? At any rate, you've gotten me to
> think and understand this properly... which is good considering the lab is
> a week away.
>
> Regards,
> Adrian
>
> ----- Original Message -----
> From: "Michael Le" <mmle@sprintparanet.com>
> To: "'Adrian Chew'" <achew@unmail.org>; "'Padhu (LFG)'" <padhu@steinroe.com>
> Cc: <ccielab@groupstudy.com>
> Sent: Friday, January 26, 2001 6:31 PM
> Subject: RE: BGP - 'neighbor x.x.x.x default-originate route-map mymap'
> command weirdness
>
>
>> Dammit, I'm an idiot. But can you also tell me where the extended
>> access-list I tried was flawed. It wouldn't work either and I know I'm
>
> doing
>
>> something fundamentally (and idiotically) wrong.
>>
>> access-list 101 permit ip 10.10.10.0 0.0.0.0 255.255.255.0 0.0.0.0
>>
>> Thanks for your help.
>>
>> Michael
>>
>> And yes, I accidentally typed in 'network' instead of 'neighbor' under the
>> bgp router statement.
>>
>> -----Original Message-----
>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>> Adrian Chew
>> Sent: Friday, January 26, 2001 5:24 PM
>> To: Michael Le; 'Padhu (LFG)'
>> Cc: ccielab@groupstudy.com
>> Subject: Re: BGP - 'neighbor x.x.x.x default-originate route-map mymap'
>> command weirdness
>>
>>
>> Michael,
>>
>> Change your access list...
>>
>> access-list 1 permit 10.1.1.0 0.0.0.255
>>
>> Unless you have a classful network, include the wildcard mask, and it
>
> should
>
>> work fine.
>>
>> Regards,
>> Adrian
>>
>> ----- Original Message -----
>> From: "Michael Le" <mmle@sprintparanet.com>
>> To: "'Padhu (LFG)'" <padhu@steinroe.com>
>> Cc: <ccielab@groupstudy.com>
>> Sent: Friday, January 26, 2001 5:54 PM
>> Subject: RE: BGP - 'neighbor x.x.x.x default-originate route-map mymap'
>> command weirdness
>>
>>
>>> Yes, both routers have no auto-summary. They're both also running
>>
>> 12.0(15).
>>
>>> Not sure what could be wrong.
>>> Thanks.
>>>
>>> -----Original Message-----
>>> From: Padhu (LFG) [mailto:padhu@steinroe.com]
>>> Sent: Friday, January 26, 2001 4:43 PM
>>> To: 'Michael Le'
>>> Subject: RE: BGP - 'neighbor x.x.x.x default-originate route-map mymap'
>>> command weirdness
>>>
>>>
>>> Did u try no auto summary ?
>>>
>>> -----Original Message-----
>>> From: Michael Le [mailto:mmle@sprintparanet.com]
>>> Sent: Friday, January 26, 2001 4:36 PM
>>> To: ccielab@groupstudy.com
>>> Subject: BGP - 'neighbor x.x.x.x default-originate route-map mymap'
>>> command weirdness
>>>
>>>
>>> I'm trying to get this command to work and it's acting weird.
>>> I have just two routers who are EBGP peers. I want it that if R1 has the
>>> route 10.10.10.0/24 in it's routing table, then it will send the 0.0.0.0
>>> route to R2.
>>>
>>>
>>> [R1]-------[R2]
>>>
>>>
>>> The configs are as follows:
>>>
>>> R1
>>> !
>>> int Serial 0
>>> description To EBGP Peer R2
>>> ip address 192.168.1.1 255.255.255.0
>>> int Loopback 0
>>> description BGP Source Interface
>>> ip address 1.1.1.1 255.255.255.0
>>> int Loopback 1
>>> ip address 10.10.10.1 255.255.255.0
>>> !
>>> router bgp 1
>>> network 192.168.1.2 remote-as 2
>>> network 192.168.1.2 update-source Loopback 0
>>> network 192.168.1.2 ebgp multihop
>>> network 192.168.1.2 default-originate route-map mymap
>>> !
>>> route-map mymap permit 10
>>> match ip address 1
>>> !
>>> access-list 1 permit 10.10.10.0
>>>
>>> Please assume next-hop connectivity and all that, as I haven't posted
>>
>> entire
>>
>>> config. Config for R2 isn't really needed.
>>>
>>>
>>> If I have the configuration as above, then R1 will not advertise the
>>> default route to R2.
>>> However, if I change Loopback 1 to '10.10.10.1 255.0.0.0' and I change
>>
> the
>
>>> access-list to 'permit 10.0.0.0', it will work.
>>> It seems as if it only works with classful networks. I have tried
>>> this with
>>> other network masks too and it only works when the network and the masks
>>> match each other classfully.
>>> This makes no sense to me. Could someone please explain if I'm doing
>>> something wrong or if the command was made to work this way? And if it
>>
> was
>
>>> made to work this way, why? Because it doesn't really give you that much
>>> flexibility with your route-maps.
>>> Thank you.
>>>
>>> Michael Le
>>>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:45 GMT-3