<?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"
	>
<channel>
	<title>Comments on: How do I compute complex wildcard masks for access-lists?</title>
	<atom:link href="http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/</link>
	<description>Helping you become a Cisco Certified Internetwork Expert</description>
	<pubDate>Fri, 05 Sep 2008 15:02:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Phil</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-6650</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Mon, 25 Aug 2008 18:01:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-6650</guid>
		<description>Hi

I read the article from Brian McGahan under http://www.internetworkexpert.com/resources/01700370.htm

I can not follow his wildcard calculation (xor part) in the 2nd example. The calculation is

xor of

00001010 00000000 00000000 00000000
00001010 00000100 00000000 00000000
00001010 00100000 00000000 00000000
00001010 00100100 00000000 00000000

00000000 00100100 00000000 00000000 (his result)

00000000 00000000 00000000 00000000 (my result)

Why does 1 xor 1 become 1 in his calculation?

Any help or insight highly appreciated.

cheers</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>I read the article from Brian McGahan under <a href="http://www.internetworkexpert.com/resources/01700370.htm" rel="nofollow">http://www.internetworkexpert.com/resources/01700370.htm</a></p>
<p>I can not follow his wildcard calculation (xor part) in the 2nd example. The calculation is</p>
<p>xor of</p>
<p>00001010 00000000 00000000 00000000<br />
00001010 00000100 00000000 00000000<br />
00001010 00100000 00000000 00000000<br />
00001010 00100100 00000000 00000000</p>
<p>00000000 00100100 00000000 00000000 (his result)</p>
<p>00000000 00000000 00000000 00000000 (my result)</p>
<p>Why does 1 xor 1 become 1 in his calculation?</p>
<p>Any help or insight highly appreciated.</p>
<p>cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harmik</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-4521</link>
		<dc:creator>Harmik</dc:creator>
		<pubDate>Sun, 20 Jul 2008 01:21:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-4521</guid>
		<description>Thanks All

I just figured out how to do all this

deny ip 192.168.1.0 0.0.0.255 any
deny ip 192.168.3.0 0.0.252.255 any
deny ip any 192.168.1.0 0.0.0.255
deny ip any 192.168.3.0 0.0.252.255
permit ip 192.168.0.0 0.0.0.255 any
permit ip 192.168.2.0 0.0.0.255 any

======its working for me now....

