comparison doc/echodrop.rgwx.conf.sample @ 550:4c935aecee6c

Hide and automate the Proxy-State attributes management in RADIUS gateway
author Sebastien Decugis <sdecugis@nict.go.jp>
date Wed, 15 Sep 2010 14:24:45 +0900
parents 1faed3f64af6
children
comparison
equal deleted inserted replaced
549:1b8809c7d7cc 550:4c935aecee6c
23 # <ext-type>: NOTE: THIS OPTION IS NOT SUPPORTED PROPERLY YET!!!! 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) 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). 25 # and we match only this "Ext-Type" value (16 bits).
26 # This option should only be used with "CODE 26 VENDOR 0". 26 # This option should only be used with "CODE 26 VENDOR 0".
27 # 27 #
28 # Note that the Proxy-State (code 33) attribute is handled directly as an ECHO parameter by the gateway core.
28 29
29 # Examples: 30 # Examples:
30 # DROP code 18 ; # Reply-Message attribute, should not be included in requests 31 # DROP code 18 ; # Reply-Message attribute, should not be included in requests
31 # DROP code 26 vendor 9 ; # Drop any Cisco-specific attribute 32 # DROP code 26 vendor 9 ; # Drop any Cisco-specific attribute
32 # ECHO code 26 vendor 0 ext 256 ; # Echo any extended attribute with the type 256. 33 # ECHO code 26 vendor 0 ext 256 ; # Echo any extended attribute with the type 256.
33
34 ECHO code 33 ; # RADIUS Proxy-State attribute
"Welcome to our mercurial repository"