Re: (RADIATOR) CHAP-Password / User-Password

2003-10-09 Thread Matteo Jurman
Thank you Hugh, I fixed that goddam problem (the funny thing is, I don't know how!) now I have a new problem: in the request (from client) I have to include, besides username/psw/service-type, also other 2 fields, the 2 names (row1 and row2, stored in the db) of the client which is authenticated,

(RADIATOR) Accounting Local and forwarding using rewriteusername problems

2003-10-09 Thread Sergio Gómez \(E-mail\)
Hi everybody, I have problems using Local and forwarding accounting. First of all here you have a piece of mi cfg file for the 'test' realm: AuthBy SQL Identifier authBySQL_InsertCallAcct DBSource dbi:ODBC:radius_databasex DBUsername testuser DBAuth

RE: (RADIATOR) NULL usernames in Radius Packets

2003-10-09 Thread Mahesh Neelakanta
Just a followup. We indeed were ignoring those types of packets since we don't have a handler where username is NULL (we check based on realms). So we added: Handler RejectHasReason AuthBy INTERNAL DefaultResult REJECT AcctResult ACCEPT

Re: (RADIATOR) cisco-avpair accounting

2003-10-09 Thread Hugh Irvine
Hello Jesus - If you are receiving multiple attributes with the same name (ie: cisco-avpair = .) then yes you will need to use a Hook to parse them into seperate differently named attributes. Then you can use the AcctColumnDef's in your AuthBy SQL clause. regards Hugh On Friday, Oct 10,

Re: (RADIATOR) Accounting Local and forwarding using rewriteusername problems

2003-10-09 Thread Hugh Irvine
Hello Sergio - You will need to use an AuthBy GROUP with the RewriteUsername inside: Handler Request-Type=Accounting-Request,Realm=test AuthByPolicy ContinueAlways AuthBy authBySQL_InsertCallAcct AcctLogFileName %L/radiusd_acct-%Y%m%d.log AuthBy GROUP

Re: (RADIATOR) CHAP-Password / User-Password

2003-10-09 Thread Hugh Irvine
Ciao Matteo - I don't quite understand what you mean below in the request (from client) I have to include ? Can you give me a bit more detail on what you want to do? regards Hugh On Thursday, Oct 9, 2003, at 23:32 Australia/Melbourne, Matteo Jurman wrote: Thank you Hugh, I fixed that

(RADIATOR) AuthBy EXTERNAL Can't pass received attribute to external program via STDIN

2003-10-09 Thread Man Meng Fei
Hi Previously i did ask a question regarding test run AuthBy External by using sample configuration (external.cfg) and perl script (testcommand.pl) which can be found in the goodies directory. After read thru all the replied emails and relevant document, i tried to execute this sample

Re: (RADIATOR) AuthBy EXTERNAL Can't pass received attribute to external program via STDIN

2003-10-09 Thread Hugh Irvine
Hello Man - You are correct, Radiator will stop while the program specified by the AuthBy EXTERNAL command executes. If the program never exits, then Radiator will wait forever. You should add some print ... statements to the code in the external program to see what it is doing. BTW - you

(RADIATOR) AddToReply

2003-10-09 Thread Andrea Brancatelli
in my SUBSCRIBERS table I have the following entry: Username = ugo Password = Checkattr = (NULL) ReplyAttr = 'Class = 3, Idle-Timeout = 600' TimeLeft = (NULL) WHERE am I supposed to see the replyattr? The access point is not doing what is specified there and radpwtst doesn't show any

(RADIATOR) replyattr

2003-10-09 Thread Andrea Brancatelli
sorry, i'm dumb. :-) i've read the manual and changed the authselect accordingly.