rapolicy(1) [debian man page]
RAPOLICY(1) General Commands Manual RAPOLICY(1) NAME
rapolicy - compare a argus(8) data file/stream against a Cisco Access Control List. COPYRIGHT
Copyright (c) 2000-2003 QoSient. All rights reserved. SYNOPSIS
rapolicy -r argus-file [ra options] DESCRIPTION
Rapolicy reads argus data from an argus-file list, and tests the argus data stream against a Cisco access control list configuration file, printing out records that represent activity that would violate the policy. Rapolicy can be used to indicate access control violations, as well as test new access control definitions prior to installing them in a router. OPTIONS
Rapolicy, like all ra based clients, supports a large number of options. Options that have specific meaning to rapolicy are: -f <Cisco ACL file> Print records that violate the policy. -D 0 (default) Print records that violate the policy. -D 1 Print records and the violated ruleset. -D 2 Print all records and the ruleset that matched. See ra(1) for a complete description of ra options. EXAMPLE INVOCATION
rapolicy -r argus.file CISCO ACL SYNTAX
There does not seem to be authoritative Cisco-ACL-Documentation, nor ACL syntax standardization. Because Cisco has been know to improve its ACL rules syntax, rapolicy is known to work with Cisco ACL router defintions up to July, 2002. A Cisco ACL configuration file consists of a collection of any number of ACL statements, each on a separte line. The syntax of an ACL statement is: ACL = "access-list" ID ACTION PROTOCOL SRC DST NOTIFICATION ID = Number ACTION = permit | deny PROTO = protocol name | protocol number SRC | DST = ADDRESS [PORTMATCH] ADDRESS = any | host HOSTADDR | HOSTADDR HOSTMASK HOSTADDR = ipV4 address HOSTMASK = matching-mask PORTMATCH = PORTOP PORTNUM | range PORTRANGE PORTOP = eq | lt | gt | neq | established PORTRANGE = PORTNUM PORTNUM PORTNUM = TCP or UDP port value (unsigned decimal from 0 to 65535) EXAMPLE CONFIGURATION
This example Cisco Access Control List configuration is provided as an example only. No effort has been made to verify that this example Access Control List enforces a useful access control policy of any kind. #allow www-traffic to webserver access-list 102 permit tcp any 193.174.13.99 0.0.0.0 eq 80 #allow ftp control connection to server access-list 102 permit tcp any 193.174.13.99 0.0.0.0 eq 21 #allow normal ftp access-list 102 permit tcp any 193.174.13.99 0.0.0.0 eq 20 #allow ftp passive conncetions in portrange 10000 to 10500 access-list 102 permit tcp any host 193.174.13.99 range 10000 10500 #dummy example access-list 102 permit tcp host 193.174.13.1 eq 12345 host 193.174.13.2 range 12345 23456 #deny the rest access-list 102 deny tcp any any #same thing in other words: access-list 102 deny tcp 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255 AUTHORS
Carter Bullard (carter@qosient.com). Olaf Gellert (gellert@pca.dfn.de). SEE ALSO
ra(1), rarc(5), argus(8) 22 July 2002 RAPOLICY(1)
Check Out this Related Man Page
YPSERV.ACL(5) BSD File Formats Manual YPSERV.ACL(5) NAME
ypserv.acl -- ypserv(8) configuration file DESCRIPTION
The ypserv.acl file controls which hosts can connect to the YP server. The format is more complex than the format for securenet(5). The first two verbs on each line controls if the line will allow or deny access for a host, network (net) or all hosts. The YP server reads the configuration file and build a list in memory. This list is processed from the beginning for every incomming request. As soon a match is found in the list the search terminates and it returns success or failure depending on allow or deny. If no match was found in the list success is returned. If access is denied every call will cause a no such domain error for the caller. Don't forget to allow localhost access if you want the machine running ypserv access it too. There is no default name for this file. Start ypserv with a -a filename to read a file with this format. The following different syntax can be used: < allow|deny > host < hostname|ip-address > If hostname has more than one ip address then all will be added to the list. < allow|deny > net < netname|netnumber > [netmask <netname|netnumber>] If netmask part of the command isn't given then the netmask will be assumed to be a class A, B or C net depending on the net number. < allow|deny > all A line containing one of these commands will always match any host. EXAMPLES
A configuration file might appear as follows: # This is an example of an access control file to be used by ypserv. # # This file is parsed line by line. First match will terminate the check # of the caller. # ########################################################################### # This is the commands that will match a single host # # allow host <hostname|ip-address> # deny host <hostname|ip-address> # # To process hostname gethostbyname is called. If the hostname has # multiple ip-addresses all will be added (I hope). ip-address # processed by inet_aton. allow host localhost deny host jodie ########################################################################### # This is the commands that will match a network # # allow net <netname|netnumber> [netmask <netname|netnumber>] # deny net <netname|netnumber> [netmask <netname|netnumber>] # # To process netname getnetbyname is called, and inet_aton is used for # netnumber. inet_aton both access numbers as 255.255.255.0 and 0xffffff00. # # If netmask isn't given the parser will assume netmask from the first bits # of the network number. So if the network is subneted the you have to add # the netmask. In my case I've got the network 139.58.253.0 at home so too # allow any of my computers to talk with the server I need the following # line # allow net mojathome netmask 255.255.255.0 ########################################################################### # At last we have a command that will match any caller: # # allow all # deny all # # reject all connections deny all FILES
/var/yp/ypserv.acl A ypserv(8) configuration file. SEE ALSO
yp(8), ypserv(8), securenet(5) AUTHOR
Mats O Jansson <moj@stacken.kth.se> BSD
July 2, 1994 BSD