🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dcom.sys.cisco
Article #1782

extended access-lists

#1782
From: Brian H. Powell
Date: Thu, 20 Jun 1991 21:44
23 lines
1440 bytes
     I'm new to the cisco router, so please bear with me.
     I've got some questions about extended access-lists, particularly about
the example in the 8.2 manual on pp. 5-26 and 5-27.  The example concerns
allowing all outbound connections, but restricting inbound connections only
to an SMTP port on a particular machine.
     I'll type in the outgoing side of their example, which is what I'm
curious about:

access-list 101 permit tcp 128.88.0.0 0.0.255.255 0.0.0.0 255.255.255.255
access-list 101 deny icmp 128.88.0.0 0.0.255.255 0.0.0.0 255.255.255.255

     The first line makes sense, of course.  Why, though, deny outgoing
icmp?
     Also, in this example, the inbound traffic is limited to source ports
greater than 1023.  Is this also appropriate for NNTP, FTP, DNS, and the
other sets of things we typically want to allow?  (Perhaps what I'm asking
is what are the various incantations for a typical secure setup where you
don't want to allow incoming telnet, rsh, etc., and restrict certain other
services (such as mail & news) to a specific host.)
     Thanks.

Brian
Technical Details
Message-ID: <24746@natinst.natinst.com>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!balkan!natinst!brian

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!balkan!natinst!brian
From: brian@natinst.com (Brian H. Powell)
Newsgroups: comp.dcom.sys.cisco
Subject: extended access-lists
Message-ID: <24746@natinst.natinst.com>
Date: 20 Jun 91 21:44:12 GMT
Organization: National Instruments, Austin, TX
Lines: 23