OpenOTP

[/dev/null]

Hat jemand hier den OpenOTP von Rcdevs am laufen?

Ich frage, weil es mir konkret um die Radius Bridge geht, die ich aktuell einfach nicht zum fliegen bringe! :-(

Kurz zum System: Virtuelle Debian sqeeze Büchse

Code: Select all

root@admin:/opt/radiusd/libexec# cat /proc/version
Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-30) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 05:46:49 UTC 2011

Das Problem dabei scheint im Modul rlm_pap zu liegen, da:

Code: Select all

root@admin:/opt/radiusd/libexec# ./openotp-radiusd -X -f
FreeRADIUS Version 2.1.11, for host i686-pc-linux-gnu, built on Aug  4 2011 at 1                                                              1:11:00
Copyright (C) 1999-2009 The FreeRADIUS server project and contributors.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
You may redistribute copies of FreeRADIUS under the terms of the
GNU General Public License v2.
Starting - reading configuration files ...
including configuration file /opt/radiusd/conf/radiusd.conf
including configuration file /opt/radiusd/conf/clients.conf
including configuration file /opt/radiusd/conf/openotp.conf
main {
        user = "radiusd"
        group = "radiusd"
        allow_core_dumps = no
}
including dictionary file /opt/radiusd/conf/dictionary
main {
        name = "radiusd"
        prefix = "/opt/radiusd"
        localstatedir = "/opt/radiusd/var"
        sbindir = "/opt/radiusd/sbin"
        logdir = "/opt/radiusd/logs"
        run_dir = "/opt/radiusd/var/run/radiusd"
        libdir = "/opt/radiusd/lib"
        radacctdir = "/opt/radiusd/logs/radacct"
        hostname_lookups = no
        max_request_time = 30
        cleanup_delay = 5
        max_requests = 1024
        pidfile = "/opt/radiusd/logs/radiusd.pid"
        checkrad = "/opt/radiusd/libexec/checkrad"
        debug_level = 0
        proxy_requests = yes
 log {
        stripped_names = no
        auth = yes
        auth_badpass = yes
        auth_goodpass = yes
 }
 security {
        max_attributes = 200
        reject_delay = 1
        status_server = yes
 }
}
radiusd: #### Loading Realms and Home Servers ####
radiusd: #### Loading Clients ####
 client 0.0.0.0/0 {
        require_message_authenticator = no
        secret = "testing123"
        shortname = "any"
 }
radiusd: #### Instantiating modules ####
 instantiate {
/opt/radiusd/conf/radiusd.conf[541]: Failed to link to module 'rlm_pap': rlm_pap                                                              .so: cannot open shared object file: No such file or directory

Jemadn ne Idee?

Beste Grüße
/dev/null

[Joe User]

Befindet sich die rlm_pap.so denn dort, wo Dein Radiusd sie erwartet?

[/dev/null]

Ich denke schon, das ganze wird als self-install Paket geliefert und legt sich automatisch in /opt/radiusd..

Code: Select all

root@admin:/opt/radiusd/libexec# find /opt/radiusd -name rlm_pap.so
/opt/radiusd/lib/modules/rlm_pap.so

[/dev/null]

So viel dazu... Das Modul war echt an der falschen Stelle... :-/ (AUTOinstall :-D))

[Joe User]

Dann schreib am Besten auch gleich einen Bugreport, damit es beim nächsten Update behoben wird ;)

[/dev/null]

Schon passiert! ;-)