rad_recv: Access-Request packet from host 172.41.10.71 port 42678, id=153, length=61
        User-Name = "azerty5"
        User-Password = "xxxxxxxxx"
        NAS-IP-Address = 172.30.10.71
        NAS-Port = 1812
+- entering group authorize {...}
++[preprocess] returns ok
++[chap] returns noop
[suffix] No '@' in User-Name = "azerty5", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
++[files] returns noop
++[expiration] returns noop
++[logintime] returns noop
[pap] WARNING! No "known good" password found for the user. Authentication may fail because of this.
++[pap] returns noop
No authenticate method (Auth-Type) configuration found for the request: Rejecting the user
Failed to authenticate the user.
Login incorrect: [azerty5/xxxxxxxx] (from client SRV-RADIUS port 1812)
Using Post-Auth-Type Reject
+- entering group REJECT {...}
[attr_filter.access_reject]     expand: %{User-Name} -> lndakpaze
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 0 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 0
Sending Access-Reject of id 153 to 172.30.10.71 port 42678
Waking up in 4.9 seconds.
Cleaning up request 0 ID 153 with timestamp +7

thank you for your help

2009/3/30 John Dennis <jdennis@redhat.com>

David N'DAKPAZE wrote:

I am re-intalling freeradius and when I run make after ./configure --disable-shared I have this:
Don't make matters worse by trying to defeat loadable modules. Go back and figure out why the loader can't find the modules. A good place to start is looking to see what libdir was defined as when you ran configure and/or look to see where the modules were installed when you ran "make install" (should be the same place and by default is /usr/lib/freeradius). Are the modules there? Was rpath set when the modules were linked? Was ldconfig run so the loader knows where to find them?

>radiusd: #### Instantiating modules ####
> instantiate {
>/usr/local/etc/raddb/modules/exec[24]: Failed to link to module
>'rlm_exec': rlm_exec.a: cannot open shared object file: No such file
>or directory
>Errors initializing modules
>

Same applies to *any* missing library.If your linker doesn't have the
correct path it doesn't matter what's the library called.
-- 
John Dennis <jdennis@redhat.com>

Looking to carve out IT costs?
www.redhat.com/carveoutcosts/
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html