Hello Nihal -
I would specify two AuthBy UNIX clauses, and use the "Match" parameter in
the second clause. I would then use Handlers to call one or the other, or I
would use an AuthByPolicy to call one then the other.
See section 6.23.2 in the Radiator 2.18.1 reference manual.
hth
Hugh
O
Hi Chairath,
Because of the way UNIX calculates time, you can only set this to Dec
31, 2037, 23:59. I don't know if this is true for running Radiator on
Windows...
Regards,
Danny Kruitbosch
On 05 Jun 2001 09:00:43 +0700, chairarth wrote:
> Hi all,
>
> In case of created user via RAdmin , wha
We currently using radiator to validate based on
the users Unix group.
and have several entries in the users file like
this -
DEFAULT Auth-Type = System, Group =
shell Service-Type =
Login-User, Login-IP-Host =
123.123.123.123, Login-Service =
Telnet
DEFAULT Auth-
Hello Chairarth -
Just specify a date far in the future.
regards
Hugh
On Tuesday 05 June 2001 12:00, chairarth wrote:
> > Hi all,
>
> In case of created user via RAdmin , what should I specifies in "Valid
> to" field to let new user will be able to login forever.
>
> Thanks,
> Chairath
Hi all,
In case of created user via
RAdmin , what should I specifies in "Valid to" field to let new user will
be able to login forever.
Thanks,
Chairath
Hello Dave -
I have copied this to Mike for his comments.
regards
Hugh
On Tuesday 05 June 2001 00:57, Kitabjian, Dave wrote:
> One problem that may inhibit our rollout of concurrency enforcement is the
> slowness of "snmpget" to query the NASes. Chatting with others and checking
> the archive
Hello Robert -
I would suggest that you change the entries below to something like this:
# this is the users file refered to by the configuration file
DEFAULT User-Name=user, NAS-IP-Address=x.x.x.x, Auth-Type=System
Framed-IP-Address = 1.2.3.4
DEFAULT User-Name=user, NAS-IP-Address=y
Hello Adam -
I will need to see a trace 4 debug from Radiator showing what is happening,
and I will need a detailed description of the problem.
thanks
Hugh
On Monday 04 June 2001 20:03, Mohammed Adam wrote:
> Hi all
>
> i'm facing a problem with Maxsessions, it doesnt work the following is m
One problem that may inhibit our rollout of concurrency enforcement is the
slowness of "snmpget" to query the NASes. Chatting with others and checking
the archive, it appears that others have had this problem, and that OSC has
indicated they may use Net::SNMP instead of snmpget:
http://w
I'm in the process of switching from Cistron to Radiator
using AuthEMERALD to authenticate against my database
which is maintained by Platypus 3.0.
One issue that I'm running into that I have yet to understand
how to resolve is the case of fall-through entries for the
user.
Currently I have ent
Hi all
i'm facing a problem with Maxsessions, it doesnt work the following is my Radius
config file
#
Foreground
LogStdout
LogDir .
DbDir .
DictionaryFile d:\radiator-demo-2.18\dictionary.cisco
Trace 4
# For testing: this allows us to honour requests from radpwtst
# on t
Hello Chairarth -
Radmin itself does not yet have this capability, however if you install the
"radwho.cgi" script included with Radiator, you will find that it does have a
"Delete Session" option.
Otherwise, you can just issue an SQL query directly to delete the row.
hth
Hugh
On Monday 04
12 matches
Mail list logo