Re: how to configure my scenario
- Original Message -
From: Peter Manckok [EMAIL PROTECTED]
To: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Sent: Thursday, February 23, 2006 11:52 AM
Subject: Re: how to configure my scenario
--- Phil Mayers [EMAIL PROTECTED] escribió:
Peter Manckok wrote:
authenticate {
..
Auth-Type LDAP1 {
interface1
}
Auth-Type LDAP2 {
interface2
}
Auth-Type LDAP3 {
interface3
}
}
In my authorize section I have:
authorize{
files
...
}
In my users file I have:
DEFAULT NAS-IP-Address == a.b.c.d, Auth-Type
:=LDAP1
DEFAULT NAS-IP-Address == a2.b2.c2.d2, Auth-Type
:=LDAP2
DEFAULT NAS-IP-Address == a3.b3.c3.d3, Auth-Type
:=LDAP3
Provided there's nothing after the files in
authorize that might be
(re)setting Auth-Type, that should work.
Thanks for the warning
Don't snip
bits out - what is
the full contents of the authorize and authenticate
sections? What does
the radius server say when you run it in debug mode
(with -X)?
-
Hy Phil,
My problem is how to select the correct authorize
method of an instance depending on the NAS-IP-Address
of the Access-Request packet. For example, if the
NAS-IP-Address is a.b.c.d I would like to use the
authorize method of interface1 (and NOT the authorize
method of interface2 or interface3)
I haven´t tested it yet, I am not in my company now
In the authorize section I have:
authorize{
preprocess
suffix
files
??? --- how can I discriminate between the
differents authorize methods of interface1,
interface2, interface3 depending on the source
NAS-IP-Address?
}
In the authenticate section:
authenticate {
Auth-Type LDAP1 {
interface1
}
Auth-Type LDAP2 {
interface2
}
Auth-Type LDAP3 {
interface3
}
unix
}
Thanks again
Any hint is very appreciated
Peter
Use Autz-Type to select between authorization methods
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
__
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
LDAP iplanet
Hy all, Has someone used FreeRadius with a iplanet LDAP server? Thanks a lot - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
ldap control access
Hy all, I have configured my LDAP server with the following control access. In the slapd.conf: access to * by self write by dn="cn=replica,ou=admins,ou=radius,dc=mydomain,dc=com" write by anonymous auth by * none --- My users file: DEFAULT Ldap-Group == isdn, NAS-Port == 58, User-Profile := "uid=isdn,ou=profiles,ou=radius,dc=mydomain,dc=com" DEFAULT Auth-Type := Reject Reply-Message = "Llamse a servicio tecnico" --- My directory: dn: dc=mydomain,dc=comobjectclass: dcObjectobjectclass: organizationalUnitou: Mydomain.com Radiusdc: mydomain dn: ou=radius,dc=mydomain,dc=comobjectclass: organizationalUnitou: radius dn: ou=profiles,ou=radius,dc=mydomain,dc=comobjectclass: organizationalUnitou: profiles dn: ou=users,ou=radius,dc=mydomain,dc=comobjectclass: organizationalUnitou: users dn: ou=admins,ou=radius,dc=mydomain,dc=comobjectclass: organizationalUnitou: admins dn: uid=dial,ou=profiles,ou=radius,dc=mydomain,dc=comobjectclass: radiusprofileuid: dialradiusServiceType: Framed-UserradiusFramedProtocol: PPPradiusFramedIPNetmask: 255.255.255.0radiusFramedRouting: None dn: uid=isdn,ou=profiles,ou=radius,dc=mydomain,dc=comobjectclass: radiusprofileuid: isdnradiusServiceType: Framed-UserradiusFramedProtocol: PPPradiusFramedIPNetmask: 255.255.254.0radiusFramedRouting: None dn: uid=example,ou=users,ou=radius,dc=mydomain,dc=comobjectclass: radiusprofileuid: exampleuserPassword: testradiusGroupName: dialradiusGroupName: isdn dn: cn=freeradius,ou=admins,ou=radius,dc=mydomain,dc=comobjectclass: personsn: freeradiuscn: freeradiususerPassword: freeradius dn: cn=billing,ou=admins,ou=radius,dc=mydomain,dc=comobjectclass: personsn: billing cn: billing userPassword: billing dn: cn=replica,ou=admins,ou=radius,dc=mydomain,dc=comobjectclass: personsn: replicacn: replicauserPassword: replica When I try to authorize a user, it fails: rad_recv: Access-Request packet from host 127.0.0.1:39035, id=223, length=59 User-Name = "example" User-Password = "test" NAS-IP-Address =xx.yy.cc.vv NAS-Port = 58 Processing the authorize section of radiusd.confmodcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "example", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 0rlm_ldap: Entering ldap_groupcmp()radius_xlat: 'ou=users,ou=radius,dc=mydomain,dc=com'radius_xlat: '(uid=example)'rlm_ldap: ldap_get_conn: Checking Id: 0rlm_ldap: ldap_get_conn: Got Id: 0rlm_ldap: attempting LDAP reconnectionrlm_ldap: (re)connect to localhost:389, authentication 0rlm_ldap: bind as / to localhost:389rlm_ldap: waiting for bind result ...rlm_ldap: Bind was successfulrlm_ldap: performing search in ou=users,ou=radius,dc=mydomain,dc=com, with filter (uid=example)rlm_ldap: object not found or got ambiguous search resultrlm_ldap::ldap_groupcmp: search failedrlm_ldap: ldap_release_conn: Release Id: 0 users: Matched entry DEFAULT at line 3 modcall[authorize]: module "files" returns ok for request 0rlm_ldap: - authorize If I remove the access control lines from slapd.conf, it works well. What am I doing wrong? Regards, Rafa - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: ldap control access
Yes, sorry, that was the error. I forgot to include the identity param in the ldap module in radiusd.conf Thanks - Original Message - From: Bjørn Mork [EMAIL PROTECTED] To: FreeRadius users mailing list freeradius-users@lists.freeradius.org Sent: Wednesday, February 01, 2006 12:36 PM Subject: Re: ldap control access Rafael Roldán [EMAIL PROTECTED] writes: rlm_ldap: bind as / to localhost:389 Doesn't look like you've set identity and password to anything. Maybe you should consider posting the ldap module configuration part of radiusd.conf too? Bjørn - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
bind failed in LDAP authentication phase
Hy all,
I am still doing tests with the rlm_ldap module and I have encountered with
the following problem:
In the authenticate phase the user replica try to bind to the LDAP server.
But this attempts fails. However, in the access control section of the LDAP
server, it has permission...
I don´t know what I am doing wrong
I have configured my LDAP server with the following control access. In the
slapd.conf:
access to *
by self write
by dn=cn=billing,ou=admins,ou=radius,dc=mydomain,dc=com write
by dn=cn=freeradius,ou=admins,ou=radius,dc=mydomain,dc=com read
by anonymous auth
by * none
My users file:
DEFAULT NAS-Port == 58, User-Profile :=
uid=isdn,ou=profiles,ou=radius,dc=mydomain,dc=com
DEFAULT Auth-Type := Reject
Reply-Message = Llamse a servicio tecnico
My directory:
dn: dc=mydomain,dc=com
objectclass: dcObject
objectclass: organizationalUnit
ou: Mydomain.com Radius
dc: mydomain
dn: ou=radius,dc=mydomain,dc=com
objectclass: organizationalUnit
ou: radius
dn: ou=profiles,ou=radius,dc=mydomain,dc=com
objectclass: organizationalUnit
ou: profiles
dn: ou=users,ou=radius,dc=mydomain,dc=com
objectclass: organizationalUnit
ou: users
dn: ou=admins,ou=radius,dc=mydomain,dc=com
objectclass: organizationalUnit
ou: admins
dn: uid=dial,ou=profiles,ou=radius,dc=mydomain,dc=com
objectclass: radiusprofile
uid: dial
radiusServiceType: Framed-User
radiusFramedProtocol: PPP
radiusFramedIPNetmask: 255.255.255.0
radiusFramedRouting: None
dn: uid=isdn,ou=profiles,ou=radius,dc=mydomain,dc=com
objectclass: radiusprofile
uid: isdn
radiusServiceType: Framed-User
radiusFramedProtocol: PPP
radiusFramedIPNetmask: 255.255.254.0
radiusFramedRouting: None
dn: uid=example,ou=users,ou=radius,dc=mydomain,dc=com
objectclass: radiusprofile
uid: example
userPassword: test
radiusGroupName: dial
radiusGroupName: isdn
dn: cn=freeradius,ou=admins,ou=radius,dc=mydomain,dc=com
objectclass: person
sn: freeradius
cn: freeradius
userPassword: freeradius
dn: cn=billing,ou=admins,ou=radius,dc=mydomain,dc=com
objectclass: person
sn: billing
cn: billing
userPassword: billing
dn: cn=replica,ou=admins,ou=radius,dc=mydomain,dc=com
objectclass: person
sn: replica
cn: replica
userPassword: replica
My radiusd.conf:
ldap {
server = localhost
identity =
cn=freeradius,ou=admins,ou=radius,dc=mydomain,dc=com
password = freeradius
basedn = ou=radius,dc=mydomain,dc=com
filter =
((sn=replica)(cn=%{Stripped-User-Name:-%{User-Name}}))
start_tls = no
dictionary_mapping = ${raddbdir}/ldap.attrmap
ldap_connections_number = 10
password_attribute = userPassword
groupname_attribute = radiusGroupName
groupmembership_filter =
((uid=%{Stripped-User-Name:-%{User-Name}}))(objectclass=radiusProfile)
groupmembership_attribute = radiusGroupName
timeout = 3
timelimit = 5
net_timeout = 1
}
---
Ready to process requests.
rad_recv: Access-Request packet from host 127.0.0.1:39089, id=92, length=59
User-Name = replica
User-Password = replica
NAS-IP-Address = 10.95.4.93
NAS-Port = 58
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 0
modcall[authorize]: module preprocess returns ok for request 0
modcall[authorize]: module chap returns noop for request 0
modcall[authorize]: module mschap returns noop for request 0
rlm_realm: No '@' in User-Name = replica, looking up realm NULL
rlm_realm: No such realm NULL
modcall[authorize]: module suffix returns noop for request 0
rlm_eap: No EAP-Message, not doing EAP
modcall[authorize]: module eap returns noop for request 0
users: Matched entry DEFAULT at line 1
modcall[authorize]: module files returns ok for request 0
rlm_ldap: - authorize
rlm_ldap: performing user authorization for replica
radius_xlat: '((sn=replica)(cn=replica))'
radius_xlat: 'ou=radius,dc=mydomain,dc=com'
rlm_ldap: ldap_get_conn: Checking Id: 0
rlm_ldap: ldap_get_conn: Got Id: 0
rlm_ldap: attempting LDAP reconnection
rlm_ldap: (re)connect to localhost:389, authentication 0
rlm_ldap: bind as
cn=freeradius,ou=admins,ou=radius,dc=mydomain,dc=com/freeradius to
localhost:389
rlm_ldap: waiting for bind result ...
rlm_ldap: Bind was successful
rlm_ldap: performing search in ou=radius,dc=mydomain,dc=com, with filter
((sn=replica)(cn=replica))
rlm_ldap: performing search in
uid=isdn,ou=profiles,ou=radius,dc=mydomain,dc=com, with filter
(objectclass=radiusprofile)
rlm_ldap: Adding radiusFramedRouting as Framed-Routing, value None op=11
rlm_ldap: Adding radiusFramedIPNetmask as Framed-IP-Netmask, value
Re: IPPOOL PROBLEM
Hy, Thanks Nicolas. Sorry, its the first time I work in a UNIX environment. In the configure output I obtained: configure: warning: silently not building rlm_ippool. configure: warning: FAILURE: rlm_ippool requires: libgdbm. After installing the package gdbm-1.8.3, which are the steps I have to follow in order to get rlm_ippool compiled? May I have to repeat all the steps of the installation ( $./configure - $ make - $ make install)? Or is there another way? Thank you very much, Rafa - Original Message - From: Nicolas Baradakis [EMAIL PROTECTED] To: FreeRadius users mailing list freeradius-users@lists.freeradius.org Sent: Tuesday, January 24, 2006 2:01 PM Subject: Re: IPPOOL PROBLE Rafael Roldán wrote: But when I tried to test the ippool module I obtained a segmentation fault when I run radiusd. Please no HTML to the list. If you found a bug in FreeRADIUS, follow the instructions here: http://freeradius.org/radiusd/doc/bugs In my rlm_ippool directory I have: # pwd .../freeradius-1.0.5/src/modules/rlm_ippool # ls acconfig.h config.log configure.in Makefile.in rlm_ippool_tool.c config.h config.statusCVS rlm_ippool.c rlm_ippool_tool.pod config.h.in configureMakefile rlm_ippool_tool.8 # Has the rlm_ippool module compiled well? How can I resolve the problem? It looks like the rlm_ippool module was skipped, read the configure output to find out why. -- Nicolas Baradakis - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
IPPOOL PROBLE
Hy all,
I installed FR 1.0.5 in a Solaris 8
machine:
$ ./configure --localstatedir=/var
--sysconfdir=/etc --with-openssl-libraries=/usr/local/ssl/lib
--with-openssl-includes=/usr/local/ssl/include
$ make
# make install
and all seemed to be OK.
But when I tried to test the ippool module I
obtained a segmentation fault when I run radiusd.
Module: Loaded radutmp radutmp:
filename = "/var/log/radius/radutmp"radutmp: username =
"%{User-Name}"radutmp: case_sensitive = yesradutmp:
check_with_nas = yesradutmp: perm = 384radutmp: callerid =
yesModule: Instantiated radutmp (radutmp) Segmentation Fault - core
dumped
In my rlm_ippool directory I have:
#
pwd.../freeradius-1.0.5/src/modules/rlm_ippool
#
lsacconfig.h
config.log
configure.in
Makefile.in
rlm_ippool_tool.cconfig.h
config.status
CVS
rlm_ippool.c
rlm_ippool_tool.podconfig.h.in
configure
Makefile
rlm_ippool_tool.8#
Has the rlm_ippool module compiled well?
How can I resolve the problem?
Thank you very much
Rafa
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
state of art of freeradius
Hy all, I would like to know your opinion about the following issues: Which is the most common use of the freeradius server in your particular cases? Which version are you using? is it stable? What problems have you found using freeradius (during installation, configuration, use...)? My objective is writing a document trying to reflect the state of art of the freeradius server. Thanks a lot for you help Best regards from Madrid Rafa - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
MYSQL installation for interaction with freeradius
Hy all, I am testing freeradius 1.0.5 in a solaris 8 machine and it really satisfied me. Now I want to test freeradius with MYSQL. So first, I am going to install the MYSQL software. When I visit the download page (http://dev.mysql.com/downloads/mysql/5.0.html), I see there are three software package options(standard, max and debug). Also, reading the document "Freeradius and MYSQL" (http://www.frontios.com/freeradius.html), I read that I have to make sure to install the MYSQL development headers installed. Which of these MYSQL packages do you recommend me to interact with freeradius? Thank you very much, Rafa - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Problem with rlm_counter in compiling
Hy all, I am trying to install freeradius 1.0.5 in a solaris 8 machine. When I run make, I obtain the following error: ... rlm_counter.c:38:18: gdbm.h: No such file or directoryrlm_counter.c:84: parse error before "GDBM_FILE"rlm_counter.c:84: warning: no semicolon at end of struct or unionrlm_counter.c:88: parse error before '}' tokenrlm_counter.c:88: warning: type defaults to `int' in declaration of `rlm_counter_t'rlm_counter.c:88: warning: data definition has no type or storage classrlm_counter.c:116: parse error before ')' tokenrlm_counter.c:116: initializer element is not constantrlm_counter.c:116: (near initialization for `module_config[0].offset')rlm_counter.c:116: warning: missing initializerrlm_counter.c:116: warning: (near initialization for `module_config[0].offset')rlm_counter.c:116: initializer element is not constantrlm_counter.c:116: (near initialization for `module_config[0]')rlm_counter.c:117: parse error before ')' tokenrlm_counter.c:117: initializer element is not constantrlm_counter.c:117: (near initialization for `module_config[1].offset')rlm_counter.c:117: warning: missing initializerrlm_counter.c:117: warning: (near initialization for `module_config[1].offset')rlm_counter.c:117: initializer element is not constantrlm_counter.c:117: (near initialization for `module_config[1]')rlm_counter.c:118: parse error before ')' tokenrlm_counter.c:118: initializer element is not constantrlm_counter.c:118: (near initialization for `module_config[2].offset')rlm_counter.c:118: warning: missing initializerrlm_counter.c:118: warning: (near initialization for `module_config[2].offset')rlm_counter.c:118: initializer element is not constantrlm_counter.c:118: (near initialization for `module_config[2]')rlm_counter.c:119: parse error before ')' tokenrlm_counter.c:119: initializer element is not constantrlm_counter.c:119: (near initialization for `module_config[3].offset')rlm_counter.c:119: warning: missing initializerrlm_counter.c:119: warning: (near initialization for `module_config[3].offset')rlm_counter.c:119: initializer element is not constantrlm_counter.c:119: (near initialization for `module_config[3]')rlm_counter.c:120: parse error before ')' tokenrlm_counter.c:120: initializer element is not constantrlm_counter.c:120: (near initialization for `module_config[4].offset')rlm_counter.c:120: warning: missing initializerrlm_counter.c:120: warning: (near initialization for `module_config[4].offset')rlm_counter.c:120: initializer element is not constantrlm_counter.c:120: (near initialization for `module_config[4]')rlm_counter.c:121: parse error before ')' tokenrlm_counter.c:121: initializer element is not constantrlm_counter.c:121: (near initialization for `module_config[5].offset')rlm_counter.c:121: warning: missing initializerrlm_counter.c:121: warning: (near initialization for `module_config[5].offset')rlm_counter.c:121: initializer element is not constantrlm_counter.c:121: (near initialization for `module_config[5]')rlm_counter.c:122: parse error before ')' tokenrlm_counter.c:122: initializer element is not constantrlm_counter.c:122: (near initialization for `module_config[6].offset')rlm_counter.c:122: warning: missing initializerrlm_counter.c:122: warning: (near initialization for `module_config[6].offset')rlm_counter.c:122: initializer element is not constantrlm_counter.c:122: (near initialization for `module_config[6]')rlm_counter.c:123: parse error before ')' tokenrlm_counter.c:123: initializer element is not constantrlm_counter.c:123: (near initialization for `module_config[7].offset')rlm_counter.c:123: warning: missing initializerrlm_counter.c:123: warning: (near initialization for `module_config[7].offset')rlm_counter.c:123: initializer element is not constantrlm_counter.c:123: (near initialization for `module_config[7]')rlm_counter.c:124: initializer element is not constantrlm_counter.c:124: (near initialization for `module_config[8]')rlm_counter.c: In function `counter_cmp':rlm_counter.c:138: `data' undeclared (first use in this function)rlm_counter.c:138: (Each undeclared identifier is reported only oncerlm_counter.c:138: for each function it appears in.)rlm_counter.c:138: parse error before ')' tokenrlm_counter.c:139: `datum' undeclared (first use in this function)rlm_counter.c:156: `key_datum' undeclared (first use in this function)rlm_counter.c:159: `count_datum' undeclared (first use in this function)rlm_counter.c:159: warning: implicit declaration of function `gdbm_fetch'rlm_counter.c:133: warning: unused parameter `instance'rlm_counter.c: At top level:rlm_counter.c:171: parse error before '*' tokenrlm_counter.c:172: warning: function declaration isn't a prototyperlm_counter.c: In function `add_defaults':rlm_counter.c:173: `datum' undeclared (first use in this function)rlm_counter.c:173: parse error before "key_datum"rlm_counter.c:180: `key_datum' undeclared (first use in this
Re: Problem with rlm_counter in compiling
Hy Michael, Thanks a lot for your extense response. I have deleted rlm_counter and rlm_ippool directory (both of them need gdbm.h) because I only want to test the proxy functionality of freeradius. But, after this I have installed freeradius 1.0.5 in another solaris 8 machine and here I haven´t had any problem (and the gdbm.h file doesn´t exits in this machine too, I tried to find it with the find command wihout any result). I don´t know what I am doing different... Best regards from Madrid Rafa - Original Message - From: Michael Mitchell [EMAIL PROTECTED] To: FreeRadius users mailing list freeradius-users@lists.freeradius.org Sent: Wednesday, December 21, 2005 11:41 AM Subject: Re: Problem with rlm_counter in compiling Do you need to use rlm_counter? If not, you can simply delete the rlm_counter directory and run configure again then make, or delete rlm_counter from the MODULES item in Make.inc, and run make again. The problem is that the compiler can't find gdbm.h. It may not be installed on your system, in which case the configure process should have removed rlm_counter from the Makefiles. If gdbm.h does exist, the configure script may not have updated the Makefile with the location of gdbm.h. If you know where gdbm.h exists on your system (config.log may give you some hints) then you can update RLM_CFLAGS in the Makefile in rlm_counter manually and see if you get any further. Please report back with your progress, as it may help to improve the configure and Make process for the future. Building freeRADIUS on Solaris always seems to be a little troublesome - I've had various problems with the configure scripts on Solaris 9 and 10 in the past. If none of this makes sense, shoot me an email and I can try to walk you through it in a bit more detail. regards, Mike Rafael Roldán wrote: Hy all, I am trying to install freeradius 1.0.5 in a solaris 8 machine. When I run make, I obtain the following error: ... rlm_counter.c:38:18: gdbm.h: No such file or directory rlm_counter.c:84: parse error before GDBM_FILE rlm_counter.c:84: warning: no semicolon at end of struct or union rlm_counter.c:88: parse error before '}' token rlm_counter.c:88: warning: type defaults to `int' in declaration of `rlm_counter_t' rlm_counter.c:88: warning: data definition has no type or storage class rlm_counter.c:116: parse error before ')' token rlm_counter.c:116: initializer element is not constant rlm_counter.c:116: (near initialization for `module_config[0].offset') rlm_counter.c:116: warning: missing initializer rlm_counter.c:116: warning: (near initialization for `module_config[0].offset') rlm_counter.c:116: initializer element is not constant rlm_counter.c:116: (near initialization for `module_config[0]') rlm_counter.c:117: parse error before ')' token rlm_counter.c:117: initializer element is not constant rlm_counter.c:117: (near initialization for `module_config[1].offset') rlm_counter.c:117: warning: missing initializer rlm_counter.c:117: warning: (near initialization for `module_config[1].offset') rlm_counter.c:117: initializer element is not constant rlm_counter.c:117: (near initialization for `module_config[1]') rlm_counter.c:118: parse error before ')' token rlm_counter.c:118: initializer element is not constant rlm_counter.c:118: (near initialization for `module_config[2].offset') rlm_counter.c:118: warning: missing initializer rlm_counter.c:118: warning: (near initialization for `module_config[2].offset') rlm_counter.c:118: initializer element is not constant rlm_counter.c:118: (near initialization for `module_config[2]') rlm_counter.c:119: parse error before ')' token rlm_counter.c:119: initializer element is not constant rlm_counter.c:119: (near initialization for `module_config[3].offset') rlm_counter.c:119: warning: missing initializer rlm_counter.c:119: warning: (near initialization for `module_config[3].offset') rlm_counter.c:119: initializer element is not constant rlm_counter.c:119: (near initialization for `module_config[3]') rlm_counter.c:120: parse error before ')' token rlm_counter.c:120: initializer element is not constant rlm_counter.c:120: (near initialization for `module_config[4].offset') rlm_counter.c:120: warning: missing initializer rlm_counter.c:120: warning: (near initialization for `module_config[4].offset') rlm_counter.c:120: initializer element is not constant rlm_counter.c:120: (near initialization for `module_config[4]') rlm_counter.c:121: parse error before ')' token rlm_counter.c:121: initializer element is not constant rlm_counter.c:121: (near initialization for `module_config[5].offset') rlm_counter.c:121: warning: missing initializer rlm_counter.c:121: warning: (near initialization for `module_config[5].offset') rlm_counter.c:121: initializer element is not constant rlm_counter.c:121: (near initialization for `module_config[5
Re: anybody installed freeradius-1.0.5 on Solaris 8 successfully?
Yes, yesterday, and it works fine... - Original Message - From: Qin Zhen To: freeradius-users@lists.freeradius.org Sent: Wednesday, December 14, 2005 7:57 AM Subject: anybody installed freeradius-1.0.5 on Solaris 8 successfully? Hello All, seems solaris 8 and freeradius-1.0.5 dont like each other.. after i installed it, it gave segmentation fault when i tried to run it. anybody has installed and run it successfully on solaris 8? cheers, QZ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
