Re: ospf wildcard bits

From: Frank (ocsic@web.de)
Date: Thu Jan 04 2007 - 11:21:11 ART


Alexei Monastyrnyi schrieb:

OK, thank you. I just was confused about "exactly match", that brought
me to the idea, to match it more
close also to the netmask, because i have not seen this kind of wording.

Normaly i would also configure it with the 0.0.0.0 mask. In ospfv3 it's
already only an interface definition.

What i found is, that i will be sometimes confused about the wording in
the questions. Thinking it might be that
there is something hidden i don't expect. People have so must written
about reading each task very carefully,
that maybe i'm now sometimes a little bit picky. That's not bad. Just
takes some time if you think to much on
how to do it. That might be a problem than.

Thanks also for the other answers.

Frank

> Hi.
> I would go for the first one if it is asked for exact match.
> Those two are quite the same in this case, but should you go for /25
> etc mask on interface, that might become critical. I think 0.0.0.0
> wildcard is the best practice until said otherwise.
>
> HTH
> A.
>
> on 1/4/2007 1:52 PM Frank wrote:
>> Hi,
>>
>> what does it mean if i have configure ospf network statements to
>> "match the interface exaclty"?
>>
>> interface s0/0
>> ip add 150.1.1.1 255.255.255.0
>>
>> router ospf 1
>> netwo 150.1.1.1 0.0.0.0
>>
>> or
>>
>> router ospf 1
>> netwo 150.1.1.1 0.0.0.255
>>
>> The first configuration does match the ip address exactly and the
>> second does match the netmask directly.
>> What should you choose. I know both are valid, but what would be the
>> right one regarding to "exaclty
>> match the interface"?
>>
>>
>> Frank
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Thu Feb 08 2007 - 23:46:55 ART