Delimeters doesn't work

Does freeRadius support prefix and suffix delimeters other than '/' and '@' sign. If yes then where to specify them. I tried to use '%','.' and '\' them after specifying in radiusd.conf file but it doesn't work. Can someone solve my issue? -- Nishant Shah U4 Computer Engineering 979-268-0866

Delimeter other than / and @

Hi, Can anyone tell me how to specify prefix and suffix delimeters other than '/' and '@' sign? I tried '$', '.', and '%' sign, but it doesn't work. -- Nishant Shah U4 Computer Engineering 979-268-0866 (M)281-222-3176 - List info/subscribe/unsubscribe? See

Accounting Attributes

I have Cisco 2509 NAS box. I want it to send me all the accounting attributes mentioned in RFC's and that is used by freeRADIUS. Presently, it sends very few accounting attributes. Can anyone tell me how to configure NAS to add more accounting attributes besides what it sends. Thanks, Nishant

Configuring server for authorization

I have a Access-Request packet from NAS that looks like: User-Name = user1 Password = user1 Cisco-AVPair = ip:9.3.41.17 On server, user1 is defined in users file with password user1 and Cisco- AVPair = ip:9.3.141.1. I want to authorize user based on the password and Cisco-AVPair =

Vendor Specific attribute in authorization packet

Hi all, If I am not misunderstanding, RADIUS authorizes the user with password only and not with vendor specific attribute in the packet. If it can be done then can anyone tell me how to configure the server for that.Here is the scenario: I have a cisco router between user

Vendor Specific attribute in authorization packet

I am sending an authorization packet from radclient with vendor specific attribute: Cisco-AVPair=ip:xxx along with username and correct password.RADIUS server authorizes the user with access-accept packet with Cisco-AVPair=ip:yyy, which confuses me. Because in the users file on server side

Re: Vendor Specific attribute in authorization packet

Alan DeKok [EMAIL PROTECTED] said: Shah, Nishant B [EMAIL PROTECTED] wrote: I am sending an authorization packet from radclient with vendor specific attribute: Cisco-AVPair=ip:xxx Ok... I don't see why, though. RADIUS server authorizes the user with access-accept packet

Re: Vendor Specific attribute in authorization packet

Alan DeKok [EMAIL PROTECTED] said: Shah, Nishant B [EMAIL PROTECTED] wrote: YES I DO HAVE SPECIFIC QUESTION. AS FOR EXAMPLE, No need to shout. I apologise for that, I didn't mean to shout. sorry if I hurt someone's feelings If the user sends a packet with Cisco-AVPair=ip:xxx

RE: How freeRADIUS handles vendor specific

. -Original Message- From: Shah, Nishant B [mailto:[EMAIL PROTECTED] Sent: Thursday, April 22, 2004 12:23 PM To: [EMAIL PROTECTED] Subject: Re: How freeRADIUS handles vendor specific Alan DeKok [EMAIL PROTECTED] said: Can someone tell me how RADIUS server handles vendor specific

Re: How freeRADIUS handles vendor specific

Alan DeKok [EMAIL PROTECTED] said: Can someone tell me how RADIUS server handles vendor specific attribute. I am sending a packet using radclient with vendor specific attribute and its working. I found that attribute is not in dictionary. I want to know where in the code it checks for

How freeRADIUS handles vendor specific

Hi everyone, Can someone tell me how RADIUS server handles vendor specific attribute. I am sending a packet using radclient with vendor specific attribute and its working. I found that attribute is not in dictionary. I want to know where in the code it checks for the vendor specific