Mercurial > hg > waaad
view doc/sub_echo_drop.conf.sample @ 374:883330e610e1
Progress on the echo_drop sub extension
author | Sebastien Decugis <sdecugis@nict.go.jp> |
---|---|
date | Tue, 26 May 2009 11:37:32 +0900 |
parents | 0cb02e490017 |
children | 03b512313cc1 |
line wrap: on
line source
# Sample configuration file for the sub_echo_drop subextension of radius_gw. # # This extension allows to easily specify the following handling of RADIUS attributes # received in a RADIUS request: # - ECHO: the attribute will be copied as-is in the RADIUS answer. # - DROP: the attribute is discarded. # # In both cases, the attribute is NOT converted to Diameter. # # Note that this extension needs a session module extension processed the message previously, # if the ECHO handling is to be used. # # This file contains lines like this: # <action> CODE <code> [ VENDOR <vid> [ TLV <type> | EXT <ext-type> ] ]; # Where: # <action>: is either DROP or ECHO. # <code> : is a (decimal) integer between 0 and 255, and designates the type of the attribute. # # The remaining of the line is optional, and should only be used # with lines containing "CODE 26" (Vendor-Specific Attribute) # <vid> : a Vendor value (32 bit), see RFC2865 section 5.26 for detail. # # <type> : The attribute is interpreted as TLV (rfc3865, section 5.26) # and we match only this "vendor type" value (8 bits). # # <ext-type>: NOTE: THIS OPTION IS NOT SUPPORTED PROPERLY YET!!!! # The attribute is interpreted as extended attribute (draft-ietf-radext-extended-attributes-08) # and we match only this "Ext-Type" value (16 bits). # This option should only be used with "CODE 26 VENDOR 0". # # Examples: # ECHO code 25 ; # Class attributes # DROP code 18 ; # Reply-Message attribute, should not be included in requests # DROP code 26 vendor 9 ; # Drop any Cisco-specific attribute # ECHO code 26 vendor 0 ext 256 ; # Echo any extended attribute with the type 256.