Re: update session database in Authorization

2010-02-16 Thread Houssam Melhem
Hello,
You are right, I have this problem with Pheenet Access point and Nomadix AG,
for cisco NAS I have no problem
If I need to fix this issue what is the recommended solution to fix this
issue?
If I modify the authorize section to save sessions does it break Radius
Protocol ?
I am thinking in patching rlm_sql, what do you think?

Thanks,
Houssam

On Wed, Feb 17, 2010 at 12:19 AM, Fajar A. Nugraha  wrote:

> On Wed, Feb 17, 2010 at 12:19 AM, Houssam Melhem 
> wrote:
> > How can we prevent multiple login in this situation? shall we think in
> > adding a record to the session database in authorization section?
>
> In normal situation, acct-capable NAS send acct-start immediately
> after it receives access-accept, so there should be no need for you to
> do that manually.
>
> --
> Fajar
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

update session database in Authorization

2010-02-16 Thread Houssam Melhem
Hello,

When 2 users  with same username try to login to the server at the same
time; Radius server receives Auth and Acct packets in the following order:

1- Auth from user1
2- Auth from user2
3- Acct from user1
4- Acct from user2

Since the session database is not populated until a user sends an accounting
packet (using radutmp or sql modules)
How can we prevent multiple login in this situation? shall we think in
adding a record to the session database in authorization section?


I am using freeradius-2.1.6

configurations
=
authorize {
preprocess
chap
suffix
files
sql
pap
}
preacct {
preprocess
acct_unique
suffix
files
}
accounting {
#   radutmp
sql
}
session {
#   radutmp
sql
}


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