Re: Summerization (Doyle's book)
Daniel, Sorry, book answer seems pretty good to me. Your binary example shows that the first 7 bits of the third octet are identical. 16+7=23. Give us a shout if it still doesn't ring true. Regards, Gareth ""Daniel"" [EMAIL PROTECTED] wrote in message 8u48dj$e70$[EMAIL PROTECTED]">news:8u48dj$e70$[EMAIL PROTECTED]... I search the archives, looked at the errata for Routing tcp/ip and did not find a correction for the following scenario. Chapt 8 P 373 figure 8.34 Wouldn't the summerization for 192.168.16.0/24.0001 192.168.17.0/24.0001 0001 be 192.168.16.0 /20? The example states 192.168.16.0/23 as the answer Why /23 ? Is this a typo or is there something I am missing? All the other summerization were right on. Thanks, Daniel _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Summerization (Doyle's book)
On Sun, 5 Nov 2000, Daniel wrote: I search the archives, looked at the errata for Routing tcp/ip and did not find a correction for the following scenario. Chapt 8 P 373 figure 8.34 Wouldn't the summerization for 192.168.16.0/24.0001 192.168.17.0/24.0001 0001 /23 is the answer, this doesn't make sense to you though? Here are some examples 192.168.16.0/28 192.168.16.0 - 192.168.16.15 192.168.16.0/27 192.168.16.0 - 192.168.16.31 192.168.16.0/26 192.168.16.0 - 192.168.16.63 192.168.16.0/25 192.168.16.0 - 192.168.16.127 192.168.16.0/24 192.168.16.0 - 192.168.16.255 192.168.16.0/23 192.168.16.0 - 192.168.17.255 192.168.16.0/22 192.168.16.0 - 192.168.19.255 192.168.16.0/21 192.168.16.0 - 192.168.23.255 192.168.16.0/20 192.168.16.0 - 192.168.31.255 Brian be 192.168.16.0 /20? The example states 192.168.16.0/23 as the answer Why /23 ? Is this a typo or is there something I am missing? All the other summerization were right on. Thanks, Daniel _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] --- Brian Feeny, CCNP, CCDP [EMAIL PROTECTED] Network Administrator ShreveNet Inc. (ASN 11881) _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Summerization (Doyle's book) Thanks
also, think of it like: /25 = 2 x /26 /24 = 2 x /25 /23 = 2 x /24 /22 = 2 x /23 /21 = 2 x /22 etc then the only thing you need to make sure of is that the boundries are correct. Brian On Sun, 5 Nov 2000, Daniel wrote: I really appreciate the fast answers I got from all of you.. After researching a lot deeper(should of done this before posting, dah?), I remembered that I had seen good examples of summerization in one of my books. Guess what? Caslow has (page 306) several good examples. What I reaslized I was doing was that I forgot about "contiguous subnets" and was using the "common one bit" rather than the "common bit". so: 192.168.16.0/24.0001 192.168.17.0/24.0001 0001 the "common bit is the "0" at the /23 position The way I see it I was advertising a lot of subnets and that would of confused the routing tables. "Black holes" also comes to mind. Thanks again Daniel ""Daniel"" [EMAIL PROTECTED] wrote in message 8u48dj$e70$[EMAIL PROTECTED]">news:8u48dj$e70$[EMAIL PROTECTED]... I search the archives, looked at the errata for Routing tcp/ip and did not find a correction for the following scenario. Chapt 8 P 373 figure 8.34 Wouldn't the summerization for 192.168.16.0/24.0001 192.168.17.0/24.0001 0001 be 192.168.16.0 /20? The example states 192.168.16.0/23 as the answer Why /23 ? Is this a typo or is there something I am missing? All the other summerization were right on. Thanks, Daniel _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] --- Brian Feeny, CCNP, CCDP [EMAIL PROTECTED] Network Administrator ShreveNet Inc. (ASN 11881) _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
