In message [EMAIL PROTECTED],
"Mike McCauley" [EMAIL PROTECTED] writes:
| Yes, its pretty easy, but the way to do it depends on what type of databse yo
|u
| have. Basically what you need to do is set up a reply item for the user with
| eg:
| Framed-IP-Address=192.168.1.1
While we're
Hi Paul,
Yes, AuthBy SQL (like all AuthBy clauses takes an AddToReply parameter, which
is a comma separated list of attribute-value pairs. It will add those
attributes to _every_ reply. So if you have a common set of attributes, use
AddToReply.
There is also DefaultReply, which adds attributes
Does anybody knows if there is a way to configure time based restriction
("Time" check item) for users authenticated via Authby UNIX ou SYSTEM?
Using Radiator v.2.13.1 with latest patches, OS platform is IBM AIX
v.4.1.5.
The user in question has it group set to "admfin". By looking at the log
IgnoreAcctSignature seems to have rectified the accting interference.
Thanks,
Oliver
On Mon, 7 Jun 1999, Mike McCauley wrote:
Hi Oliver,
On Jun 4, 4:57pm, O Stockhammer wrote:
Subject: Re: (RADIATOR) Accounting dictionary for netserver card
These are from the logfile:
Fri Jun
In my ongoing struggle to setup radiator to authenticate off a SQL Server and
Platypus, I have the following questions:
I'm using the Authby EMERALD because we do have the Radius package add-on for
platypus. However, I was looking at AuthbyEMERALD.pm. Can I not specify a custom
select
Hi Rich,
I cant explain that at all. Could you send me a sanitized extract from your
users file, so I can test it here?
Cheers.
On Jun 7, 1:38pm, Richard Cameron wrote:
Subject: (RADIATOR) AuthBy File Problems- Version Differences between 2.13
Hello Radiator's:
I have recently
Hi Richard,
In both EMERALD and PLATYPUS, the select statment is mostly hard-wired, but you
do get the chance to tweak it. The theory is that you can add extra columns to
the Emerald or Platypus tables if you wish.
In both of those modules, if you specify AuthSelect, its added to the select
Hi Mike,
It seems the the specific clause is working ok, but the auth packet is
being catched by the last DEFAULT clause. Here you are (debug level 4):
Tks,
Mon Jun 7 20:57:11 1999: DEBUG: Packet dump:
*** Received from 200.240.25.3 port 1645
Code: Access-Request
Identifier: 160
On Jun 7, 9:03pm, Jose Roberto Bulcao wrote:
Subject: Re: (RADIATOR) Time check item in Authby UNIX
Hi Mike,
It seems the the specific clause is working ok, but the auth packet is
being catched by the last DEFAULT clause. Here you are (debug level 4):
Yes, its clear that your clause is
