I've been messing around with trying to get huntgroup access working
with SQL. I've made some headway, but I'm seeing something mighty
strange. Specifically, the line below which reads: rlm_sql
(sql_acct): - sql_groupcmp
I have my sql.conf configured to check accounting on one sql server
, Jason Lixfeld wrote:
I've been messing around with trying to get huntgroup access working
with SQL. I've made some headway, but I'm seeing something mighty
strange. Specifically, the line below which reads: rlm_sql
(sql_acct): - sql_groupcmp
I have my sql.conf configured to check accounting
On Dec 6, 2004, at 12:57 PM, Alan DeKok wrote:
Jason Lixfeld [EMAIL PROTECTED] wrote:
Hi. I'm reposting this in hopes that someone will be able to give me
some insight as to what I've missed...
There were issues with the huntgroup code, but I think they've been
fixed in 1.0.x.
We're using 1.0.1
Yes, -X is telling you that TLS is configured incorrectly. Read the
documentation on TLS and you will find out exactly where your problem
is.
On Dec 4, 2004, at 7:52 PM, Carl wrote:
tls: certificate_file = (null)
...
...
...
rlm_eap_tls: Error reading certificate file
-
List
Hello...
I'm having a hard time wrapping my head around some problems I'm having
with huntgroups. I'm trying to permit access only based on if a
request comes from a certain huntgroup and the user is a member of said
group.
Here's radtest:
# radtest [EMAIL PROTECTED] beantest 127.0.0.1 10
Pardon my possible stupidity, but in looking at how to solve my own
problems, I came across this from man 5 users:
DEFAULT Service-Type == Framed-User, Framed-Protocol == PPP
Service-Type = Framed-User,
Framed-Protocol = PPP,
Fall-Through = Yes
, at 4:13 PM, Jason Lixfeld wrote:
I'm getting segmentation faults when it tried to load the SQL module
after implementing Thor's changes:
bash# radiusd -X
...
...
...
Module: Instantiated realm (suffix)
Segmentation fault
bash#
Configuration:
sql.conf:
sql_acct {
driver = rlm_sql_mysql
Thanks. That was it.
For the maintainers: Perhaps adding a comment or something to the
sql.conf to the effect of using sql custom name { } for users who
want to use multiple databases but not for the purposes described in
the configurable_failover document. Maybe adding an example in the
8 matches
Mail list logo