Re: Access Accept

[Miha Zoubek]

Hi @Alexandre, I add this to my post-auth { } section: update reply {         3GPP2-Prepaid-acct-Capability =%{request:3GPP2-Prepaid-acct-Capability}         Acct-Multi-Session-Id =%{request:Acct-Multi-Session-Id}         3GPP2-Session-Termination-Capability =%{request:3GPP2-Session-Termination-Capability}         3GPP2-Release-Indicator =%{request:3GPP2-Release-Indicator} } From the debug I get:  }  Module: Checking session {...} for more modules to load  Module: Checking post-proxy {...} for more modules to load  Module: Checking post-auth {...} for more modules to load /etc/raddb/sites-enabled/default[462]: ERROR: Unknown value %{request:3GPP2-Session-Termination-Capability} for attribute 3GPP2-Session-Termination-Capability /etc/raddb/sites-enabled/default[456]: Errors parsing post-auth section. Why I am getting 3GPP2-Session-Termination-Capability as unknown value (I have this attribute in my dictionaries) as this value (value of 3GPP2-Session-Termination-Capability attribute) is send in access-request packet? For    3GPP2-Session-Termination-Capability =%{request:3GPP2-Session-Termination-Capability} I am still getting Acct-Multi-Session-Id = "%{request:Acct-Multi-Session-Id}". Here is  access-request from Wireshark for batter pictre: access-request:  Attribute Value Pairs         AVP: l=15  t=Acct-Multi-Session-Id(50): 1317016867140  (I need this one in access-accept)             Acct-Multi-Session-Id: 1317016867140         AVP: l=41  t=Vendor-Specific(26) v=Cisco(9)             VSA: l=35 t=Unknown-Attribute(130): 683332332d63616c6c696e672d656e74657270726973652d...                 Unknown-Attribute: 683332332d63616c6c696e672d656e74657270726973652d...         AVP: l=10  t=Calling-Station-Id(31): 81609000             Calling-Station-Id: 81609000         AVP: l=13  t=NAS-Identifier(32): intraswitch         AVP: l=6  t=NAS-IP-Address(4): xxx.xxx.xxx.xxx         AVP: l=14  t=Vendor-Specific(26) v=3GPP2(5535)  (I need this one in access-accept)             VSA: l=8 t=3GPP2-Prepaid-acct-Capability(91): 010600000002                   3GPP2-Prepaid-acct-Capability: 010600000002         AVP: l=12  t=Vendor-Specific(26) v=3GPP2(5535)     (I need this one in access-accept)             VSA: l=6 t=3GPP2-Session-Termination-Capability(88): 1                   3GPP2-Session-Termination-Capability: 1         AVP: l=34  t=Vendor-Specific(26) v=Cisco(9)             VSA: l=28 t=h323-conf-id(24): h323-conf-id=1317016867140                 h323-conf-id: h323-conf-id=1317016867140         AVP: l=6  t=Vendor-Specific(26) v=Cisco(9)         AVP: l=6  t=Event-Timestamp(55): Sep 26, 2011 08:01:07.000000000 Central Europe Daylight Time         AVP: l=11  t=User-Name(1): 081609000         AVP: l=18  t=User-Password(2): Encrypted Thank you! BR, Miha On 9/24/2011 2:43 PM, Alexandre Chapellon wrote: Le 23/09/2011 22:01, Miha a écrit : Hi @Alexandre, here is a copy from me default file: post-auth { # Get an address from the IP Pool. # main_pool update reply { 3GPP2-Prepaid-acct-Capability = %{request:3GPP2-Prepaid-acct-Capability} } update reply { Acct-Multi-Session-Id = %{request:Acct-Multi-Session-Id} } IIRC I use double quoted variables in my config. Anyway, this is odd it happens for the second attributes and not the first one. I have also try this way, but still the same: update reply { 3GPP2-Prepaid-acct-Capability = %{request:3GPP2-Prepaid-acct-Capability} Acct-Multi-Session-Id = %{request:Acct-Multi-Session-Id} } This sounds better. I do not see any problem with quotes. Thank you! Br, Miha -- View this message in context: http://freeradius.1045715.n5.nabble.com/Access-Accept-tp4832711p4834972.html Sent from the FreeRadius - User mailing list archive at Nabble.com. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- Alexandre Chapellon Ingénierie des systèmes open sources et réseaux. Follow me on twitter: @alxgomz - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html