RE: Is either more correct: Network cmd wildcard mask 0.0.0.0

From: Scott Morris (smorris@ipexpert.com)
Date: Sat May 19 2007 - 16:19:02 ART


Part of the reason for older recommendations on using 0.0.0.0 came with an
avoidance issue on the peer neighbor route for PPP on ISDN BRI and OSPF
demand circuit. We don't have that any more, so there's not much of an
issue for running using one over the other.

Unless there's a strange scenario to run demand circuit over PPPoFR or
something like that. That would create the same problem and thus give you a
desire for 0.0.0.0 to keep your OSPF traffic minimal, but that seems WAY out
there IMHO.

So use whatever method makes you feel better!

 
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
IPexpert VP - Curriculum Development
IPexpert Sr. Technical Instructor
smorris@ipexpert.com
http://www.ipexpert.com
 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Paul
Zugnoni
Sent: Saturday, May 19, 2007 3:00 PM
To: ccielab@groupstudy.com
Subject: Is either more correct: Network cmd wildcard mask 0.0.0.0 vs.
subnet of interface?

Greetings.

Does anyone know whether there's a more correct way (as far as the lab exam
grading goes) between a 0.0.0.0 wildcard mask in the network command vs a
wildcard mask that defines the whole subnet for that interface?

int e0
  ip address 192.168.1.1 255.255.255.0
router eigrp 10
  network 192.168.1.1 0.0.0.0 ! versus
  network 192.168.1.0 0.0.0.255

They both functionally do the same thing, but is there a best practice
around that? In my search on group-study archives, I found a thread from
2001 that ultimately recommended the 0.0.0.0 wildcard mask. Still true?

Thanks,
Paul



This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:21 ART