hi,
How do i restrict users to authenticate from say 4:00 am till 2:00 pm
only?
At present we are doing this with a select statement in the
AuthSelect section.
Is there a way other than this
regards
eapen
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL
Hi All,
Apologies for the long message...
I have discovered a freaky problem in Radiator - this is not Radiators fault
but it causes problems.
The situation I have found is as follows :
We use Authby DyanAddress to allocate IP addresses to broadband users -
radius requests are sent to our
Hello Brian -
As you say - this is not a Radiator problem - and it is difficult to see how
Radiator can be made to deal with a network routing issue. Depending on the
exact contents of the radius requests that you are receiving, it may be
possible to set up a session database and use session
Hello Robert -
Both the NAS and Radiator consider case differences as different usernames,
so the answer to your question is no - the RewriteUsername has no bearing. As
mentioned previously, the only way to deal with the problem is with a session
database that stores both the original and
Hello Eapen -
This is easiest to do with Handlers:
# define AuthBy SQL clauses
AuthBy SQL
Identifier SQLAcct1
.
/AuthBy
AuthBy SQL
Identifier SQLAcct2
.
/AuthBy
AuthBy SQL
Identifier SQLAcct3
.
/AuthBy
# define Handlers
Handler
Hello Eapen -
You would use the Time = check item.
Have a look at section 13.1.13 in the Radiator 2.19 reference manual.
regards
Hugh
On Sun, 3 Feb 2002 20:37, Eapen Joseph wrote:
hi,
How do i restrict users to authenticate from say 4:00 am till 2:00 pm
only?
At present we are
Hello Allister -
You may find it easiest to proxy the radius requests to the Windows 2000 box
and run a copy of Radiator there with an AuthBy ADSI clause.
Have a look at section 6.40 in the Radiator 2.19 reference manual
(doc/ref.html).
Otherwise you should supply your own SearchFilter
Dear Hugh,
As you said, the time option should work. But the restriction should be
in such a way, so that the session time returned by the time function
should not override the balance time, which is returned as the session
time to the access-server in the normal fashion.
i.e the balancetime
Agreed,
However, I notice that Radiator removes any 'freaky' entry from the
RADONLINE table along the lines of:
Delete from radonline where nasidentifier = 'whatever' and nasport =
'whatever'
prior to adding the new entry to the RADONLINE table.
Couldn't a similar sanity check be used for
Hello Eapen -
I think you will have to do this in a hook (probably a PostAuthHook).
There are some example hooks in the file goodies/hooks.txt.
regards
Hugh
On Mon, 4 Feb 2002 16:43, Eapen Joseph wrote:
Dear Hugh,
As you said, the time option should work. But the restriction should be
Hello Brian -
As I mentioned in my previous mail, you will have to look closely at the
requests that you receive from your NAS(s) to determine whether or not there
is any way to apply a sanity check and indeed what that sanity check might be.
regards
Hugh
On Mon, 4 Feb 2002 16:55, Brian
11 matches
Mail list logo