good news....</description>
		<content:encoded><![CDATA[<p>Thanks All</p>
<p>I just figured out how to do all this</p>
<p>deny ip 192.168.1.0 0.0.0.255 any<br />
deny ip 192.168.3.0 0.0.252.255 any<br />
deny ip any 192.168.1.0 0.0.0.255<br />
deny ip any 192.168.3.0 0.0.252.255<br />
permit ip 192.168.0.0 0.0.0.255 any<br />
permit ip 192.168.2.0 0.0.0.255 any</p>
<p>======its working for me now&#8230;.</p>
<p>good news&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harmik</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-4520</link>
		<dc:creator>Harmik</dc:creator>
		<pubDate>Sun, 20 Jul 2008 01:00:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-4520</guid>
		<description>Hi All

I am new to this configuring cisco router. the scenario is, I want to use access list.

In ACL, I want to permit only ip range 192.168.0.0 - 192.168.0.255
192.168.2.0 - 192.168.2.255

and deny the following

deny 192.168.1.0 - 192.168.1.255
deny 192.168.3.0 - 192.168.255.255</description>
		<content:encoded><![CDATA[<p>Hi All</p>
<p>I am new to this configuring cisco router. the scenario is, I want to use access list.</p>
<p>In ACL, I want to permit only ip range 192.168.0.0 - 192.168.0.255<br />
192.168.2.0 - 192.168.2.255</p>
<p>and deny the following</p>
<p>deny 192.168.1.0 - 192.168.1.255<br />
deny 192.168.3.0 - 192.168.255.255</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian McGahan, CCIE #8593</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-3653</link>
		<dc:creator>Brian McGahan, CCIE #8593</dc:creator>
		<pubDate>Wed, 25 Jun 2008 15:11:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-3653</guid>
		<description>The point is just to show the binary logic of how the wildcard is derived.  The practical implementation of this would be to aggregate multiple access list lines into a single statement in order to save processing power.  Remember that for a traffic filter the router has to check each entry in a top down fashion until a match occurs.  For example if you are doing "bogon" filtering, the access-list is best implemented as an aggregated list.  You can see more information about this here:

http://www.cymru.com/Documents/bogon-dd.html

Look at Cisco ACL Aggregated and Cisco ACL Non-Aggregated</description>
		<content:encoded><![CDATA[<p>The point is just to show the binary logic of how the wildcard is derived.  The practical implementation of this would be to aggregate multiple access list lines into a single statement in order to save processing power.  Remember that for a traffic filter the router has to check each entry in a top down fashion until a match occurs.  For example if you are doing &#8220;bogon&#8221; filtering, the access-list is best implemented as an aggregated list.  You can see more information about this here:</p>
<p><a href="http://www.cymru.com/Documents/bogon-dd.html" rel="nofollow">http://www.cymru.com/Documents/bogon-dd.html</a></p>
<p>Look at Cisco ACL Aggregated and Cisco ACL Non-Aggregated</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Raymond</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-3633</link>
		<dc:creator>Steve Raymond</dc:creator>
		<pubDate>Mon, 23 Jun 2008 21:31:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-3633</guid>
		<description>While this is interesting, what is a practical application of that broad an ACL?  e.g., the example 8.20.20.8 34.10.10.34 covers any IP addresses starting with the 1st octet like:
8
9
10
11
12
13
14
15
24
25
26
27
28
29
30
31
40
41

And the 2nd &#38; 3rd octet:
20
21
22
23
28
29
30
31
52
53
54
55
60
61
62
63
84
85

Don't get me wrong, I like the xor description and explanation.  But I don't see where this would be useful in IOS ACLs?

Thanks!</description>
		<content:encoded><![CDATA[<p>While this is interesting, what is a practical application of that broad an ACL?  e.g., the example 8.20.20.8 34.10.10.34 covers any IP addresses starting with the 1st octet like:<br />
8<br />
9<br />
10<br />
11<br />
12<br />
13<br />
14<br />
15<br />
24<br />
25<br />
26<br />
27<br />
28<br />
29<br />
30<br />
31<br />
40<br />
41</p>
<p>And the 2nd &amp; 3rd octet:<br />
20<br />
21<br />
22<br />
23<br />
28<br />
29<br />
30<br />
31<br />
52<br />
53<br />
54<br />
55<br />
60<br />
61<br />
62<br />
63<br />
84<br />
85</p>
<p>Don&#8217;t get me wrong, I like the xor description and explanation.  But I don&#8217;t see where this would be useful in IOS ACLs?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ziv</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-3622</link>
		<dc:creator>Ziv</dc:creator>
		<pubDate>Mon, 23 Jun 2008 08:48:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-3622</guid>
		<description>I'm working with Cisco and ACLs for nearly 10 years and I'd never needed to calculate so complex wildcards, so I don't know, perhaps I've never met complex networks, but I think that if you're in need for so comlex wildcards it must have something to do with bad network designing...</description>
		<content:encoded><![CDATA[<p>I&#8217;m working with Cisco and ACLs for nearly 10 years and I&#8217;d never needed to calculate so complex wildcards, so I don&#8217;t know, perhaps I&#8217;ve never met complex networks, but I think that if you&#8217;re in need for so comlex wildcards it must have something to do with bad network designing&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Roman</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-3477</link>
		<dc:creator>George Roman</dc:creator>
		<pubDate>Thu, 05 Jun 2008 17:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-3477</guid>
		<description>One problem, 

As far as i now this "XOR" function is not the logical XOR when you try to compute more than 2  "inputs"(3 ips for example). In this last case the result of the XOR operation would be different (you would calculate xor between first 2 inputs and the result will come into play with the 3-rd input). 
So by the correct XOR logic the result of 3 IPs would not give you the correct wildcard mask.</description>
		<content:encoded><![CDATA[<p>One problem, </p>
<p>As far as i now this &#8220;XOR&#8221; function is not the logical XOR when you try to compute more than 2  &#8220;inputs&#8221;(3 ips for example). In this last case the result of the XOR operation would be different (you would calculate xor between first 2 inputs and the result will come into play with the 3-rd input).<br />
So by the correct XOR logic the result of 3 IPs would not give you the correct wildcard mask.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: trilok</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-1098</link>
		<dc:creator>trilok</dc:creator>
		<pubDate>Fri, 18 Apr 2008 12:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-1098</guid>
		<description>I won't agree with the solution provided as to combine a pair of ip address  with wild card mask the mandatory thing is only 1 bit has to vary while we compare that pair of addresses or else no way we can combine those IP addresses if they are are having more than 1 bit varying in between them.

The range of IP addresses that an accesslist applies is purely based on number of 1's in the wild card mask. i.e range = 2^(number of 1's in the wild card mask)

If its failing then it will apply to some other addresses apart from the desired one's</description>
		<content:encoded><![CDATA[<p>I won&#8217;t agree with the solution provided as to combine a pair of ip address  with wild card mask the mandatory thing is only 1 bit has to vary while we compare that pair of addresses or else no way we can combine those IP addresses if they are are having more than 1 bit varying in between them.</p>
<p>The range of IP addresses that an accesslist applies is purely based on number of 1&#8217;s in the wild card mask. i.e range = 2^(number of 1&#8217;s in the wild card mask)</p>
<p>If its failing then it will apply to some other addresses apart from the desired one&#8217;s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-1047</link>
		<dc:creator>D</dc:creator>
		<pubDate>Tue, 08 Apr 2008 14:26:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-1047</guid>
		<description>Also you can use the calc in windows (scientific) AND/XOR function to compute the wild card masks.</description>
		<content:encoded><![CDATA[<p>Also you can use the calc in windows (scientific) AND/XOR function to compute the wild card masks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Day 4 of Week 2 &#171; Richard Bannister&#8217;s CCIE Blog</title>
		<link>http://blog.internetworkexpert.com/2007/12/26/q-how-do-i-compute-complex-wildcard-masks-for-access-lists/#comment-615</link>
		<dc:creator>Day 4 of Week 2 &#171; Richard Bannister&#8217;s CCIE Blog</dc:creator>
		<pubDate>Thu, 06 Mar 2008 21:32:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internetworkexpert.com/?p=7#comment-615</guid>
		<description>[...] quite tedious so NAT added a bit of interest to it.  Another item that gained my interest is a post by Brian McGahan on the Internetwork Experts blog detailing how to work out the most specific match [...]</description>
		<content:encoded><![CDATA[<p>[...] quite tedious so NAT added a bit of interest to it.  Another item that gained my interest is a post by Brian McGahan on the Internetwork Experts blog detailing how to work out the most specific match [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
