Adam, Thanks, that actually makes the most sense to me.
I was just frustrated because yesterday I was using 0.0.0.255 and the DSG had 0.0.0.0 so today I switched to 0.0.0.0 and the DSG had 0.0.0.255 and I was just frustrated. It made me wonder what I was missing. Jud On Sun, Sep 26, 2010 at 5:30 PM, Adam Booth <[email protected]> wrote: > Hi Judson, > > These are just my thoughts on the matter but happy to be corrected by > someone else. Being loose with 0.0.0.255 may allow you to be a little > quicker when you are assembling config fragments in notepad since you can > quickly copy and paste without needing to specify the local interface IP. > > I expect it's a trade off for absolute accuracy against common config parts > for rapid copy and paste. Personally I would be aware of the valid methods > as you are, pick a style that works for you and keep with it regardless of > the DSG as long as you meet the specific lab requirements to meet the > objectives. > > As for the differences that show up in the DSG for specific labs perhaps > they are written by different staff members at IPExpert. > > Cheers, > Adam > > > On Mon, Sep 27, 2010 at 7:51 AM, Judson Bishop <[email protected]> > wrote: >> >> All, >> >> Yesterday I did Vol-1 Lab-11 and today I am working on Vol-1 Lab-15 >> and I have a question regrading the wildcard mask. In the Lab-11 >> solution guide all of the wildcard masks are 0.0.0.0 but in the Lab-15 >> solution guide some are 0.0.0.0 and some are 0.0.0.255. Is it just >> loopback addresses? Is there some rule of thumb I missed? >> >> I realize the goal is determining which interface will be placed in >> what area, 0.0.0.0 only matching the one interface and 0.0.0.255 >> matching a subnets worth of interface addresses, I'm just looking for >> consistency for my understanding and I'm struggling to find it. In >> both situations it is only one interface that is added to an area, yet >> the wildcard masks are different. >> >> I do not understand why Lab-11 uses such tight scope and Lab-15 does not. >> >> Thanks for your help. >> >> Jud >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
