From: Alexei Monastyrnyi (alexeim@orcsoftware.com)
Date: Sat Nov 11 2006 - 18:25:50 ART
Hi.
"wildcard" is probably not very suitable word here, leading astray. J.
Doyle refers to it as to "inverse mask" for subnet mask on the interface
involved , If we know that "subnet mask" is contiguous so should inverse
mask be.
A.
Alexey Tolstenok wrote:
> Hello group,
> I've discovered some strange thing with subj. If I wanna put several
> interfaces in area with one network command.
> 154.1.3.3/24, 154.1.13.3/24 , 154.1.23.3/24
>
> My solution is through wildcard as usual with access-lists but...
>
> CCIE-R3(config-router)#network 192.168.13.3 0.0.30.0 a 0
> OSPF: Invalid address/mask combination (discontiguous mask)
>
> After some investigation I researched that here only allowed to add "inverse
> mask"
> No "0" after 1st zero allowed:
>
> CCIE-R3(config-router)#network 192.168.13.3 0.0.30.255 a 0
> OSPF: Invalid address/mask combination (discontiguous mask)
> CCIE-R3(config-router)#network 192.168.13.3 0.0.31.255 a 0
> CCIE-R3(config-router)#
>
> In UniverCD says:
>
> The Cisco IOS software sequentially evaluates the *ip-addres*s *
> wildcard-mask* pair for each interface as follows:
>
> * 1. *The *wildcard-mask argument* is logically ORed with the interface IP
> address.
>
> * 2. *The *wildcard-mask argument* is logically ORed with the ip-*address
> argument *in the *network* command.
>
> * 3. *The software compares the two resulting values. If they match, OSPF is
> enabled on the associated interface and this interface is attached to the
> OSPF area specified.
>
> What is going on?
This archive was generated by hypermail 2.1.4 : Fri Dec 01 2006 - 08:05:46 ART