<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Binary Math, Part II</title>
	<atom:link href="http://blog.ine.com/2008/11/03/binary-math-part-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/</link>
	<description>Helping you become a Cisco Certified Internetwork Expert</description>
	<lastBuildDate>Wed, 28 Jul 2010 22:47:55 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Binary Math (Part II) &#38; IPv4 Prefix Summarization - So Do You Want to be a CCIE? - 2bccie.com</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-101633</link>
		<dc:creator>Binary Math (Part II) &#38; IPv4 Prefix Summarization - So Do You Want to be a CCIE? - 2bccie.com</dc:creator>
		<pubDate>Wed, 24 Mar 2010 14:40:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-101633</guid>
		<description>[...] subject of Summarization using different methods. I learnt &gt; alot. They were great! &gt; &gt; http://blog.ine.com/2008/11/03/binary-math-part-ii/ &gt; &gt; &gt; http://blog.ine.com/2010/03/17/a-simple-ipv4-prefix-summarization-procedure/ &gt; [...]</description>
		<content:encoded><![CDATA[<p>[...] subject of Summarization using different methods. I learnt &gt; alot. They were great! &gt; &gt; <a href="http://blog.ine.com/2008/11/03/binary-math-part-ii/" rel="nofollow">http://blog.ine.com/2008/11/03/binary-math-part-ii/</a> &gt; &gt; &gt; <a href="http://blog.ine.com/2010/03/17/a-simple-ipv4-prefix-summarization-procedure/" rel="nofollow">http://blog.ine.com/2010/03/17/a-simple-ipv4-prefix-summarization-procedure/</a> &gt; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Binary Math (Part II) &#38; IPv4 Prefix Summarization - So Do You Want to be a CCIE? - 2bccie.com</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-101627</link>
		<dc:creator>Binary Math (Part II) &#38; IPv4 Prefix Summarization - So Do You Want to be a CCIE? - 2bccie.com</dc:creator>
		<pubDate>Wed, 24 Mar 2010 13:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-101627</guid>
		<description>[...] dissected the subject of Summarization using different methods. I learnt alot. They were great! http://blog.ine.com/2008/11/03/binary-math-part-ii/ http://blog.ine.com/2010/03/17/a-simple-ipv4-prefix-summarization-procedure/ I decided to compare [...]</description>
		<content:encoded><![CDATA[<p>[...] dissected the subject of Summarization using different methods. I learnt alot. They were great! <a href="http://blog.ine.com/2008/11/03/binary-math-part-ii/" rel="nofollow">http://blog.ine.com/2008/11/03/binary-math-part-ii/</a> <a href="http://blog.ine.com/2010/03/17/a-simple-ipv4-prefix-summarization-procedure/" rel="nofollow">http://blog.ine.com/2010/03/17/a-simple-ipv4-prefix-summarization-procedure/</a> I decided to compare [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Binary Math (Part II) &#38; IPv4 Prefix Summarization - So Do You Want to be a CCIE? - 2bccie.com</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-101589</link>
		<dc:creator>Binary Math (Part II) &#38; IPv4 Prefix Summarization - So Do You Want to be a CCIE? - 2bccie.com</dc:creator>
		<pubDate>Wed, 24 Mar 2010 10:08:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-101589</guid>
		<description>[...] http://blog.ine.com/2008/11/03/binary-math-part-ii/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.ine.com/2008/11/03/binary-math-part-ii/" rel="nofollow">http://blog.ine.com/2008/11/03/binary-math-part-ii/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Sequeira, #15626</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-59544</link>
		<dc:creator>Anthony Sequeira, #15626</dc:creator>
		<pubDate>Wed, 12 Aug 2009 07:25:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-59544</guid>
		<description>Wow - we have not seen a CCIE Prep book that really goes into this!</description>
		<content:encoded><![CDATA[<p>Wow &#8211; we have not seen a CCIE Prep book that really goes into this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bhuvanesh</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-59174</link>
		<dc:creator>Bhuvanesh</dc:creator>
		<pubDate>Sat, 08 Aug 2009 19:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-59174</guid>
		<description>Dear Scott,

is there any practice book available for such wonderful stuff to be stronger on this part?

Because it needs more practice to be on tips..

Brgds
Bhuvanesh Rajput</description>
		<content:encoded><![CDATA[<p>Dear Scott,</p>
<p>is there any practice book available for such wonderful stuff to be stronger on this part?</p>
<p>Because it needs more practice to be on tips..</p>
<p>Brgds<br />
Bhuvanesh Rajput</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R&#38;S Short Notes – Security &#38; IP Services &#171; #sh ip route vrf CCIE 24163</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-57770</link>
		<dc:creator>R&#38;S Short Notes – Security &#38; IP Services &#171; #sh ip route vrf CCIE 24163</dc:creator>
		<pubDate>Fri, 24 Jul 2009 17:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-57770</guid>
		<description>[...] Know your binary voodoo as Scott Morris @INE calls it,  PartI &amp; PartII. [...]</description>
		<content:encoded><![CDATA[<p>[...] Know your binary voodoo as Scott Morris @INE calls it,  PartI &amp; PartII. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rafał Dworaczek</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-11826</link>
		<dc:creator>Rafał Dworaczek</dc:creator>
		<pubDate>Thu, 06 Nov 2008 20:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-11826</guid>
		<description>My solutions

Question 1:
deny ip 180.34.80.133 0.16.128.96 150.100.32.128 0.0.0.126
permit ip any any

Question 2:
permit 50 ip 19.55.4.0 64.0.9.0 
permit 50 ip 79.55.4.0 0.0.16.0 
permit 50 ip 79.56.4.0 0.0.16.0</description>
		<content:encoded><![CDATA[<p>My solutions</p>
<p>Question 1:<br />
deny ip 180.34.80.133 0.16.128.96 150.100.32.128 0.0.0.126<br />
permit ip any any</p>
<p>Question 2:<br />
permit 50 ip 19.55.4.0 64.0.9.0<br />
permit 50 ip 79.55.4.0 0.0.16.0<br />
permit 50 ip 79.56.4.0 0.0.16.0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Morris, CCIE #4713</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-11696</link>
		<dc:creator>Scott Morris, CCIE #4713</dc:creator>
		<pubDate>Wed, 05 Nov 2008 18:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-11696</guid>
		<description>One more answer had slipped in which I missed:

Dear Scott,

 

The solutions for the binary math2 brainteasers:

 

1.       1.   You have hosts on 150.100.32.0/24.  Make sure the following addresses are not allowed to access any even-numbered server in the second-half of your IP range.  All other access should be allowed.

 

access-list 100 deny ip 180.34.80.133 0.16.128.96 150.100.32.128 0.0.0.126

access-list 100 permit ip any any

 

Explanation:

 

Summarizing the source addresses:

We have 16 ClassB addresses. First octet is the same for each. 2nd, 3rd, 4th octet differs.

We can create 4 piece of subnet-bundle with 4 subnet in each, where subnets have 3 octet in common:

 

1st group

180.34.80.133

180.34.80.165

180.34.80.197

180.34.80.229

 

2nd group

180.34.208.133

180.34.208.165

180.34.208.197

180.34.208.229

 

3rd group

180.50.80.133

180.50.80.165

180.50.80.197

180.50.80.229

 

4th group

180.50.208.133

180.50.208.165

180.50.208.197

180.50.208.229

 

 

3 different octets mean 3 places where we can summarize.

 

2nd octets are 

34

50

In decimal.

 

2nd octets are

00100010

00110010

In binary

 

The bitstrings have 7 bits in common. Where bits are common, we „dont care” in the WC mask so bits will be 0.

The summarized bitstring is

00010000 in binary, that is 16 in decimal.

 

 

3rd octet are

80

208

In decimal

 

3rd octets are

01010000

11010000

In binary

 

The bitstrings have 7 bits in common. Where bits are common, we „dont care” in the WC mask so bits will be 0.

The summarized bitstring is

10000000

In binary, that is 128 in decimal.

 

4th octets are

133

165

197

229

In decimal

 

4th octet are

10000101

10100101

11000101

11100101

 

The bitstrings have 6 bits in common. Where bits are common, we „dont care” in the WC mask so bits will be 0.

The summarized bitstring is

01100000

In binary, that is 96 in decimal.

 

 

The first 8 address can be summarized as follows:

1st group

180.34.80.133

180.34.80.165

180.34.80.197

180.34.80.229

2nd group

180.34.208.133

180.34.208.165

180.34.208.197

180.34.208.229

 

First two octet are common so WC mask will be 0.

Third octet are 80 and 208. These can covered with WC mask 128.

4th octets can be covered with WC mask 96.

 

The summarization of the 8 addresses is   180.34.80.133 0.0.128.96

 

The second 8 address can be summarized as follows:

1st group

180.50.80.133

180.50.80.165

180.50.80.197

180.50.80.229

2nd group

180.50.208.133

180.50.208.165

180.50.208.197

180.50.208.229

 

First two octet are common so WC mask will be 0.

Third octet are 80 and 208. These can covered with WC mask 128.

4th octets can be covered with WC mask 96.

 

The summarization of the 8 addresses is   180.50.80.133 0.0.128.96

 

The first and the second summarizations:

180.34.80.133 0.0.128.96

180.50.80.133 0.0.128.96

 

Only the second octets are different, and can be covered with WC mask 16 (as explained earlier)

So the full summarization of source addresses is:

 

180.34.80.133 0.16.128.96

 

180.34.80.133

180.34.80.165

180.34.80.197

180.34.80.229

 

180.34.208.133

180.34.208.165

180.34.208.197

180.34.208.229

 

180.50.80.133

180.50.80.165

180.50.80.197

180.50.80.229

 

180.50.208.133

180.50.208.165

180.50.208.197

180.50.208.229

 

3 octets differ.

 

We can summarize all of them.

 

34              00100010

50              00110010

 - - - - - - - - - - - - - - - -

WC            00010000 = 16 in decimal

 

80              01010000

208            11010000

 - - - - - - - - - - - - - - - -

WC            10000000 = 128 in decimal

 

133            10000101

165            10100101

197            11000101

229            11100101

 - - - - - - - - - - - - - - - -

WC            01100000 = 96 in decimal

 

 

 

180.34.80.133

180.34.80.165

180.34.80.197

180.34.80.229

Summarized as 180.34.80.133 0.0.0.96

 

180.34.208.133

180.34.208.165

180.34.208.197

180.34.208.229

Summarized as 180.34.208.133 0.0.0.96

 

180.50.80.133

180.50.80.165

180.50.80.197

180.50.80.229

Summarized as 180.50.80.133 0.0.0.96

 

180.50.208.133

180.50.208.165

180.50.208.197

180.50.208.229

Summarized as 180.50.208.133 0.0.0.96

 

180.34.80.133 0.0.0.96 and 180.34.208.133 0.0.0.96 can be further summarized as 180.34.80.133 0.0.128.96 (summarizing the 3rd octets).

180.50.80.133 0.0.0.96 and 180.50.208.133 0.0.0.96 can be further summarized as 180.50.80.133 0.0.128.96 (summarizing the 3rd octets).

 

180.34.80.133 0.0.128.96 and 180.50.80.133 0.0.128.96 can be further summarized, summarizing the 2nd octets:  180.34.80.133 0.16.128.96

 

 

 

 

Destination addresses are 150.100.32.128 – 150.100.32.254  in the 150.100.32.0/24 subnet

 

The last octet of these addresses:

10000000

10000010

10000100

...

11111110

 

The most significant bits are always 1 the leasts are always 0. Common bits are 0 in the WC mask, so WC mask will be 01111110 in binary, 126 in decimal. The even-numbered servers in upper half of the subnet 150.100.32.0/24 are covered with 150.100.32.128 0.0.0.126 

 

The access-list will be:

 

access-list 100 deny ip 180.34.80.133 0.16.128.96 150.100.32.128 0.0.0.126

access-list 100 permit ip any any

 

 

 

2.     Second task

 

access-list 90 permit 19.55.4.0 64.0.9.0

access-list 90 permit 79.55.4.0 0.0.16.0

access-list 90 permit 79.56.4.0 0.0.16.0

 

Expl.

 

19.55.4.0/24

19.55.5.0/24

19.55.12.0/24

19.55.13.0/24

 

4          00000100

5          00000101

12        00001100

13        00001101

- - - - - - -  - - - - - - 

WC       00001001

 

These 4 networks can be summarized as  19.55.4.0 0.0.9.0

 

83.55.4.0/24

83.55.5.0/24

83.55.12.0/24

83.55.13.0/24

 

4          00000100

5          00000101

12        00001100

13        00001101

- - - - - - -  - - - - - - 

WC       00001001

 

These 4 networks can be summarized as  83.55.4.0 0.0.9.0

 

The 2 summarized networks are

19.55.4.0 0.0.9.0

83.55.4.0 0.0.9.0

 

Only the first octet differs. Can be summarized:

 

19        00010011

83        01010011

 - - - - - - - - - - - - - 

WC       01000000  = 64 in decimal

 

So we can further summarize as:           19.55.4.0 64.0.9.0

 

79.55.4.0/24

79.55.20.0/24

 

3rd octet differs, we can summarize as follows:

 

4          00000100

20        00010100

 - - - - - - - - - - - - - 

WC       00010000 = 16 in decimal

 

So we can summarize as:  79.55.4.0 0.0.16.0

 

79.56.4.0/24

79.56.20.0/24

 

Same.

 

We can summarize as:  79.56.4.0 0.0.16.0

 

55        00110111

56        00111000

 - - - - - - - - - - - - - 

WC       00001111 = 15 decimal, well-known mask, would overlap several networks

 

55 and 56 cannot be summarized without overlapping other networks.

 

So the final summarization is:

 

access-list 90 permit 19.55.4.0 64.0.9.0

access-list 90 permit 79.55.4.0 0.0.16.0

access-list 90 permit 79.56.4.0 0.0.16.0

 

 

 

3.      The following hosts should be allowed to telnet into your router:

132.130.1.16
132.194.1.16
132.130.1.17
132.194.1.17
132.130.1.19
132.194.1.19
132.130.1.24
132.194.1.24
132.130.1.25
132.194.1.25
132.130.1.26
132.194.1.26
132.130.1.27
132.194.1.27
124.130.1.16
124.194.1.16
124.130.1.17
124.194.1.17
124.130.1.19
124.194.1.19
124.130.1.24
124.194.1.24
124.130.1.25
124.194.1.25
124.130.1.26
124.194.1.26
124.130.1.27
124.194.1.27

Create an ACL to use as an access-class on the VTY ports.  Use as few lines as possible.  You must use two “deny” statements in your ACL.

132.130.1.18 (deny)
132.194.1.18 (deny)

124.130.1.18 (deny)
124.194.1.18 (deny)

Solution:

 

access-list 77 deny 124.130.1.18 0.64.0.0

access-list 77 deny 132.130.1.18 0.64.0.0

access-list 77 permit 124.130.1.16 0.64.0.11

access-list 77 permit 132.130.1.16 0.64.0.11

 

Explanation:

 

First octets are 124 and 132

Second octets 130 and 194

Third octet are always 1

Fourth octets are 16,17,19,24,25,26,27 

 

124            01111100

132            10000100

 - - - - - - - - - - - - - - - -

WC            11111000 = 248 in decimal but would overlap several networks (addresses)

 

130            10000010

194            11000010

 - - - - - - - - - - - - - - - -

WC            01000000 = 64 in decimal

 

 

16              00010000

17              00010001

18              00010010 ------   WE WILL OVERLAP 18  ! and filter it later

19              00010011

 - - - - - - - - - - - - - - - -

WC            00000011 = 3 in decimal

 

 

24              00011000

25              00011001

26              00011010

27              00011011

- - - - - - - - - - - - - - - - 

WC            00000011 = 3 in decimal

 

130 and 194 on the 2nd octet  will be summarized with WC mask 64.

 

124.130.1.16

124.130.1.17

124.130.1.18 (overlapped)

124.130.1.19 

Summarized as 124.130.1.16 0.64.0.3

 

124.130.1.24

124.130.1.25

124.130.1.26

124.130.1.27

Summarized as 124.130.1.24 0.64.0.3

 

132.130.1.16

132.130.1.17

132.130.1.18 (overlapped)

132.130.1.19 

Summarized as 132.130.1.16 0.64.0.3

 

132.130.1.24

132.130.1.25

132.130.1.26

132.130.1.27

Summarized as 132.130.1.24 0.64.0.3

 

 

124.130.1.16 0.64.0.3 and 124.130.1.24 0.64.0.3 can be further summarized as 124.130.1.16 0.64.0.11 because

 

16              00010000

17              00010001

18              00010010 ------   WE WILL OVERLAP 18  ! and filter it later

19              00010011

24              00011000

25              00011001

26              00011010

27              00011011

- - - - - - - - - - - - - - - - 

WC            00001011 = 11 in decimal

 

 

132.130.1.16 0.64.0.3 and 132.130.1.24 0.64.0.3 can be further summarized as 132.130.1.16 0.64.0.11

 

The final summarization will be:

 

124.130.1.16 0.64.0.11

132.130.1.16 0.64.0.11

 

 

 

We have overlapped 4 addresses

124.130.1.18

124.194.1.18

132.130.1.18

132.194.1.18

These addresses should be summarized and denied by the ACL.

 

These can summarized as follows:

 

124.130.1.18 0.64.0.0

132.130.1.18 0.64.0.0

 

 

The access-list will be:

 

 

access-list 77 deny 124.130.1.18 0.64.0.0

access-list 77 deny 132.130.1.18 0.64.0.0

access-list 77 permit 124.130.1.16 0.64.0.11

access-list 77 permit 132.130.1.16 0.64.0.11

 

 

 

4.    You have one router configured with a prefix-list in BGP:

ip prefix-list GoodRoutes permit 192.168.0.0/15 ge 20 le 24

You want the same information configured on a different router, but you need to integrate this with your existing BGP distribute-list.  Your current BGP distribute-list is:

access-list 44 permit 150.100.0.0 0.0.0.255
access-list 44 permit 150.100.1.0 0.0.0.255
access-list 44 permit 150.100.2.0 0.0.0.255
access-list 44 permit 150.100.3.0 0.0.0.255
access-list 44 permit 150.100.4.0 0.0.0.255
access-list 44 permit 150.100.5.0 0.0.0.255
access-list 44 permit 150.100.6.0 0.0.0.255
access-list 44 permit 150.100.7.0 0.0.0.255
access-list 44 permit 150.100.8.0 0.0.0.255
access-list 44 permit 150.100.9.0 0.0.0.255
access-list 44 permit 150.100.10.0 0.0.0.255
access-list 44 permit 150.100.11.0 0.0.0.255
access-list 44 permit 150.100.12.0 0.0.0.255
access-list 44 permit 150.100.13.0 0.0.0.255
access-list 44 permit 150.100.14.0 0.0.0.255
access-list 44 permit 150.100.15.0 0.0.0.255

Create a new BGP distribute-list in as few lines as possible.

 

The 16 existing networks can be summarized as

access-list 44 permit 150.100.0.0 0.0.15.0

The prefix-list 

ip prefix-list GoodRoutes permit 192.168.0.0/15 ge 20 le 24

means the 15 most significant bits must match , the 16th bit can be 0 or 1, so the second octet can be 168 or 169.

The prefix-list covers /20 /21 /22 /23 and /24 networks.

/24 networks:

192.168.0.0/24 --- 192.169.255.0/24 These can be covered with 192.168.0.0 0.1.255.0

/23 networks:

192.168.0.0/23 --- 192.169.254.0/23 These can be covered with 192.168.0.0 0.1.254.0

/22 networks:

192.168.0.0/22 --- 192.169.252.0/24 These can be covered with 192.168.0.0 0.1.252.0

/21 networks:

192.168.0.0/21 --- 192.169.248.0/21 These can be covered with 192.168.0.0 0.1.248.0

/20 networks:

192.168.0.0/22 --- 192.169.240.0/22 These can be covered with 192.168.0.0 0.0.240.0

 

Access-list matching logic differs from prefix-list matching logic: only exact matches count.

So these networks cannot be summarized further.

 

The new final ACL will be:

access-list 44 permit 150.100.0.0 0.0.15.0

access-list 44 permit 192.168.0.0 0.1.255.0

access-list 44 permit 192.168.0.0 0.1.254.0

access-list 44 permit 192.168.0.0 0.1.252.0

access-list 44 permit 192.168.0.0 0.1.248.0

access-list 44 permit 192.168.0.0 0.1.240.0

 

 

 

 

Best regards,

Csaba KISS
Email: csaba.kiss@nextiraone.hu</description>
		<content:encoded><![CDATA[<p>One more answer had slipped in which I missed:</p>
<p>Dear Scott,</p>
<p>The solutions for the binary math2 brainteasers:</p>
<p>1.       1.   You have hosts on 150.100.32.0/24.  Make sure the following addresses are not allowed to access any even-numbered server in the second-half of your IP range.  All other access should be allowed.</p>
<p>access-list 100 deny ip 180.34.80.133 0.16.128.96 150.100.32.128 0.0.0.126</p>
<p>access-list 100 permit ip any any</p>
<p>Explanation:</p>
<p>Summarizing the source addresses:</p>
<p>We have 16 ClassB addresses. First octet is the same for each. 2nd, 3rd, 4th octet differs.</p>
<p>We can create 4 piece of subnet-bundle with 4 subnet in each, where subnets have 3 octet in common:</p>
<p>1st group</p>
<p>180.34.80.133</p>
<p>180.34.80.165</p>
<p>180.34.80.197</p>
<p>180.34.80.229</p>
<p>2nd group</p>
<p>180.34.208.133</p>
<p>180.34.208.165</p>
<p>180.34.208.197</p>
<p>180.34.208.229</p>
<p>3rd group</p>
<p>180.50.80.133</p>
<p>180.50.80.165</p>
<p>180.50.80.197</p>
<p>180.50.80.229</p>
<p>4th group</p>
<p>180.50.208.133</p>
<p>180.50.208.165</p>
<p>180.50.208.197</p>
<p>180.50.208.229</p>
<p>3 different octets mean 3 places where we can summarize.</p>
<p>2nd octets are </p>
<p>34</p>
<p>50</p>
<p>In decimal.</p>
<p>2nd octets are</p>
<p>00100010</p>
<p>00110010</p>
<p>In binary</p>
<p>The bitstrings have 7 bits in common. Where bits are common, we „dont care” in the WC mask so bits will be 0.</p>
<p>The summarized bitstring is</p>
<p>00010000 in binary, that is 16 in decimal.</p>
<p>3rd octet are</p>
<p>80</p>
<p>208</p>
<p>In decimal</p>
<p>3rd octets are</p>
<p>01010000</p>
<p>11010000</p>
<p>In binary</p>
<p>The bitstrings have 7 bits in common. Where bits are common, we „dont care” in the WC mask so bits will be 0.</p>
<p>The summarized bitstring is</p>
<p>10000000</p>
<p>In binary, that is 128 in decimal.</p>
<p>4th octets are</p>
<p>133</p>
<p>165</p>
<p>197</p>
<p>229</p>
<p>In decimal</p>
<p>4th octet are</p>
<p>10000101</p>
<p>10100101</p>
<p>11000101</p>
<p>11100101</p>
<p>The bitstrings have 6 bits in common. Where bits are common, we „dont care” in the WC mask so bits will be 0.</p>
<p>The summarized bitstring is</p>
<p>01100000</p>
<p>In binary, that is 96 in decimal.</p>
<p>The first 8 address can be summarized as follows:</p>
<p>1st group</p>
<p>180.34.80.133</p>
<p>180.34.80.165</p>
<p>180.34.80.197</p>
<p>180.34.80.229</p>
<p>2nd group</p>
<p>180.34.208.133</p>
<p>180.34.208.165</p>
<p>180.34.208.197</p>
<p>180.34.208.229</p>
<p>First two octet are common so WC mask will be 0.</p>
<p>Third octet are 80 and 208. These can covered with WC mask 128.</p>
<p>4th octets can be covered with WC mask 96.</p>
<p>The summarization of the 8 addresses is   180.34.80.133 0.0.128.96</p>
<p>The second 8 address can be summarized as follows:</p>
<p>1st group</p>
<p>180.50.80.133</p>
<p>180.50.80.165</p>
<p>180.50.80.197</p>
<p>180.50.80.229</p>
<p>2nd group</p>
<p>180.50.208.133</p>
<p>180.50.208.165</p>
<p>180.50.208.197</p>
<p>180.50.208.229</p>
<p>First two octet are common so WC mask will be 0.</p>
<p>Third octet are 80 and 208. These can covered with WC mask 128.</p>
<p>4th octets can be covered with WC mask 96.</p>
<p>The summarization of the 8 addresses is   180.50.80.133 0.0.128.96</p>
<p>The first and the second summarizations:</p>
<p>180.34.80.133 0.0.128.96</p>
<p>180.50.80.133 0.0.128.96</p>
<p>Only the second octets are different, and can be covered with WC mask 16 (as explained earlier)</p>
<p>So the full summarization of source addresses is:</p>
<p>180.34.80.133 0.16.128.96</p>
<p>180.34.80.133</p>
<p>180.34.80.165</p>
<p>180.34.80.197</p>
<p>180.34.80.229</p>
<p>180.34.208.133</p>
<p>180.34.208.165</p>
<p>180.34.208.197</p>
<p>180.34.208.229</p>
<p>180.50.80.133</p>
<p>180.50.80.165</p>
<p>180.50.80.197</p>
<p>180.50.80.229</p>
<p>180.50.208.133</p>
<p>180.50.208.165</p>
<p>180.50.208.197</p>
<p>180.50.208.229</p>
<p>3 octets differ.</p>
<p>We can summarize all of them.</p>
<p>34              00100010</p>
<p>50              00110010</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; -</p>
<p>WC            00010000 = 16 in decimal</p>
<p>80              01010000</p>
<p>208            11010000</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; -</p>
<p>WC            10000000 = 128 in decimal</p>
<p>133            10000101</p>
<p>165            10100101</p>
<p>197            11000101</p>
<p>229            11100101</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; -</p>
<p>WC            01100000 = 96 in decimal</p>
<p>180.34.80.133</p>
<p>180.34.80.165</p>
<p>180.34.80.197</p>
<p>180.34.80.229</p>
<p>Summarized as 180.34.80.133 0.0.0.96</p>
<p>180.34.208.133</p>
<p>180.34.208.165</p>
<p>180.34.208.197</p>
<p>180.34.208.229</p>
<p>Summarized as 180.34.208.133 0.0.0.96</p>
<p>180.50.80.133</p>
<p>180.50.80.165</p>
<p>180.50.80.197</p>
<p>180.50.80.229</p>
<p>Summarized as 180.50.80.133 0.0.0.96</p>
<p>180.50.208.133</p>
<p>180.50.208.165</p>
<p>180.50.208.197</p>
<p>180.50.208.229</p>
<p>Summarized as 180.50.208.133 0.0.0.96</p>
<p>180.34.80.133 0.0.0.96 and 180.34.208.133 0.0.0.96 can be further summarized as 180.34.80.133 0.0.128.96 (summarizing the 3rd octets).</p>
<p>180.50.80.133 0.0.0.96 and 180.50.208.133 0.0.0.96 can be further summarized as 180.50.80.133 0.0.128.96 (summarizing the 3rd octets).</p>
<p>180.34.80.133 0.0.128.96 and 180.50.80.133 0.0.128.96 can be further summarized, summarizing the 2nd octets:  180.34.80.133 0.16.128.96</p>
<p>Destination addresses are 150.100.32.128 – 150.100.32.254  in the 150.100.32.0/24 subnet</p>
<p>The last octet of these addresses:</p>
<p>10000000</p>
<p>10000010</p>
<p>10000100</p>
<p>&#8230;</p>
<p>11111110</p>
<p>The most significant bits are always 1 the leasts are always 0. Common bits are 0 in the WC mask, so WC mask will be 01111110 in binary, 126 in decimal. The even-numbered servers in upper half of the subnet 150.100.32.0/24 are covered with 150.100.32.128 0.0.0.126 </p>
<p>The access-list will be:</p>
<p>access-list 100 deny ip 180.34.80.133 0.16.128.96 150.100.32.128 0.0.0.126</p>
<p>access-list 100 permit ip any any</p>
<p>2.     Second task</p>
<p>access-list 90 permit 19.55.4.0 64.0.9.0</p>
<p>access-list 90 permit 79.55.4.0 0.0.16.0</p>
<p>access-list 90 permit 79.56.4.0 0.0.16.0</p>
<p>Expl.</p>
<p>19.55.4.0/24</p>
<p>19.55.5.0/24</p>
<p>19.55.12.0/24</p>
<p>19.55.13.0/24</p>
<p>4          00000100</p>
<p>5          00000101</p>
<p>12        00001100</p>
<p>13        00001101</p>
<p>- &#8211; - &#8211; - &#8211; -  &#8211; - &#8211; - &#8211; - </p>
<p>WC       00001001</p>
<p>These 4 networks can be summarized as  19.55.4.0 0.0.9.0</p>
<p>83.55.4.0/24</p>
<p>83.55.5.0/24</p>
<p>83.55.12.0/24</p>
<p>83.55.13.0/24</p>
<p>4          00000100</p>
<p>5          00000101</p>
<p>12        00001100</p>
<p>13        00001101</p>
<p>- &#8211; - &#8211; - &#8211; -  &#8211; - &#8211; - &#8211; - </p>
<p>WC       00001001</p>
<p>These 4 networks can be summarized as  83.55.4.0 0.0.9.0</p>
<p>The 2 summarized networks are</p>
<p>19.55.4.0 0.0.9.0</p>
<p>83.55.4.0 0.0.9.0</p>
<p>Only the first octet differs. Can be summarized:</p>
<p>19        00010011</p>
<p>83        01010011</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; </p>
<p>WC       01000000  = 64 in decimal</p>
<p>So we can further summarize as:           19.55.4.0 64.0.9.0</p>
<p>79.55.4.0/24</p>
<p>79.55.20.0/24</p>
<p>3rd octet differs, we can summarize as follows:</p>
<p>4          00000100</p>
<p>20        00010100</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; </p>
<p>WC       00010000 = 16 in decimal</p>
<p>So we can summarize as:  79.55.4.0 0.0.16.0</p>
<p>79.56.4.0/24</p>
<p>79.56.20.0/24</p>
<p>Same.</p>
<p>We can summarize as:  79.56.4.0 0.0.16.0</p>
<p>55        00110111</p>
<p>56        00111000</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; </p>
<p>WC       00001111 = 15 decimal, well-known mask, would overlap several networks</p>
<p>55 and 56 cannot be summarized without overlapping other networks.</p>
<p>So the final summarization is:</p>
<p>access-list 90 permit 19.55.4.0 64.0.9.0</p>
<p>access-list 90 permit 79.55.4.0 0.0.16.0</p>
<p>access-list 90 permit 79.56.4.0 0.0.16.0</p>
<p>3.      The following hosts should be allowed to telnet into your router:</p>
<p>132.130.1.16<br />
132.194.1.16<br />
132.130.1.17<br />
132.194.1.17<br />
132.130.1.19<br />
132.194.1.19<br />
132.130.1.24<br />
132.194.1.24<br />
132.130.1.25<br />
132.194.1.25<br />
132.130.1.26<br />
132.194.1.26<br />
132.130.1.27<br />
132.194.1.27<br />
124.130.1.16<br />
124.194.1.16<br />
124.130.1.17<br />
124.194.1.17<br />
124.130.1.19<br />
124.194.1.19<br />
124.130.1.24<br />
124.194.1.24<br />
124.130.1.25<br />
124.194.1.25<br />
124.130.1.26<br />
124.194.1.26<br />
124.130.1.27<br />
124.194.1.27</p>
<p>Create an ACL to use as an access-class on the VTY ports.  Use as few lines as possible.  You must use two “deny” statements in your ACL.</p>
<p>132.130.1.18 (deny)<br />
132.194.1.18 (deny)</p>
<p>124.130.1.18 (deny)<br />
124.194.1.18 (deny)</p>
<p>Solution:</p>
<p>access-list 77 deny 124.130.1.18 0.64.0.0</p>
<p>access-list 77 deny 132.130.1.18 0.64.0.0</p>
<p>access-list 77 permit 124.130.1.16 0.64.0.11</p>
<p>access-list 77 permit 132.130.1.16 0.64.0.11</p>
<p>Explanation:</p>
<p>First octets are 124 and 132</p>
<p>Second octets 130 and 194</p>
<p>Third octet are always 1</p>
<p>Fourth octets are 16,17,19,24,25,26,27 </p>
<p>124            01111100</p>
<p>132            10000100</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; -</p>
<p>WC            11111000 = 248 in decimal but would overlap several networks (addresses)</p>
<p>130            10000010</p>
<p>194            11000010</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; -</p>
<p>WC            01000000 = 64 in decimal</p>
<p>16              00010000</p>
<p>17              00010001</p>
<p>18              00010010 &#8212;&#8212;   WE WILL OVERLAP 18  ! and filter it later</p>
<p>19              00010011</p>
<p> &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; -</p>
<p>WC            00000011 = 3 in decimal</p>
<p>24              00011000</p>
<p>25              00011001</p>
<p>26              00011010</p>
<p>27              00011011</p>
<p>- &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; </p>
<p>WC            00000011 = 3 in decimal</p>
<p>130 and 194 on the 2nd octet  will be summarized with WC mask 64.</p>
<p>124.130.1.16</p>
<p>124.130.1.17</p>
<p>124.130.1.18 (overlapped)</p>
<p>124.130.1.19 </p>
<p>Summarized as 124.130.1.16 0.64.0.3</p>
<p>124.130.1.24</p>
<p>124.130.1.25</p>
<p>124.130.1.26</p>
<p>124.130.1.27</p>
<p>Summarized as 124.130.1.24 0.64.0.3</p>
<p>132.130.1.16</p>
<p>132.130.1.17</p>
<p>132.130.1.18 (overlapped)</p>
<p>132.130.1.19 </p>
<p>Summarized as 132.130.1.16 0.64.0.3</p>
<p>132.130.1.24</p>
<p>132.130.1.25</p>
<p>132.130.1.26</p>
<p>132.130.1.27</p>
<p>Summarized as 132.130.1.24 0.64.0.3</p>
<p>124.130.1.16 0.64.0.3 and 124.130.1.24 0.64.0.3 can be further summarized as 124.130.1.16 0.64.0.11 because</p>
<p>16              00010000</p>
<p>17              00010001</p>
<p>18              00010010 &#8212;&#8212;   WE WILL OVERLAP 18  ! and filter it later</p>
<p>19              00010011</p>
<p>24              00011000</p>
<p>25              00011001</p>
<p>26              00011010</p>
<p>27              00011011</p>
<p>- &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; - &#8211; </p>
<p>WC            00001011 = 11 in decimal</p>
<p>132.130.1.16 0.64.0.3 and 132.130.1.24 0.64.0.3 can be further summarized as 132.130.1.16 0.64.0.11</p>
<p>The final summarization will be:</p>
<p>124.130.1.16 0.64.0.11</p>
<p>132.130.1.16 0.64.0.11</p>
<p>We have overlapped 4 addresses</p>
<p>124.130.1.18</p>
<p>124.194.1.18</p>
<p>132.130.1.18</p>
<p>132.194.1.18</p>
<p>These addresses should be summarized and denied by the ACL.</p>
<p>These can summarized as follows:</p>
<p>124.130.1.18 0.64.0.0</p>
<p>132.130.1.18 0.64.0.0</p>
<p>The access-list will be:</p>
<p>access-list 77 deny 124.130.1.18 0.64.0.0</p>
<p>access-list 77 deny 132.130.1.18 0.64.0.0</p>
<p>access-list 77 permit 124.130.1.16 0.64.0.11</p>
<p>access-list 77 permit 132.130.1.16 0.64.0.11</p>
<p>4.    You have one router configured with a prefix-list in BGP:</p>
<p>ip prefix-list GoodRoutes permit 192.168.0.0/15 ge 20 le 24</p>
<p>You want the same information configured on a different router, but you need to integrate this with your existing BGP distribute-list.  Your current BGP distribute-list is:</p>
<p>access-list 44 permit 150.100.0.0 0.0.0.255<br />
access-list 44 permit 150.100.1.0 0.0.0.255<br />
access-list 44 permit 150.100.2.0 0.0.0.255<br />
access-list 44 permit 150.100.3.0 0.0.0.255<br />
access-list 44 permit 150.100.4.0 0.0.0.255<br />
access-list 44 permit 150.100.5.0 0.0.0.255<br />
access-list 44 permit 150.100.6.0 0.0.0.255<br />
access-list 44 permit 150.100.7.0 0.0.0.255<br />
access-list 44 permit 150.100.8.0 0.0.0.255<br />
access-list 44 permit 150.100.9.0 0.0.0.255<br />
access-list 44 permit 150.100.10.0 0.0.0.255<br />
access-list 44 permit 150.100.11.0 0.0.0.255<br />
access-list 44 permit 150.100.12.0 0.0.0.255<br />
access-list 44 permit 150.100.13.0 0.0.0.255<br />
access-list 44 permit 150.100.14.0 0.0.0.255<br />
access-list 44 permit 150.100.15.0 0.0.0.255</p>
<p>Create a new BGP distribute-list in as few lines as possible.</p>
<p>The 16 existing networks can be summarized as</p>
<p>access-list 44 permit 150.100.0.0 0.0.15.0</p>
<p>The prefix-list </p>
<p>ip prefix-list GoodRoutes permit 192.168.0.0/15 ge 20 le 24</p>
<p>means the 15 most significant bits must match , the 16th bit can be 0 or 1, so the second octet can be 168 or 169.</p>
<p>The prefix-list covers /20 /21 /22 /23 and /24 networks.</p>
<p>/24 networks:</p>
<p>192.168.0.0/24 &#8212; 192.169.255.0/24 These can be covered with 192.168.0.0 0.1.255.0</p>
<p>/23 networks:</p>
<p>192.168.0.0/23 &#8212; 192.169.254.0/23 These can be covered with 192.168.0.0 0.1.254.0</p>
<p>/22 networks:</p>
<p>192.168.0.0/22 &#8212; 192.169.252.0/24 These can be covered with 192.168.0.0 0.1.252.0</p>
<p>/21 networks:</p>
<p>192.168.0.0/21 &#8212; 192.169.248.0/21 These can be covered with 192.168.0.0 0.1.248.0</p>
<p>/20 networks:</p>
<p>192.168.0.0/22 &#8212; 192.169.240.0/22 These can be covered with 192.168.0.0 0.0.240.0</p>
<p>Access-list matching logic differs from prefix-list matching logic: only exact matches count.</p>
<p>So these networks cannot be summarized further.</p>
<p>The new final ACL will be:</p>
<p>access-list 44 permit 150.100.0.0 0.0.15.0</p>
<p>access-list 44 permit 192.168.0.0 0.1.255.0</p>
<p>access-list 44 permit 192.168.0.0 0.1.254.0</p>
<p>access-list 44 permit 192.168.0.0 0.1.252.0</p>
<p>access-list 44 permit 192.168.0.0 0.1.248.0</p>
<p>access-list 44 permit 192.168.0.0 0.1.240.0</p>
<p>Best regards,</p>
<p>Csaba KISS<br />
Email: <a href="mailto:csaba.kiss@nextiraone.hu">csaba.kiss@nextiraone.hu</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Morris, CCIE #4713</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-11694</link>
		<dc:creator>Scott Morris, CCIE #4713</dc:creator>
		<pubDate>Wed, 05 Nov 2008 18:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-11694</guid>
		<description>The contest part is now closed.  Comments should be approved and appearing here.  

Next I get to go through them all, and see who won!

I will also be posting the answers fairly shortly.

Scott</description>
		<content:encoded><![CDATA[<p>The contest part is now closed.  Comments should be approved and appearing here.  </p>
<p>Next I get to go through them all, and see who won!</p>
<p>I will also be posting the answers fairly shortly.</p>
<p>Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shai</title>
		<link>http://blog.ine.com/2008/11/03/binary-math-part-ii/comment-page-1/#comment-11676</link>
		<dc:creator>Shai</dc:creator>
		<pubDate>Wed, 05 Nov 2008 15:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=324#comment-11676</guid>
		<description>hello

i cannot understand something - every example here have bunch of /24 subnets - yet all access-lists have .0 as the last octet - why is that ? shouldn&#039;t it be .255 for all bits ?


P.S.
sorry if the answer was implied somewhere and i missed it somehow ...

thanks
Shai</description>
		<content:encoded><![CDATA[<p>hello</p>
<p>i cannot understand something &#8211; every example here have bunch of /24 subnets &#8211; yet all access-lists have .0 as the last octet &#8211; why is that ? shouldn&#8217;t it be .255 for all bits ?</p>
<p>P.S.<br />
sorry if the answer was implied somewhere and i missed it somehow &#8230;</p>
<p>thanks<br />
Shai</p>
]]></content:encoded>
	</item>
</channel>
</rss>
