Access list

From: Joseph D. Phillips (jphillips@ufcwdrugtrust.org)
Date: Wed Mar 31 2004 - 21:18:20 GMT-3


Thanks for the advice.

In the real world don't they use calculators?

-----Original Message-----
From: Richard L. Pickard [mailto:nettable_walker@comcast.net]
Sent: Wednesday, March 31, 2004 16:23
To: Joseph D. Phillips
Subject: RE: Access list

Don't waste a lot of time on this type of stuff

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Joseph D. Phillips
Sent: Wednesday, March 31, 2004 5:52 PM
To: Group Study (E-mail)
Subject: Access list

I've spent the entire afternoon on a single access list and still can't
figure out the logic. I've looked up articles, and converted everything to
binary and still can't make sense of this.

Given the following networks (last two octets relevant), I need to block
them all in as few lines as possible. Some of you people can do this in your
heads. Simpletons like me, however, can't.

These are the networks:

1.2
1.10
1.18
1.26
3.2
3.10
3.18
3.26

In binary it looks like:

1 2 00000001 00000010
1 10 00000001 00001010
1 18 00000001 00010010
1 26 00000001 00011010
3 2 00000011 00000010
3 10 00000011 00001010
3 18 00000011 00010010
3 26 00000011 00011010

What do I do after that? I know how to summarize them all into one
statement, but I need specific deny statements that only apply to the
networks to be blocked and to none else.



This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:50 GMT-3