May 2008 - Freeradius-Users - lists.freeradius.org

Triggering of billing engine post-acc
by Pete Kay 25 May '08

25 May '08

Hi, I have a question about triggering my custom billing engine after accounting info is stored in the DB. Does FreeRadius has any event mechanism or somewhere that I can embed a script to trigger my billing calculation? Thanks in advance for your suggestion. Regards, Pete

3 4

Client Certificate!
by Kwok Sianbin 25 May '08

25 May '08

Hi Alan, As you previous email mention, I need to run the server script. Do you mean the script in the README file that come with Freeradius (/raddb/scripts). # make server.pem # make server.csr I just started to use the Linux hence I am not quite familiar with it. ----- Original Message ---- From: Alan DeKok <aland(a)deployingradius.com> To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Sent: Saturday, May 24, 2008 2:00:22 PM Subject: Re: Re : EAP-TTLS w/MS-CHAPv2 Kwok Sianbin wrote: ... > #radtest MarsNet Mars123 localhost 0 testing123 > User-Name = "MarsNet" ... > if I change the configuration in radiusd.conf to bind to particular IP > address (eth0) then about radtest failed to Accept. Because you're sending packets to localhost? Do you know what different network interfaces are? ... > ++[eap] returns handled > Reply-Message = "Hello, MarsNet" > EAP-Message = 0x010200060d20 > Message-Authenticator = 0x00000000000000000000000000000000 > State = 0x58961ab6589417883d2fb3d577435665 > Finished request 2. > Going to the next request > Waking up in 4.9 seconds. This is in the FAQ. You are using a Microsoft client, and the server certificate doesn't have the correct OID's. Use the certificate generation scripts that come with the server. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

1 0

Re : EAP-TTLS w/MS-CHAPv2
by Joel MBA OYONE 25 May '08

25 May '08

> You'll also need a raddb/sites-enabled/inner-tunnel file. It's not > installed in 2.0.3. This was fixed in 2.0.4. what is "inner-tunnel file intend for ?? __________________________________________________ Do You Yahoo!? En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités http://mail.yahoo.fr Yahoo! Mail

4 5

Dear freeradius-users@list.xs4all.nl May 83% 0FF
by VIAGRA � Official Site 24 May '08

24 May '08

1 0

Configuring authentication against mysql
by Pete Kay 24 May '08

24 May '08

