June 2009 - Freeradius-Users - lists.freeradius.org

Access Challenge in freeRadius server
by kpani 16 Jun '09

16 Jun '09

Hi, I am new to freeRadius server. I am trying to authorize the ssh and telnet login users of my Redhat Linux machine using freeRadius server. I am able to test Access-Accept and Access-Reject with right and wrong credentials respectively by configuring the file '/etc/pam.d/sshd' with entry pam_radius_auth.so. But I do not know how to achieve and test the Access-Challenge concept. I mean what type of input will result in Access Challenge (I know it happens when we provide partial login information but not sure how to achieve with login in real time)? Please help me with some solutions in achieving Access Challenge. Thanks in advance. Regards, Dhandapani -- View this message in context: http://www.nabble.com/Access-Challenge-in-freeRadius-server-tp24025860p2402… Sent from the FreeRadius - User mailing list archive at Nabble.com.

2 7

Re: SSL3_GET_CLIENT_CERTIFICATE:peer did not return a certificate
by john 15 Jun '09

15 Jun '09

On Sat, Jun 13, 2009 at 7:08 AM, Ivan Kalik<tnt(a)kalik.net> wrote: >> I used the Makefile to generate the certs. I then exported ca.der and >> client.p12 and installed them on the XP box. Did I get the wrong >> files? > > No, those are correct files. Is ca OK but you get errors for client > certificate? Try using included Makefile (rename old Makefile to > Makefile.old and this one to Makefile). It will create client certificates > signed by the ca certificate. > > Ivan Kalik > Kalik Informatika ISP Hi Ivan, The makefile you sent me allowd me to generate a correct client.p12 which cleared up the error reported by windows. Thanks very much. So it looks like windows may prefer personal certs signed by the CA rather than the server? I can sucessfully use the client cert with the "Smart Card or other Certificate" options on Windows XP/SP3 (which uses EAP-TLS I believe). However it didn't fix my issue with trying to use a cert and PEAP or TTLS. So I am stumped still on that one. Any other ideas? Thanks for your help! John

2 3

Problems with Cisco switch and authorization.
by Jeff Davis 15 Jun '09

15 Jun '09

Sorry - I'm a n00b to this project. Trying to get OpenLDAP-based authentication working (well the auth DOES work) but cannot seem to get authorization working. Googling has so far failed me. Perhaps someone on this list can clue me in... users file has the following: DEFAULT Service-Type == NAS-Prompt-User Service-Type := NAS-Prompt-User, Cisco-AVPair += "shell:priv-lvl=15" -- Jefferson K Davis Technology & Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661.392.2110 ext 120

4 7

mod_auth_radius
by Thomas Noppe 15 Jun '09

15 Jun '09

Hi, Has anyone compiled the mod_auth_radius module for apache 2.x on windows? Wheren can I download the binary? Kind regards --------------------------------------------------------------------------------------------- Thomas Noppe Dienst Informatiesystemen - S&O thomas.noppe(a)uzleuven.be<mailto:thomas.noppe@uzleuven.be> +32 16 34 79 87 +32 16 34 78 01 UZ Leuven | campus Gasthuisberg | Herestraat 49 | B - 3000 Leuven | www.uzleuven.be<http://www.uzleuven.be>

1 0

Freeradius and Alvarion
by Jairos Jackson 15 Jun '09

15 Jun '09

Hi, I have a problem with MAC Authentication on an Alvarion Wimax base station. I use freeradius 1.1.7 with Radius Manager 3.6. Currently I am running pppoe authentication with a Mikrotik router at the backend of the Alvarion Wimax and its working fine but I need to change to MAC authentication. I have not done MAC authentication before. Thank you in advance..

4 9

Cleartext password between NAS and Radius Server
by kpani 15 Jun '09

15 Jun '09

Hi, I am using PAP for radius authentication. I have a general question here. When we use PAP for user authentication, the password will be passed from user to NAS(radius client) as cleartext password. But how it is transmitted from NAS to Radius server. 1) As clear text password? or 2) The password is encrypted using the secret keyword(used in both radius client & server) and decrypted using secret key in server. Please correct me. I am seeing different answers in web pages. Regards, Dhandapani -- View this message in context: http://www.nabble.com/Cleartext-password-between-NAS-and-Radius-Server-tp24… Sent from the FreeRadius - User mailing list archive at Nabble.com.

