1 | # Sample configuration file for the echodrop.rgwx plugin of RADIUS/Diameter translation agent. |
---|
2 | # |
---|
3 | # This plugin allows to easily specify the following handling of RADIUS attributes |
---|
4 | # received in a RADIUS request: |
---|
5 | # - ECHO: the attribute will be copied verbatim in the RADIUS answer. |
---|
6 | # - DROP: the attribute is discarded. |
---|
7 | # |
---|
8 | # In both cases, the attribute is NOT translated in Diameter message. |
---|
9 | # |
---|
10 | # The format of this file is: |
---|
11 | # <action> CODE <code> [ VENDOR <vid> [ TLV <type> | EXT <ext-type> ] ]; |
---|
12 | # Where: |
---|
13 | # <action>: is either DROP or ECHO. |
---|
14 | # <code> : is a (decimal) integer between 0 and 255, and designates the type of the attribute. |
---|
15 | # |
---|
16 | # The remaining of the line is optional, and should only be used |
---|
17 | # with lines containing "CODE 26" (Vendor-Specific Attribute) |
---|
18 | # <vid> : a Vendor value (32 bit), see RFC2865 section 5.26 for detail. |
---|
19 | # |
---|
20 | # <type> : The attribute is interpreted as TLV (rfc3865, section 5.26) |
---|
21 | # and we match only this "vendor type" value (8 bits). |
---|
22 | # |
---|
23 | # <ext-type>: NOTE: THIS OPTION IS NOT SUPPORTED PROPERLY YET!!!! |
---|
24 | # The attribute is interpreted as extended attribute (draft-ietf-radext-extended-attributes-08) |
---|
25 | # and we match only this "Ext-Type" value (16 bits). |
---|
26 | # This option should only be used with "CODE 26 VENDOR 0". |
---|
27 | # |
---|
28 | # Note that the Proxy-State (code 33) attribute is handled directly as an ECHO parameter by the gateway core. |
---|
29 | |
---|
30 | # Examples: |
---|
31 | # DROP code 18 ; # Reply-Message attribute, should not be included in requests |
---|
32 | # DROP code 26 vendor 9 ; # Drop any Cisco-specific attribute |
---|
33 | # ECHO code 26 vendor 0 ext 256 ; # Echo any extended attribute with the type 256. |
---|