Hello MunFai -
Your AuthBy SQL clause(s) will need an additional check item for the
NAS-Port.
Something like this:
AuthBy SQL
.
AuthSelect select password, nasport from subscribers \
where username=%0
Oh, I didn't saw that, thanks! Mea culpa.
Ok, half the problem solved :-)
How about the password?... since in order to support various valid
sessions for the same username the password must be part of the search
query, right? Without the password the query might return multiple
lines, and
Hello Daniel -
The only other thing I can think of is that you are using Fork
somewhere in your configuration.
BTW - the latest version is Radiator 3.7.1 (plus patches).
regards
Hugh
On 10/12/2003, at 11:59 PM, Danny Bendersky wrote:
Hi,
On Dec 4, 2003, at 3:44 AM, Hugh Irvine wrote:
Hello Rodrigo -
In this case you should probably write a hook to run the SQL query and
parse the rows that come back.
regards
Hugh
On 10/12/2003, at 11:15 PM, Rodrigo Nuno Bragança da Cunha wrote:
Oh, I didn't saw that, thanks! Mea culpa.
Ok, half the problem solved :-)
How about the
Rodrigo-
If I understand you correctly, you are concerned that someone may insert
some characters or even SQL statements into the password in order to launch
some sort of attack against your database. I think the root of your issue is
the fact that you want to include the password in the queries,
Hi,
We are running
Radiator 3.7 on a Win2k-box for some time now. System is stable, no
problems whatsoever. Until we decided to drop MS DNS-server for Bind
9.2.3. It seems to choke Radiator. Radiator just quits, no errors,
nothing... service just stopped.It stopped8
timesfromSunday
