Re : Compile problems on Solaris 10
gcc -Wall -fPIC -c pam_radius_auth.c -o pam_radius_auth.o In file included from pam_radius_auth.h:23, from pam_radius_auth.c:63: md5.h:21: error: syntax error before 'u_int32_t' md5.h:21: warning: no semicolon at end of struct or union check out what is going on in pam_radius_auth.h on line 23 ================================================== Benjamin K. Eshun ----- Message d'origine ---- De : Paul Goodman <pgoodman@ucar.edu> À : freeradius-users@lists.freeradius.org Envoyé le : Jeudi, 15 Mars 2007, 17h34mn 51s Objet : Compile problems on Solaris 10 I am trying to compile the pam_radius-1.3.16 modules on a Solaris 10 system, but when I run make, I get the following error: gcc -Wall -fPIC -c pam_radius_auth.c -o pam_radius_auth.o In file included from pam_radius_auth.h:23, from pam_radius_auth.c:63: md5.h:21: error: syntax error before 'u_int32_t' md5.h:21: warning: no semicolon at end of struct or union md5.h:22: warning: type defaults to 'int' in declaration of 'bits' md5.h:22: warning: data definition has no type or storage class md5.h:24: error: syntax error before '}' token md5.h:29: error: syntax error before 'buf' pam_radius_auth.c: In function 'get_random_vector': pam_radius_auth.c:350: error: storage size of 'my_md5' isn't known pam_radius_auth.c:350: warning: unused variable 'my_md5' pam_radius_auth.c: In function 'get_accounting_vector': pam_radius_auth.c:382: error: storage size of 'my_md5' isn't known pam_radius_auth.c:382: warning: unused variable 'my_md5' pam_radius_auth.c: In function 'verify_packet': pam_radius_auth.c:400: error: storage size of 'my_md5' isn't known pam_radius_auth.c:400: warning: unused variable 'my_md5' pam_radius_auth.c: In function 'add_password': pam_radius_auth.c:497: error: storage size of 'md5_secret' isn't known pam_radius_auth.c:497: error: storage size of 'my_md5' isn't known pam_radius_auth.c:497: warning: unused variable 'my_md5' pam_radius_auth.c:497: warning: unused variable 'md5_secret' pam_radius_auth.c: In function 'rad_converse': pam_radius_auth.c:1016: warning: passing argument 3 of 'pam_get_item' from incompatible pointer type pam_radius_auth.c:1019: warning: passing argument 2 of 'conv->conv' from incompatible pointer type pam_radius_auth.c: In function 'pam_sm_authenticate': pam_radius_auth.c:1071: warning: passing argument 2 of 'pam_get_user' from incompatible pointer type pam_radius_auth.c:1099: warning: passing argument 3 of 'pam_get_item' from incompatible pointer type pam_radius_auth.c:1113: warning: passing argument 3 of 'pam_get_item' from incompatible pointer type pam_radius_auth.c:1146: warning: passing argument 3 of 'pam_get_item' from incompatible pointer type pam_radius_auth.c: In function 'pam_private_session': pam_radius_auth.c:1267: warning: passing argument 2 of 'pam_get_user' from incompatible pointer type pam_radius_auth.c:1288: warning: passing argument 3 of 'pam_get_item' from incompatible pointer type pam_radius_auth.c: In function 'pam_sm_chauthtok': pam_radius_auth.c:1374: warning: passing argument 2 of 'pam_get_user' from incompatible pointer type pam_radius_auth.c:1395: warning: passing argument 3 of 'pam_get_item' from incompatible pointer type pam_radius_auth.c:1404: warning: passing argument 3 of 'pam_get_item' from incompatible pointer type pam_radius_auth.c:1409: warning: passing argument 3 of 'pam_get_item' from incompatible pointer type gmake: *** [pam_radius_auth.o] Error 1 The same is true when I use the Sun cc (Studio 11 compiler). I am using gcc 4.0.2 (the most recent version I could get to run on Solaris). Output of uname -a is: SunOS xxxx 5.10 Generic_118833-36 sun4u sparc SUNW,A70 Does anyone have a suggestion as to how to modify the header file to make it work or know where I can find pre-compiled modules for Solaris? - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Hello I am using freeradius 1.1.3 in freebsd 6 with mysql database. My problem is if I enable the calling-station-id in freeradius radcheck table the rejected message is shown as below in radius log Fri Mar 16 16:56:58 2007 : Info: rlm_sql (sql): No matching entry in the database for request from user [test] Fri Mar 16 16:56:58 2007 : Auth: Login incorrect (rlm_chap: Clear text password not available): [test] (from client pppoe2 port 568 cli 0:7:95:10:73:9e) The rejected message should be calling station id not allowed. Why I am not getting the valid rejected reason. Same happens for Expired accounts too. radius.log for Expiration accounts show: Fri Mar 16 16:56:38 2007 : Auth: Login incorrect: [test2] (from client pppoe2 port 566 cli 0:7:95:10:73:9e) I have seetup radcheck table as follows: +----+----------------+----------------+------------------+------+ | id | UserName | Attribute | Value | Op | +----+----------------+----------------+------------------+------+ | 1 | test | User-Password | wilma | == | | 2 | test | Expiration | 10 Feb 2007 | := | | 2 | test | Calling-Station-Id | 0:c0:26:8b:2a:e7 | == | +----+----------------+----------------+------------------+------+
Bishal wrote:
I am using freeradius 1.1.3 in freebsd 6 with mysql database. My problem is if I enable the calling-station-id in freeradius radcheck table the rejected message is shown as below in radius log
Fri Mar 16 16:56:58 2007 : Info: rlm_sql (sql): No matching entry in the database for request from user [test] Fri Mar 16 16:56:58 2007 : Auth: Login incorrect (rlm_chap: Clear text password not available): [test] (from client pppoe2 port 568 cli 0:7:95:10:73:9e)
The rejected message should be calling station id not allowed.
Why do you say that? The user is getting rejected because you had a set of requirements he had to meet in order to be authenticated, and he didn't meet those requirements. Understand that some people have MANY policies. When a user is accepted or rejected, they don't want to see hundreds of messages saying "matched policy X", or "didn't match policy Y". Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (3)
-
Alan DeKok -
Bishal -
Eshun Benjamin