(RADIATOR) RadOnLine

[Hugh Irvine]

Hello Herman -

Yes you can have different SessionDatabase's on a per-Handler or 
per-Realm basis.

# define SessionDatabase

<SessionDatabase ...>
	Identifier SDB1
	.....
</SessionDatabase>

<SessionDatabase ...>
	Identifier SDB2
	.....
</SessionDatabase>

.....

<Handler ....>
	SessionDatabase SDB1
	.....
</Handler>

<Handler ....>
	SessionDatabase SDB2
	.....
</Handler>

.....


regards

Hugh


On Thursday, Jun 26, 2003, at 04:47 Australia/Melbourne, Herman 
verschooten wrote:

> Nicolai,
>
> I see.  Now a question... Can you specify a different SessionDatabase
> per client or realm ?
>
> Herman verschooten
>
> -----Original Message-----
> From: Nicolai van der Smagt [mailto:nicolai.vandersmagt at bbned.nl]
> Sent: woensdag 25 juni 2003 20:12
> To: Herman verschooten
> Cc: radiator at open.com.au
>
> Hello,
>
> To do what you want you add this to your <SessionDatabase SQL> clause:
>
> AddQuery insert into RADONLINE (USERNAME, NASIDENTIFIER, NASPORT, \
> ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE, \
> SERVICETYPE, STATIONID) values ('%n', '%N', 0%{NAS-Port},\
> '%{Acct-Session-Id}', %{Timestamp}, '%{Framed-IP-Address}',\
> '%{NAS-Port-Type}', '%{Service-Type}', '%{Calling-Station-Id}')
>
> And modify your table to include the 'STATIONID' column ofcourse.
>
> Another way to solve the stale sessions problem is to use accounting
> updates, 'alive' packets.
>
> Cheers,
> Nicolai
>
> On Wed, 2003-06-25 at 19:18, Herman verschooten wrote:
>> Hi,
>>
>> Is there an easy way to extend the on-line check with the callerid?
>>
>>
>>
>> We use Radiator to authenticate from different ADSL-providers.  One of
>> these frequently drops STOP-packets. Don't ask me how, but we lose a
>> lot of them... Start en Alive, no problem, but Stops seem to have
> other
>> engagements.
>>
>>
>>
>> This of course means that the user's state remains on-line even after
>> they disconnect.  The NASPort is quite useless in this case, since the
>> Redback chooses a new port when the customer redials.  When we used
>> RadiusNT I wrote a complex solution using triggers and stored
>> procedures on SQL to delete the record from the online-table when the
>> request came from the same NAS/CallerID for the ADSL-users.  Now I
>> need a similar system on Radiator, but I have not yet found how to add
>> the callerid to the RadOnline table.
>
>
>
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.