Hi, I am using Free Radius 2.0.4, in my radiusd.conf, I have added the authorize and authenticate sections inside the module section, but I still can't authenticate user. I don't know how to configure radiusd.conf to get it to work. Any help will be greatly appreciated. Thanks in advance for your help. Here is part of my radiusd.conf server { # line to add authorize { preprocess auth_log chap mschap digest suffix eap sql } authenticate { Auth-Type PAP { pap } Auth-Type CHAP { chap } Auth-Type MS-CHAP { mschap } digest unix eap } accounting { detail acct_unique sql unix radutmp } post-proxy { } } But still, when launch radiusd -X, I don't see any DB calling stuff. Here is the output of radiusd -X, debian:/usr/local/etc/raddb# radiusd -X FreeRADIUS Version 2.0.4, for host i686-pc-linux-gnu, built on May 25 2008 at 00:39:50 Copyright (C) 1999-2008 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. Starting - reading configuration files ... including configuration file /usr/local/etc/raddb/radiusd.conf including configuration file /usr/local/etc/raddb/proxy.conf including configuration file /usr/local/etc/raddb/clients.conf including configuration file /usr/local/etc/raddb/snmp.conf including configuration file /usr/local/etc/raddb/eap.conf including configuration file /usr/local/etc/raddb/sql.conf including configuration file /usr/local/etc/raddb/sql/mysql/dialup.conf including configuration file /usr/local/etc/raddb/sql/mysql/counter.conf including configuration file /usr/local/etc/raddb/policy.conf including files in directory /usr/local/etc/raddb/sites-enabled/ including configuration file /usr/local/etc/raddb/sites-enabled/default including configuration file /usr/local/etc/raddb/sites-enabled/inner-tunnel including dictionary file /usr/local/etc/raddb/dictionary main { prefix = "/usr/local" localstatedir = "/usr/local/var" logdir = "/usr/local/var/log/radius" libdir = "/usr/local/lib" radacctdir = "/usr/local/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 allow_core_dumps = no pidfile = "/usr/local/var/run/radiusd/radiusd.pid" checkrad = "/usr/local/sbin/checkrad" debug_level = 0 proxy_requests = yes security { max_attributes = 200 reject_delay = 1 status_server = yes } } client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "openser" nastype = "other" } radiusd: #### Loading Realms and Home Servers #### proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 zombie_period = 40 status_check = "status-server" ping_check = "none" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } realm DEFAULT { authhost = 192.168.1.104:1600 accthost = 192.168.1.104:1601 secret = openser } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating exec exec { wait = yes input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating expr Module: Linked to module rlm_expiration Module: Instantiating expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating chap Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/usr/local/var/log/radius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "md5" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } rlm_eap: Ignoring EAP-Type/tls because we do not have OpenSSL support. rlm_eap: Ignoring EAP-Type/ttls because we do not have OpenSSL support. rlm_eap: Ignoring EAP-Type/peap because we do not have OpenSSL support. Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/usr/local/var/log/radius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Linked to module rlm_attr_filter Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/usr/local/etc/raddb/attrs.access_reject" key = "%{User-Name}" } } } server { modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating preprocess preprocess { huntgroups = "/usr/local/etc/raddb/huntgroups" hints = "/usr/local/etc/raddb/hints" with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = no with_alvarion_vsa_hack = no } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating detail detail { detailfile = "/usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Instantiating attr_filter.accounting_response attr_filter attr_filter.accounting_response { attrsfile = "/usr/local/etc/raddb/attrs.accounting_response" key = "%{User-Name}" } Module: Checking session {...} for more modules to load Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load } } radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on proxy address * port 1814 Ready to process requests. User-Name = "1005(a)192.168.1.104" User-Password = "1234" NAS-IP-Address = 255.255.255.255 NAS-Port = 1645 +- entering group authorize ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop rlm_realm: Looking up realm "192.168.1.104" for User-Name = " 1005(a)192.168.1.104" rlm_realm: Found realm "DEFAULT" rlm_realm: Adding Stripped-User-Name = "1005" rlm_realm: Adding Realm = "DEFAULT" rlm_realm: Proxying request from user 1005 to realm DEFAULT rlm_realm: Preparing to proxy authentication request to realm "DEFAULT" ++[suffix] returns updated

2 1

LDAP Module only for Authorization and not for Authentication
by HRZ Konten 24 May '08

24 May '08

Hallo, I have Freeradius 1.1.7 and use it to check user and password with pam module. The pam module uses pam_afs.so library to check in the kerberos IV server. I want to keep this configuration but additionaly to make a check for groups in LDAP. Something like: 1. Authorize Huntgroup-Name== xxx, Ldap-Group==xxx.... 2. Authenticate user + password through pam Can I do authorization with LDAP and then authenticate with pam? Then I don't want to provide any passwords in LDAP. Thay must stay in the kerberos IV server. When I use a remote LDAP-Server, should I configure some special modules during the installation of radius? Thanks. Regards Irina

2 3

Session-Timeout conditionally appearing
by Tuc at T-B-O-H.NET 23 May '08

23 May '08

Hi, I've run this on FR2.0.3 and 2.0.4, MySQL and Postgresql, and I seem to see a pattern. I'm not sure if its the correct behaviour or not. Using counters, I add "Max-All-Session := 123" into my database for a user. when I run radtest, I get : setup# radtest hotspot ICANSEE localhost 1212 testing123 User-Name = "hotspot" User-Password = "ICANSEE" NAS-IP-Address = 192.168.3.128 NAS-Port = 1212 Idle-Timeout = 900 I would think I would see a : Session-Timeout = 123 If, though, I add a record for a 122 second session into radacct and run again, I see : setup# radtest hotspot ICANSEE localhost 1212 testing123 User-Name = "hotspot" User-Password = "ICANSEE" NAS-IP-Address = 192.168.3.128 NAS-Port = 1212 Idle-Timeout = 900 Session-Timeout = 1 Is Session-Timeout not showing due to misconfiguration on my part (Fairly stock configuration), or because of some other reason? Thanks, Tuc

3 3

unable to authenticate
by David Trinh 23 May '08

23 May '08

I would like to test the security feature 802.1x EAP-TLS of our product. I set up FreeRadius and used the demo certificates. However, the server keeps rejecting access. I noticed that the server complains about <no User Password attribute>, but the wireless device (supplicant) does not have a place for me to enter the password, only the login. So how to I configure FreeRadius to ignore the password attribute? Please help. I have included the debug log and the user.conf file. Here is the log when run in debug mode: Ready to process requests. rad_recv: Access-Request packet from host 192.168.254.26:1026, id=4, length=208 Message-Authenticator = 0x9075ab275b5d9dca389e8646e992305e Service-Type = Framed-User User-Name = "FreeRADIUS.net-Client" Framed-MTU = 1488 Called-Station-Id = "00-0B-6B-85-C3-68:radius" Calling-Station-Id = "00-0B-6B-84-44-C7" NAS-Identifier = "TEst" NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x0204001a01467265655241444955532e6e65742d436c69656e74 NAS-IP-Address = 192.168.254.26 NAS-Port = 1 NAS-Port-Id = "STA port # 1" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 radius_xlat: '../var/log/radius/radacct/192.168.254.26/auth-detail-20080522.log' rlm_detail: ../var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d.log expands to ../var/log/radius/radacct/192.168.254.26/auth-detail-20080522. log modcall[authorize]: module "auth_log" 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 = "FreeRADIUS.net-Client", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: EAP packet type response id 4 length 26 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 0 users: Matched entry FreeRADIUS.net-Client at line 95 modcall[authorize]: module "files" returns ok for request 0 rlm_pap: WARNING! No "known good" password found for the user. Authentication may fail because of this. modcall[authorize]: module "pap" returns noop for request 0 modcall: leaving group authorize (returns updated) for request 0 rad_check_password: Found Auth-Type EAP auth: type "EAP" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 0 rlm_eap: EAP Identity rlm_eap: processing type tls rlm_eap_tls: Requiring client certificate rlm_eap_tls: Initiate rlm_eap_tls: Start returned 1 modcall[authenticate]: module "eap" returns handled for request 0 modcall: leaving group authenticate (returns handled) for request 0 Sending Access-Challenge of id 4 to 192.168.254.26 port 1026 EAP-Message = 0x010500060d20 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x81d7452a456ad519df0020eba90a201b Finished request 0 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... rad_recv: Access-Request packet from host 192.168.254.26:1026, id=5, length=206 Message-Authenticator = 0xb6900d65edf9c188d8eb45a273d4ceb0 Service-Type = Framed-User User-Name = "FreeRADIUS.net-Client" Framed-MTU = 1488 State = 0x81d7452a456ad519df0020eba90a201b Called-Station-Id = "00-0B-6B-85-C3-68:radius" Calling-Station-Id = "00-0B-6B-84-44-C7" NAS-Identifier = "TEst" NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x020500060300 NAS-IP-Address = 192.168.254.26 NAS-Port = 1 NAS-Port-Id = "STA port # 1" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 1 modcall[authorize]: module "preprocess" returns ok for request 1 radius_xlat: '../var/log/radius/radacct/192.168.254.26/auth-detail-20080522.log' rlm_detail: ../var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d.log expands to ../var/log/radius/radacct/192.168.254.26/auth-detail-20080522. log modcall[authorize]: module "auth_log" returns ok for request 1 modcall[authorize]: module "chap" returns noop for request 1 modcall[authorize]: module "mschap" returns noop for request 1 rlm_realm: No '@' in User-Name = "FreeRADIUS.net-Client", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 1 rlm_eap: EAP packet type response id 5 length 6 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 1 users: Matched entry FreeRADIUS.net-Client at line 95 modcall[authorize]: module "files" returns ok for request 1 rlm_pap: WARNING! No "known good" password found for the user. Authentication may fail because of this. modcall[authorize]: module "pap" returns noop for request 1 modcall: leaving group authorize (returns updated) for request 1 rad_check_password: Found Auth-Type EAP auth: type "EAP" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 1 rlm_eap: Request found, released from the list rlm_eap: EAP NAK rlm_eap: NAK asked for bad type 0 rlm_eap: Failed in EAP select modcall[authenticate]: module "eap" returns invalid for request 1 modcall: leaving group authenticate (returns invalid) for request 1 auth: Failed to validate the user. Login incorrect: [FreeRADIUS.net-Client/<no User-Password attribute>] (from client radius port 1 cli 00-0B-6B-84-44-C7) Delaying request 1 for 1 seconds Finished request 1 Going to the next request Waking up in 6 seconds... rad_recv: Access-Request packet from host 192.168.254.26:1026, id=5, length=206 Sending Access-Reject of id 5 to 192.168.254.26 port 1026 EAP-Message = 0x04050004 Message-Authenticator = 0x00000000000000000000000000000000 --- Walking the entire request list --- ##########This is the user.conf################# .... ############# RFC3580 ################ ## Also the "eap.conf" MUST be modified to include the follow line: ## "use_tunneled_reply = yes" ## the default is "use_tunneled_reply = no" ## this allow the "Tunnel*" AV's to be passed outside the eap tunnel ## otherwise the switch will NOT see the VLAN to place the port into #### Comments added by Jeff Reilly #### testuser User-Password == "testpw" #FreeRADIUS.net-Client User-Password == "demo" rfc3580 User-Password == "demo" Tunnel-Type = "VLAN", Tunnel-Medium-Type = "IEEE-802", Tunnel-Private-Group-Id = "1", Reply-Message = "Hello, %u" FreeRADIUS.net-Client Auth-Type := EAP # # This is a complete entry for "steve". Note that there is no Fall-Through # entry so that no DEFAULT entry will be used, and the user will NOT # get any attributes in addition to the ones listed here. # #steve Auth-Type := Local, User-Password == "testing" # Service-Type = Framed-User, # Framed-Protocol = PPP, # Framed-IP-Address = 172.16.3.33, # Framed-IP-Netmask = 255.255.255.0, # Framed-Routing = Broadcast-Listen, # Framed-Filter-Id = "std.ppp", # Framed-MTU = 1500, # Framed-Compression = Van-Jacobsen-TCP-IP # # This is an entry for a user with a space in their name. # Note the double quotes surrounding the name. # #"John Doe" Auth-Type := Local, User-Password == "hello" # Reply-Message = "Hello, %u" # # Dial user back and telnet to the default host for that port # #Deg Auth-Type := Local, User-Password == "ge55ged" # Service-Type = Callback-Login-User, # Login-IP-Host = 0.0.0.0, # Callback-Number = "9,5551212", # Login-Service = Telnet, # Login-TCP-Port = Telnet # # Another complete entry. After the user "dialbk" has logged in, the # connection will be broken and the user will be dialed back after which # he will get a connection to the host "timeshare1". # #dialbk Auth-Type := Local, User-Password == "callme" # Service-Type = Callback-Login-User, # Login-IP-Host = timeshare1, # Login-Service = PortMaster, # Callback-Number = "9,1-800-555-1212" # # user "swilson" will only get a static IP number if he logs in with # a framed protocol on a terminal server in Alphen (see the huntgroups file). # # Note that by setting "Fall-Through", other attributes will be added from # the following DEFAULT entries # #swilson Service-Type == Framed-User, Huntgroup-Name == "alphen" # Framed-IP-Address = 192.168.1.65, # Fall-Through = Yes # # If the user logs in as 'username.shell', then authenticate them # against the system database, give them shell access, and stop processing # the rest of the file. # #DEFAULT Suffix == ".shell", Auth-Type := System # Service-Type = Login-User, # Login-Service = Telnet, # Login-IP-Host = your.shell.machine # # The rest of this file contains the several DEFAULT entries. # DEFAULT entries match with all login names. # Note that DEFAULT entries can also Fall-Through (see first entry). # A name-value pair from a DEFAULT entry will _NEVER_ override # an already existing name-value pair. # # # First setup all accounts to be checked against the UNIX /etc/passwd. # (Unless a password was already given earlier in this file). # DEFAULT Auth-Type = System Fall-Through = 1 # # Set up different IP address pools for the terminal servers. # Note that the "+" behind the IP address means that this is the "base" # IP address. The Port-Id (S0, S1 etc) will be added to it. # #DEFAULT Service-Type == Framed-User, Huntgroup-Name == "alphen" # Framed-IP-Address = 192.168.1.32+, # Fall-Through = Yes #DEFAULT Service-Type == Framed-User, Huntgroup-Name == "delft" # Framed-IP-Address = 192.168.2.32+, # Fall-Through = Yes # # Defaults for all framed connections. # DEFAULT Service-Type == Framed-User Framed-IP-Address = 255.255.255.254, Framed-MTU = 576, Service-Type = Framed-User, Fall-Through = No # # Default for PPP: dynamic IP address, PPP mode, VJ-compression. # NOTE: we do not use Hint = "PPP", since PPP might also be auto-detected # by the terminal server in which case there may not be a "P" suffix. # The terminal server sends "Framed-Protocol = PPP" for auto PPP. # DEFAULT Framed-Protocol == PPP Framed-Protocol = PPP, Framed-Compression = Van-Jacobson-TCP-IP # # Default for CSLIP: dynamic IP address, SLIP mode, VJ-compression. # DEFAULT Hint == "CSLIP" Framed-Protocol = SLIP, Framed-Compression = Van-Jacobson-TCP-IP # # Default for SLIP: dynamic IP address, SLIP mode. # DEFAULT Hint == "SLIP" Framed-Protocol = SLIP # # Last default: rlogin to our main server. # #DEFAULT # Service-Type = Login-User, # Login-Service = Rlogin, # Login-IP-Host = shellbox.ispdomain.com # # # # Last default: shell on the local terminal server. # # # DEFAULT # Service-Type = Shell-User # On no match, the user is denied access.

2 1

multiple sessions with static IP assignment
by Flamur Rogova 23 May '08

23 May '08

Hi, I have the following situation: each user can have 2 simultaneous sessions, but they must have static IPs (consecutive) for both sessions. For example, "users" file entries would look like this: test1 Cleartext-Password :="test1", Simultaneous-Use := 2 Framed-Ip-Address := "192.168.0.1", (other reply attributes...) test1 Cleartext-Password :="test1", Simultaneous-Use := 2 Framed-Ip-Address := "192.168.0.2", (other reply attributes...) Is something like this possible ? thanks, Flamur

2 1

[1.1.0 -> 2.0.4] How to authenticate users like foo@ldap with LDAP server?
by Clark J. Wang 23 May '08

23 May '08

In FreeRADIUS 1.1, I can ask LDAP server to authenticate users with name foo@ldap by configuring like this: --- File: hints --- DEFAULT Suffix == "ldap", Strip-User-Name = Yes Hint = "ldap" --- File: users --- DEFAULT Hint == "ldap", Auth-Type := LDAP -- File: radiusd.conf --- modules { ldap { ... } } authorize { ... # ldap ... } authenticate { ... Auth-Type LDAP { ldap } ... } After upgrading to 2.0.4, when starting `radiusd -X' it failed with error: /usr/local/FreeRADIUS-2.0.4/etc/raddb/users[179]: Parse error (check) for entry DEFAULT: Unknown value LDAP for attribute Auth-Type 2.0.4 does not support this usage any longer?

1 0