Hello Camilo -
Thanks for sending the configuration file, however I will need to see a trace
4 debug from Radiator showing the problem.
BTW - I don't think your configuration file is correct, so perhaps you could
also send me a description of what you are wanting Radiator to do?
thanks
Hugh
Hello 'Tunde -
Thanks for the configuration file, however I will also need to see a trace 4
debug from Radiator showing the problem.
thanks
Hugh
On Friday 31 August 2001 02:22, 'Tunde Ogedengbe wrote:
> Hugh:
>
> See conf below:
>
> (radius.cfg)
>
> Foreground
>
> LogStdout
>
> Trace 3
>
>
Hi Hugh,
I´m using XtRadius
and we have a Cisco AS5300.
My radius.cfg file is:
=
# radius.cfg
LogStdout
Trace 4
AuthPort 1812
AcctPort 1813
LogFile /var/log/radius/radius.log
DictionaryFile /usr/local/radiator/dictionary
DictionaryFile /usr
Hugh:
See conf below:
(radius.cfg)
Foreground
LogStdout
Trace 3
PidFile /usr/local/etc/raddb/radiusd.pid
AuthPort 1645
AcctPort 1646
LogDir /usr/local/etc/raddb
DbDir /usr/local/etc/raddb
LogFile %L/logfile.%Y.%m.%d
DictionaryFile %D/dictionary
SnmpgetProg /usr/bin/snmpget
Secr
Hello Camilo, Hello 'Tunde -
In general, problems with simultaneous use are usually due to dropped
accounting packets (sometimes congested links, sometimes NAS bugs, sometimes
configuration problems with Radiator).
I am happy to assist with any problems, but I need to see what is going on.
P
I have the same problem.
Someone can help us???
'Tunde Ogedengbe wrote:
> Hello:
>
> We are having problems with this attribute. In some of our installations,
> the attribute does not work at all and so no restriction is enforced. On
> another installation, it works but with severe problems.
Hello:
We are having problems with this attribute. In some of our installations,
the attribute does not work at all and so no restriction is enforced. On
another installation, it works but with severe problems. For instance
customers with an attribute of 1 who previously connected to our syst
Hello Dave, Hello Vangelis -
Dave is correct in his comments below.
There are several things to be aware of with session databases in general.
First - the NAS stores the string that was entered by the user in its
internal table of active connections (usually). This means that you
need the or
> P.S. I think it would be very helpful if you included an
> option for case
> insensitivity for the internal session database in a future
> version of RADIATOR
You're on the right track. What it needs to store is two things:
- the ORIGINAL name as coming from the NAS. That will allow us to ma
Hugh Irvine wrote:
> Hello Vangelis -
>
> To do what you describe you need to use an SQL session database and
> supply your own AddQuery to use the rewritten username. NB - doing
> this will prevent you from using a NasType in your Client clauses.
Does this mean that if we use an SQL session d
Hello Vangelis -
To do what you describe you need to use an SQL session database and
supply your own AddQuery to use the rewritten username. NB - doing
this will prevent you from using a NasType in your Client clauses.
regards
Hugh
At 5:01 PM +0300 6/18/01, Vangelis Kyriakakis wrote:
>Hell
Hello,
using the internal session database for SimultaneousUse check
there is the following problem (if I am correct):
If a user changes the case of his username RADIATOR can't find him in
the session database if he has already logged in with his username
spelled in different case. Is it po
12 matches
Mail list logo
