But that means that the authentication is successful? If I have the NAS and Supplicant improperly set, I do not understand because it rejects the response radius. What do these lines?: rlm_realm: No '@' in User-Name = "cert", looking up realm NULL rlm_realm: No such realm "NULL" Thanks Alan.
What do these lines?:
rlm_realm: No '@' in User-Name = "cert", looking up realm NULL rlm_realm: No such realm "NULL"
You haven't configured NULL domain (in proxy.conf) for users without the domain. Like most people. It's not a problem. Ivan Kalik Kalik Informatika ISP
tnt@kalik.net wrote:
What do these lines?:
rlm_realm: No '@' in User-Name = "cert", looking up realm NULL rlm_realm: No such realm "NULL"
You haven't configured NULL domain (in proxy.conf) for users without the domain. Like most people. It's not a problem.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
your problem is in supplicant or NAS side not in freeradius. Fernando.
Hi, I am searching a solution to get status information with freeradius 2.0.5. Because of the broken snmp implemantation on 64 bit Linux systems, I can not use snmp. So I tried to use the status interface. I configured a server status as written below. server status { listen { # ONLY Status-Server is allowed to this port. # ALL other packets are ignored. type = status ipaddr = 127.0.0.1 port = 18120 } client admin { ipaddr = 127.0.0.1 secret = adminsecret } # # Simple authorize section. The "Autz-Type Status-Server" # section will work here, too. See "raddb/sites-available/default". authorize { # respond to the Status-Server request. ok } } But the freeradius start fails: Mon Nov 24 13:57:36 2008 : Error: /opt/radius/etc/raddb/sites-enabled/stats[31]: Invalid type "status" in listen section. Is there any idea to get status information ? I can not upgrade to 2.1.x because the rlm_ippool was rewritten and the retention_time patch (which I need) does not work. -- Thoralf Freitag Manager Health Services System Administration Phone: +49 (0) 30 68905-4611 Cellular:+49 (0) 151 1631-4611 Fax: +49 (0) 30 68905-2940 Mail: Thoralf.Freitag@biotronik.com From: Fernando <fbernal@um.es> To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Date: 24.11.08 13:40 Subject: Re: Problems in TLS Sent by: freeradius-users-bounces+thoralf.freitag=biotronik.com@lists.freeradius.org tnt@kalik.net wrote:
What do these lines?:
rlm_realm: No '@' in User-Name = "cert", looking up realm NULL rlm_realm: No such realm "NULL"
You haven't configured NULL domain (in proxy.conf) for users without the domain. Like most people. It's not a problem.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
your problem is in supplicant or NAS side not in freeradius. Fernando. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html www.biotronik.com BIOTRONIK GmbH & Co. KG Woermannkehre 1, 12359 Berlin, Germany Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501 Vertreten durch ihre Komplementaerin: BIOTRONIK Mess- und Therapiegeraete GmbH Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 2918 Geschaeftsfuehrer: Dr. Max Schaldach, Christoph Boehmer, Dr. Werner Braun, Dr. Lothar Krings This email and the information it contains including attachments are confidential and meant only for use by the intended recipient(s); disclosure or copying is strictly prohibited. If you are not addressed, but in the possession of this email, please notify the sender immediately.
thoralf.freitag@biotronik.com wrote:
I am searching a solution to get status information with freeradius 2.0.5. Because of the broken snmp implemantation on 64 bit Linux systems, I can not use snmp. So I tried to use the status interface. I configured a server status as written below.
This is not supported in 2.0.5.
But the freeradius start fails:
Because it's not supported.
Is there any idea to get status information ?
You can't.
I can not upgrade to 2.1.x because the rlm_ippool was rewritten and the retention_time patch (which I need) does not work.
So use the 2.0.5 rlm_ippool module with 2.1.x. Or, update the patch to work with 2.1.x. It shouldn't be hard. The module was *not* re-written. Instead, a bunch of "DEBUG" words were changed to "RDEBUG". This is a very small change. Alan DeKok.
attached is the updated patch. User need this should add # retention-time: If not zero specifies the amount of seconds to wait # before releasing an entry after receiving an acct Stop packet. # Default: 0 retention-time = 0 to the raddb/modules/ippool configuration. -- Thoralf Freitag Manager Health Services System Administration Phone: +49 (0) 30 68905-4611 Cellular:+49 (0) 151 1631-4611 Fax: +49 (0) 30 68905-2940 Mail: Thoralf.Freitag@biotronik.com www.biotronik.com BIOTRONIK GmbH & Co. KG Woermannkehre 1, 12359 Berlin, Germany Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501 Vertreten durch ihre Komplementaerin: BIOTRONIK Mess- und Therapiegeraete GmbH Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 2918 Geschaeftsfuehrer: Dr. Max Schaldach, Christoph Boehmer, Dr. Werner Braun, Dr. Lothar Krings This email and the information it contains including attachments are confidential and meant only for use by the intended recipient(s); disclosure or copying is strictly prohibited. If you are not addressed, but in the possession of this email, please notify the sender immediately.
participants (5)
-
Alan DeKok -
Fernando -
Martin Silvero -
thoralf.freitag＠biotronik.com -
tnt＠kalik.net