2 1

build error on Solaris (undefined symbol)
by Ihsan Dogan 15 Jun '09

15 Jun '09

Hello, I'm trying to build FreeRADIUS on Solaris (versions 9 and 10) and I'm getting this error: ----------------------------------------------------------------- rm -f .libs/radiusdS.c .libs/radiusd.nm .libs/radiusd.nmS .libs/radiusd.nmT /opt/csw/gcc4/bin/gcc .libs/radiusdS.o -mcpu=v8 -o .libs/radiusd .libs/acct.o .libs/auth.o .libs/client.o .libs/conffile.o .libs/crypt.o .libs/exec.o .libs/files.o .libs/listen.o .libs/log.o .libs/mainconfig.o .libs/modules.o .libs/modcall.o .libs/radiusd.o .libs/stats.o .libs/session.o .libs/threads.o .libs/util.o .libs/valuepair.o .libs/version.o .libs/xlat.o .libs/event.o .libs/realms.o .libs/evaluate.o .libs/vmps.o .libs/detail.o -L/opt/csw/gcc4/lib/. -L/opt/csw/lib /home/ihsan/gar/csw/mgar/pkg/freeradius/trunk/work/build-isa-sparcv8/freeradius-server-2.1.6/src/lib/.libs/libfreeradius-radius.so -lnsl -lresolv -lsocket -lposix4 -lpthread -lcrypt -lltdl -lssl -lcrypto -R/opt/csw/lib Undefined first referenced symbol in file lt__PROGRAM__LTX_preloaded_symbols .libs/modules.o ld: fatal: Symbol referencing errors. No output written to .libs/radiusd gmake[6]: *** [radiusd] Error 1 gmake[6]: Leaving directory `/home/ihsan/gar/csw/mgar/pkg/freeradius/trunk/work/build-isa-sparcv8/freeradius-server-2.1.6/src/main' ----------------------------------------------------------------- Configure runs fine. I've tried to build FreeRADIUS with Sun Studio 12 and GCC 4.3.3 and both show the same error. Ihsan -- ihsan(a)dogan.ch http://blog.dogan.ch/

2 4

Missing Realm when entering second authorization group
by Xiwen Cheng 15 Jun '09

15 Jun '09

Version & OS: Freeradius-2.0.5 Gentoo It appears that during the second iteration in authorize section, the Realm has become NULL. We rely on checking the Realm to choose the appropriate Auth-Type to authenticate local users and proxy everybody else to an external network. ... +- entering group authorize ++[preprocess] returns ok rlm_realm: Looking up realm "math.leidenuniv.nl" for User-Name = "testuser(a)math.leidenuniv.nl" rlm_realm: Found realm "math.leidenuniv.nl" rlm_realm: Adding Stripped-User-Name = "testuser" rlm_realm: Adding Realm = "math.leidenuniv.nl" rlm_realm: Proxying request from user testuser to realm math.leidenuniv.nl rlm_realm: Preparing to proxy authentication request to realm "math.leidenuniv.nl" ++[suffix] returns updated rlm_eap: No EAP-Message, not doing EAP ++[eap] returns noop users: Matched entry DEFAULT at line 292 ++[files] returns ok ... +- entering group pre-proxy ... +- entering group authorize ++[preprocess] returns ok ++[auth_log] returns ok rlm_realm: No '@' in User-Name = "testuser", looking up realm NULL rlm_realm: No such realm "NULL" ++[suffix] returns noop rlm_eap: No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop rlm_pap: WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop auth: No authenticate method (Auth-Type) configuration found for the request: Rejecting the user auth: Failed to validate the user. Found Post-Auth-Type Reject ... NOTE: ... means stripped normal behaviour/output. From the verbose output, the first part is correct. The request is proxied to the correct server. But when it arrives in the authentication server it fails to extract the Realm from the proxied request. In ``users'' we have: DEFAULT Realm == "math.leidenuniv.nl", Auth-Type := PAM Reply-Message = "math here", Fall-Through = no But as the log says, which is correct, there's no Auth-Type for that Realm. If the Realm == "math.leidenuniv.nl" condition is removed, which results in Auth-Type = PAM for everybody, authentication succeeds for local users; which is to be expected. Our config worked perfectly in freeradius-1.1.7. Now I wonder, why is the Realm equal to NULL? I see suffix updated the request, why isn't the second iteration seeing that update? Best regards, Xiwen -- -- Xiwen Cheng System Administrator ;" Enthusiasm is contagious, Mathematical Institute ; but hype is a disease. " Leiden University ;E-mail: xcheng(a)math.leidenuniv.nl Niels Bohrweg 1 K210 ;Office: (+31) 715277134 2333 CA Leiden ;Mobile: (+31) 611119991 The Netherlands ;GPG Key id: 194F572B ++

3 5

Robust proxy accounting
by Chris Howley 15 Jun '09

15 Jun '09

Alan, This is the debug output using the latest release of 2.1.7 from http://git.freeradius.org/pre. Thanks for your help in advance. Chris -----Original Message----- From: Chris Howley [mailto:ecl6ch@netserv3.leeds.ac.uk] Sent: 15 June 2009 12:07 To: Chris Howley Subject: radius.debug4 ending Access-Accept of id 138 to 10.12.80.109 port 32769 User-Name = "isschug" MS-MPPE-Recv-Key = 0x7c4e32b6485bed39ef623ae3c45738d54144c1492d00df705cb1902ed60d5578 MS-MPPE-Send-Key = 0x707c6949db85e4ebb023aaa8016fb3027bfaaf613fb82b92568ba62965235648 EAP-Message = 0x030b0004 Message-Authenticator = 0x00000000000000000000000000000000 Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3021," Reply-Message = "Welcome isschug - student" Finished request 9. Going to the next request Waking up in 0.2 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 1.2 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.8 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 1.1 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.8 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.7 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.9 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.7 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 1.0 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 1.0 seconds. rad_recv: Accounting-Request packet from host 10.12.80.109 port 32769, id=146, length=156 User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" +- entering group preacct {...} ++[preprocess] returns ok [acct_unique] Hashing 'NAS-Port = 29,Client-IP-Address = 10.12.80.109,NAS-IP-Address = 10.12.80.109,Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53",User-Name = "isschug"' [acct_unique] Acct-Unique-Session-ID = "04fae10ff02490f4". ++[acct_unique] returns ok [suffix] No '@' in User-Name = "isschug", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop ++[files] returns noop +- entering group accounting {...} [detail] expand: /usr/local/var/log/radius/radacct/%Y-%m-%d/accounting-detail-%H:00 -> /usr/local/var/log/radius/radacct/2009-06-15/accounting-detail-12:00 [detail] /usr/local/var/log/radius/radacct/%Y-%m-%d/accounting-detail-%H:00 expands to /usr/local/var/log/radius/radacct/2009-06-15/accounting-detail-12:00 [detail] expand: %{Packet-Src-IP-Address} - %t -> 10.12.80.109 - Mon Jun 15 12:00:24 2009 ++[detail] returns ok ++? if ("%{Client-IP-Address}" != "129.11.162.17") expand: %{Client-IP-Address} -> 10.12.80.109 ? Evaluating ("%{Client-IP-Address}" != "129.11.162.17") -> TRUE ++? if ("%{Client-IP-Address}" != "129.11.162.17") -> TRUE ++- entering if ("%{Client-IP-Address}" != "129.11.162.17") {...} +++[control] returns ok ++- if ("%{Client-IP-Address}" != "129.11.162.17") returns ok ++[unix] returns ok [radutmp] expand: /usr/local/var/log/radius/radutmp -> /usr/local/var/log/radius/radutmp [radutmp] expand: %{User-Name} -> isschug ++[radutmp] returns ok [attr_filter.accounting_response] expand: %{User-Name} -> isschug attr_filter: Matched entry DEFAULT at line 1 ++[attr_filter.accounting_response] returns updated server home.example.com { } Sending Accounting-Request of id 159 to 129.11.162.17 port 1813 User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" Proxy-State = 0x313436 Proxying request 10 to home server 129.11.162.17 port 1813 Sending Accounting-Request of id 159 to 129.11.162.17 port 1813 User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" Proxy-State = 0x313436 Going to the next request Waking up in 0.3 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.3 seconds. Cleaning up request 0 ID 129 with timestamp +6 Cleaning up request 1 ID 130 with timestamp +6 Cleaning up request 2 ID 131 with timestamp +6 Cleaning up request 3 ID 132 with timestamp +6 Cleaning up request 4 ID 133 with timestamp +6 Waking up in 0.1 seconds. Cleaning up request 5 ID 134 with timestamp +6 Cleaning up request 6 ID 135 with timestamp +6 Waking up in 0.2 seconds. Cleaning up request 7 ID 136 with timestamp +6 Cleaning up request 8 ID 137 with timestamp +7 Waking up in 0.1 seconds. Cleaning up request 9 ID 138 with timestamp +7 Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.7 seconds. rad_recv: Accounting-Request packet from host 10.12.80.109 port 32769, id=146, length=156 Discarding duplicate request from client wism07-1 port 32769 - ID: 146 due to unfinished request 10 Waking up in 0.2 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 1.1 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.8 seconds. rad_recv: Accounting-Request packet from host 10.12.80.109 port 32769, id=146, length=156 Discarding duplicate request from client wism07-1 port 32769 - ID: 146 due to unfinished request 10 Waking up in 0.2 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 1.0 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.6 seconds. rad_recv: Accounting-Request packet from host 10.12.80.109 port 32769, id=146, length=156 Discarding duplicate request from client wism07-1 port 32769 - ID: 146 due to unfinished request 10 Rejecting request 10 due to lack of any response from home server 129.11.162.17 port 1813 Found Post-Proxy-Type server home.example.com { +- entering group Fail {...} [detail.example.com] expand: /usr/local/var/log/radius/radacct/detail.example.com/detail-%Y%m%d:%H -> /usr/local/var/log/radius/radacct/detail.example.com/detail-20090615:12 [detail.example.com] /usr/local/var/log/radius/radacct/detail.example.com/detail-%Y%m%d:%H expands to /usr/local/var/log/radius/radacct/detail.example.com/detail-20090615:12 [detail.example.com] expand: %t -> Mon Jun 15 12:00:24 2009 [detail.example.com] Freeradius-Proxied-To = 129.11.162.17 ++[detail.example.com] returns ok } Sending Accounting-Response of id 146 to 10.12.80.109 port 32769 Finished request 10. Cleaning up request 10 ID 146 with timestamp +16 Going to the next request PROXY: Marking home server 129.11.162.17 port 1813 as zombie (it looks like it is dead). Sending Status-Server of id 121 to 129.11.162.17 port 1813 Message-Authenticator := 0x00000000000000000000000000000000 NAS-Identifier := "Status Check. Are you alive?" Waking up in 0.1 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* detail_recv: Renaming /usr/local/var/log/radius/radacct/detail.example.com/detail-20090615:12 -> /usr/local/var/log/radius/radacct/detail.example.com/detail.work detail_recv: Read packet from /usr/local/var/log/radius/radacct/detail.example.com/detail.work User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" Acct-Unique-Session-Id = "04fae10ff02490f4" Realm = "acct_realm.example.com" FreeRADIUS-Proxied-To = 129.11.162.17 Packet-Original-Timestamp = "Jun 15 2009 12:00:24 BST" Acct-Delay-Time = 6 server home.example.com { +- entering group accounting {...} ++[control] returns noop } # server home.example.com server home.example.com { } Sending Accounting-Request of id 21 to 129.11.162.17 port 1813 User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" FreeRADIUS-Proxied-To = 129.11.162.17 Acct-Delay-Time = 6 Proxy-State = 0x3333303539 Proxying request 12 to home server 129.11.162.17 port 1813 Sending Accounting-Request of id 21 to 129.11.162.17 port 1813 User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" FreeRADIUS-Proxied-To = 129.11.162.17 Acct-Delay-Time = 6 Proxy-State = 0x3333303539 Going to the next request Waking up in 0.8 seconds. Waking up in 0.1 seconds. Waking up in 0.5 seconds. Waking up in 1.1 seconds. Waking up in 0.9 seconds. Waking up in 0.1 seconds. Waking up in 1.0 seconds. Waking up in 1.1 seconds. Rejecting request 12 due to lack of any response from home server 129.11.162.17 port 1813 Found Post-Proxy-Type server home.example.com { +- entering group Fail {...} [detail.example.com] Suppressing writes to detail file as the request was just read from a detail file. ++[detail.example.com] returns noop } server home.example.com { } # server home.example.com No response configured for request 12. Will retry in 30 seconds Finished request 12. Cleaning up request 12 ID 33059 with timestamp +22 Going to the next request Waking up in 24.4 seconds. Sending Status-Server of id 6 to 129.11.162.17 port 1813 Message-Authenticator := 0x00000000000000000000000000000000 NAS-Identifier := "Status Check. Are you alive?" Waking up in 3.9 seconds. Waking up in 1.5 seconds. detail_recv: Read packet from /usr/local/var/log/radius/radacct/detail.example.com/detail.work User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" Acct-Unique-Session-Id = "04fae10ff02490f4" Realm = "acct_realm.example.com" FreeRADIUS-Proxied-To = 129.11.162.17 Packet-Original-Timestamp = "Jun 15 2009 12:00:24 BST" Acct-Delay-Time = 42 server home.example.com { +- entering group accounting {...} ++[control] returns noop } # server home.example.com server home.example.com { } Sending Accounting-Request of id 57 to 129.11.162.17 port 1813 User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" FreeRADIUS-Proxied-To = 129.11.162.17 Acct-Delay-Time = 42 Proxy-State = 0x3437323335 Proxying request 14 to home server 129.11.162.17 port 1813 Sending Accounting-Request of id 57 to 129.11.162.17 port 1813 User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" FreeRADIUS-Proxied-To = 129.11.162.17 Acct-Delay-Time = 42 Proxy-State = 0x3437323335 Going to the next request Waking up in 0.9 seconds. Waking up in 0.1 seconds. Waking up in 0.9 seconds. Waking up in 1.1 seconds. Waking up in 1.2 seconds. Waking up in 0.8 seconds. Waking up in 0.6 seconds. Rejecting request 14 due to lack of any response from home server 129.11.162.17 port 1813 PROXY: Marking home server 129.11.162.17 port 1813 as dead. Found Post-Proxy-Type server home.example.com { +- entering group Fail {...} [detail.example.com] Suppressing writes to detail file as the request was just read from a detail file. ++[detail.example.com] returns noop } server home.example.com { } # server home.example.com No response configured for request 14. Will retry in 30 seconds Finished request 14. Cleaning up request 14 ID 47235 with timestamp +58 Going to the next request Waking up in 0.2 seconds. Waking up in 22.2 seconds. Sending Status-Server of id 244 to 129.11.162.17 port 1813 Message-Authenticator := 0x00000000000000000000000000000000 NAS-Identifier := "Status Check. Are you alive?" Waking up in 3.9 seconds. Waking up in 3.7 seconds. detail_recv: Read packet from /usr/local/var/log/radius/radacct/detail.example.com/detail.work User-Name = "isschug" NAS-Port = 29 NAS-IP-Address = 10.12.80.109 Framed-IP-Address = 129.11.1.138 NAS-Identifier = "WM07-1" Airespace-Wlan-Id = 1 Acct-Session-Id = "4a3629c8/00:13:02:8d:f3:1f/53" Acct-Authentic = RADIUS Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "3022" Acct-Status-Type = Start Calling-Station-Id = "129.11.1.138" Called-Station-Id = "10.12.80.109" Acct-Unique-Session-Id = "04fae10ff02490f4" Realm = "acct_realm.example.com" FreeRADIUS-Proxied-To = 129.11.162.17 Packet-Original-Timestamp = "Jun 15 2009 12:00:24 BST" Acct-Delay-Time = 78 server home.example.com { +- entering group accounting {...} ++[control] returns noop } # server home.example.com server home.example.com { } >>> Sending proxied request internally to virtual server. server acct_detail.example.com { +- entering group accounting {...} [detail.example.com] Suppressing writes to detail file as the request was just read from a detail file. ++[detail.example.com] returns noop } # server acct_detail.example.com Going to the next request <<< Received proxied response code 0 from internal virtual server. Found Post-Proxy-Type server home.example.com { +- entering group Fail {...} [detail.example.com] Suppressing writes to detail file as the request was just read from a detail file. ++[detail.example.com] returns noop } server home.example.com { } # server home.example.com Finished request 16. Cleaning up request 16 ID 36027 with timestamp +94 Going to the next request Waking up in 1.0 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Waking up in 0.8 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:*

3 2

FreeRadius User Access Level
by Hakan OZAY 15 Jun '09

15 Jun '09

Hi All; I'm using FreeRadius V1. I want, when request from users to my routers(and of course routers to FreeRadius server), feedback from FreeRadius to router: "This user not connecting this router" or "OK". So, look an user access level... This feature make possible? How, if possible? Sorry my bad english, and thank you very much. Best Redards...

2 1