- Freeradius-Users - lists.freeradius.org

Overriding Auth Type in Post Auth
by Johan Meiring 31 Mar '10

31 Mar '10

Hi, In another recent email Alan mentioned that you cannot override a reject in Post-Auth >> post-auth { >> > Post-Auth-Type REJECT { >> > # attr_filter.access_reject >> > Auth-Type := Accept >> > } >> > } > > It's too late to over-ride the reject at that point. I want to implement something differently. I want to override an Accept to a Reject in post-auth (using rlm_perl). I got the impression from another email that that is possible. >> >> >> I basically want freeradius to do the PAP/CHAP stuff and AFTER that I >> want to do things like check the users CAP. > > Use post-auth. The way this sounds, is that you can change an Accept into a Reject, but not the other way around in post-auth. Or am I confused? Thanks, -- Johan Meiring Cape PC Services CC Tel: (021) 883-8271 Fax: (021) 886-7782

1 0

Re: Converting attributes from hex to ASCII
by Aaron Paetznick 31 Mar '10

31 Mar '10

Thanks Arran, but I'm already pretty clear on how to update variables in the request. I just don't know how to go about adding the logic to convert hex/octal strings to ASCII values in unlang. This is untested, but my current line of thinking is to modify the queries in sql.conf with something like this: ... IF('%{Some-Trigger-Attribute}'="TRIGGER-VALUE", UNHEX('%{Called-Station-Id}'), '%{Called-Station-Id}'), \ ... A little bit of overhead to every query, but I suspect it will be manageable on our network. Alternatively, I suppose I could do something like this (untested): ... if ("%{Some-Trigger-Attribute}" =~ /^TRIGGER-VALUE$/) { update request { Called-Station-Id := '%{sql:SELECT UNHEX(%{Called-Station-Id})}' } } ... This somehow seems less desirable though. --Aaron On 3/30/2010 10:06 PM, Arran Cudbard-Bell wrote: > update request { > Tmp-String-1 := `printf etc...` > } > > Then use variable expansion %{request:Tmp-String-1}. Variables in the > backticks will also be expanded. > > -Arran > > On 3/30/10 4:59 PM, Aaron Paetznick wrote: >> I'm receiving User-Name and various Cisco-AVPair attributes as hex. >> >> The situation is complicated. We have a Calix NAS doing something >> called DHCP-triggered RADIUS accounting through a Cisco ASR. This >> means neither vendor wants to accept responsibility, and here we are. >> >> I just thought it would be nice if FreeRADIUS supported a perl-like >> regex system for manipulating strings. I think I'll have to try to fix >> this by jiggering the SQL. >> >> I just wanted to see if anybody else has dealt with something like this. >> >> >> --Aaron >> >> >> Alan DeKok wrote: >>> Aaron Paetznick wrote: >>>> I am receiving certain accounting attributes as hex encoded strings, >>> >>> Why? Which attributes are they? >>> >>>> and >>>> I would like to convert them back to cleartext ASCII before sending >>>> them >>>> to MySQL. >>>> >>>> I can't simply update the SQL with UNHEX() functions, as not all of the >>>> requests are hex encoded this way. >>> >>> It sounds like the NAS is broken. Not that I'm surprised... >>> >>>> If I could use perl, I would do something like this: >>> >>> Why not use Perl? The server doesn't have generic string handling >>> functions, and I don't see the need to invent yet another language. >>> >>> Alan DeKok. >>> - >>> List info/subscribe/unsubscribe? See >>> http://www.freeradius.org/list/users.html >> - >> List info/subscribe/unsubscribe? See >> http://www.freeradius.org/list/users.html >

1 0

Question: How do I forcibly accept all rest requests??
by Difan Zhao 31 Mar '10

31 Mar '10

Good afternoon guys! I am running version 2.1.6. The server is currently doing 802.1x authentication for network devices. Some devices are PCs and users use their Windows domain user/password to login. The rest are special network equipments and I use "MAC address authentication bypass" to authenticate them. Now I have a dilemma that I need to make all other devices (guest devices from out of my company) to be authenticated as well... Currently if these devices (usually laptop running Windows XP) support 802.1x, they will fail and they will be put in an Auth-failed VLAN. The VLAN itself is fine and they can do whatever they want on this VLAN. However it's just that annoying icon on their laptops. It pops up from time to time to notify users that they failed authentication and even prompted for username and password if configured to do so... So I want to make all rest devices to be authenticated. It will be even better if I can assign them to a specific VLAN. I was reading ./sites-avaliable/default and I found that "forcibly accept the user (Auth-Type := Accept)". Where do I put it? I tried: post-auth { Post-Auth-Type REJECT { # attr_filter.access_reject Auth-Type := Accept } } And obviously it's not working... Any ideas how I should configure it? Thank you! Difan Zhao Network Engineer difan.zhao(a)guest-tek.com www.guest-tek.com Office: 403-509-1010 ext 3048 Cell: 403-689-7514

2 4

acct-session-id
by Marlon Duksa 31 Mar '10

31 Mar '10

Hi - The acct-session-id attribute has the length defined as =>3 in RFC 2059. Is anyone aware of any practical limitations on the length of this attribute? Does FreeRadius support the length of this attribute to be let say 300bytes, and are you aware of any other Radius servers that may have problem with larger lengths? Thanks, Marlon

2 3

Converting attributes from hex to ASCII
by Aaron Paetznick 30 Mar '10

30 Mar '10

I am receiving certain accounting attributes as hex encoded strings, and I would like to convert them back to cleartext ASCII before sending them to MySQL. I can't simply update the SQL with UNHEX() functions, as not all of the requests are hex encoded this way. If I could use perl, I would do something like this: preacct { if ("%{SomeAtribute}" =~ /^MATCHING\:(.+)\:MATCHING$/) { update request { Calling-Station-Id := s/([a-fA-F0-9]{2})/chr(hex(%{1}))/eg } } ... } Maybe I can simply flag these attributes somehow by prefixing them with "FLAG::", and use the MySQL IF() function to "post process" them with the UNHEX() function? Any help would be appreciated. Thanks! --Aaron

2 2

What does the NAS-Port mean?
by CaiMuzhang 30 Mar '10

30 Mar '10

Hello! See the packet info below: rad_recv: Access-Request packet from host 168.2.8.28 port 5001, id=142, length=121 User-Name = "licheng" EAP-Message = 0x0201000c016c696368656e67 Message-Authenticator = 0xb11d9a0d22d86cfb58038fe5832a9f9a NAS-IP-Address = 168.2.8.28 NAS-Identifier = "000fe281c738" NAS-Port = 268517377 NAS-Port-Type = Ethernet Service-Type = Framed-User Framed-Protocol = PPP Calling-Station-Id = "0006-5b28-47aa" Notice the NAS-Port = 268517377. It should represent the ID of the port, from which the packet is sent. But when I look up the MIB info of the switch, I can't find such an ID of the port. Instead, the base port number is another integer. How can I get this number (say 268517377) by SNMP? Thank you! _________________________________________________________________ SkyDrive电子画册，带你领略精彩照片，分享“美”时“美”刻! http://www.windowslive.cn/campaigns/e-magazine/ngmchina/?a=c

2 1

freeradius-users@lists.freeradius.org
by Sergio Belkin 30 Mar '10

30 Mar '10

Hi, I am using FR 2.1.1, for host x86_64, with LDAP 802.1x/WPA + OpenLDAP for wireless network access. I've found that some clients using EAP-PEAP using mainly Windows Vista sends notebook credentials despite that is disabled automatically use of credentials... There are a few log entries like as as follows Auth: Login incorrect (rlm_ldap: User not found): [QSARGENTINA\\amumenthaler] (from client UP-PVIII-VIII-Bis port 0 via TLS tunnel) Please could you help me to find a fix? Thanks in advance! -- -- Open Kairos http://www.sergiobelkin.com Watch More TV http://sebelk.blogspot.com Sergio Belkin -

2 1

EAP issue
by David Peterson 30 Mar '10

30 Mar '10

I cannot figure out where this new server is going awry. From what I can tell EAP is misconfigured but I cannot find the issue. If anyone sees anything in the debug please let me know. FreeRADIUS Version 2.1.8, for host i386-portbld-freebsd7.2, built on Mar 26 2010 at 15:24:36 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 /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 files in directory /usr/local/etc/raddb/modules/ including configuration file /usr/local/etc/raddb/modules/wimax including configuration file /usr/local/etc/raddb/modules/always including configuration file /usr/local/etc/raddb/modules/attr_filter including configuration file /usr/local/etc/raddb/modules/attr_rewrite including configuration file /usr/local/etc/raddb/modules/chap including configuration file /usr/local/etc/raddb/modules/checkval including configuration file /usr/local/etc/raddb/modules/counter including configuration file /usr/local/etc/raddb/modules/detail including configuration file /usr/local/etc/raddb/modules/detail.example.com including configuration file /usr/local/etc/raddb/modules/detail.log including configuration file /usr/local/etc/raddb/modules/digest including configuration file /usr/local/etc/raddb/modules/echo including configuration file /usr/local/etc/raddb/modules/etc_group including configuration file /usr/local/etc/raddb/modules/exec including configuration file /usr/local/etc/raddb/modules/expiration including configuration file /usr/local/etc/raddb/modules/expr including configuration file /usr/local/etc/raddb/modules/files including configuration file /usr/local/etc/raddb/modules/inner-eap including configuration file /usr/local/etc/raddb/modules/ippool including configuration file /usr/local/etc/raddb/modules/krb5 including configuration file /usr/local/etc/raddb/modules/ldap including configuration file /usr/local/etc/raddb/modules/linelog including configuration file /usr/local/etc/raddb/modules/logintime including configuration file /usr/local/etc/raddb/modules/mac2ip including configuration file /usr/local/etc/raddb/modules/mac2vlan including configuration file /usr/local/etc/raddb/modules/mschap including configuration file /usr/local/etc/raddb/modules/otp including configuration file /usr/local/etc/raddb/modules/pam including configuration file /usr/local/etc/raddb/modules/pap including configuration file /usr/local/etc/raddb/modules/passwd including configuration file /usr/local/etc/raddb/modules/perl including configuration file /usr/local/etc/raddb/modules/policy including configuration file /usr/local/etc/raddb/modules/preprocess including configuration file /usr/local/etc/raddb/modules/radutmp including configuration file /usr/local/etc/raddb/modules/realm including configuration file /usr/local/etc/raddb/modules/smbpasswd including configuration file /usr/local/etc/raddb/modules/smsotp including configuration file /usr/local/etc/raddb/modules/sql_log including configuration file /usr/local/etc/raddb/modules/sqlcounter_expire_on_login including configuration file /usr/local/etc/raddb/modules/sradutmp including configuration file /usr/local/etc/raddb/modules/unix including configuration file /usr/local/etc/raddb/modules/acct_unique including configuration file /usr/local/etc/raddb/eap.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 configuration file /usr/local/etc/raddb/sites-enabled/control-socket main { user = "freeradius" group = "freeradius" allow_core_dumps = no } including dictionary file /usr/local/etc/raddb/dictionary main { prefix = "/usr/local" localstatedir = "/var" logdir = "/var/log" libdir = "/usr/local/lib/freeradius-2.1.8" radacctdir = "/var/log/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/var/run/radiusd/radiusd.pid" checkrad = "/usr/local/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = no auth_badpass = no auth_goodpass = no } security { max_attributes = 200 reject_delay = 1 status_server = yes } } 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 radius01 { ipaddr = 1.2.3.4 port = 1812 type = "auth" secret = "secret1" response_window = 20 max_outstanding = 65536 require_message_authenticator = no zombie_period = 40 status_check = "status-server" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 irt = 2 mrt = 16 mrc = 5 mrd = 30 } home_server_pool my_auth_failover { type = fail-over home_server = radius01 } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } client 3.4.5.6 { require_message_authenticator = no secret = "secret2" shortname = "Alvarion" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating exec exec { wait = no 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 = "/var/log/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 max_sessions = 2048 } 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" } Module: Linked to sub-module rlm_eap_tls Module: Instantiating eap-tls tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 pem_file_type = yes private_key_file = "/usr/local/etc/raddb/certs/server.pem" certificate_file = "/usr/local/etc/raddb/certs/server.pem" CA_file = "/usr/local/etc/raddb/certs/ca.pem" private_key_password = "whatever" dh_file = "/usr/local/etc/raddb/certs/dh" random_file = "/usr/local/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/usr/local/etc/raddb/certs/bootstrap" cache { enable = no lifetime = 24 max_entries = 255 } } Module: Linked to sub-module rlm_eap_ttls Module: Instantiating eap-ttls ttls { default_eap_type = "md5" copy_request_to_tunnel = yes use_tunneled_reply = yes virtual_server = "inner-tunnel" include_length = yes } Module: Linked to sub-module rlm_eap_peap Module: Instantiating eap-peap peap { default_eap_type = "mschapv2" copy_request_to_tunnel = no use_tunneled_reply = no proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" } 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 = "/var/log/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}" } } # modules } # server 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: Linked to module rlm_wimax Module: Instantiating wimax wimax { delete_mppe_keys = 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 = "/var/log/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 } # modules } # server radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } listen { type = "control" listen { socket = "/var/run/radiusd/radiusd.sock" } } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /var/run/radiusd/radiusd.sock Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 3.4.5.6 port 49157, id=33, length=260 User-Name = "{am=1}d9331e46a19a9d6ffac45999467fd418(a)example.com" NAS-IP-Address = 172.16.4.6 NAS-Port-Type = 27 NAS-Port = 1 Calling-Station-Id = "\000\020\347AK\024" NAS-Identifier = "001001001000131001" WiMAX-GMT-Timezone-offset = 0 Framed-MTU = 1490 Service-Type = Framed-User WiMAX-Release = "1.0" WiMAX-Accounting-Capabilities = IP-Session-Based WiMAX-BS-Id = 0x303031303031303031303030313331303031 EAP-Message = 0x02010036017b616d3d317d6439333331653436613139613964366666616334353939393436 37666434313840736361726c65742e616e Message-Authenticator = 0x90a2f3c8f27af034fb51225e1753c977 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop rlm_wimax: Fixing WiMAX binary Calling-Station-Id to 00-10-e7-41-4b-14 ++[wimax] returns ok [suffix] Looking up realm "example.com" for User-Name = "{am=1}d9331e46a19a9d6ffac45999467fd418(a)example.com" [suffix] Found realm "example.com" [suffix] Adding Stripped-User-Name = "{am=1}d9331e46a19a9d6ffac45999467fd418" [suffix] Adding Realm = "example.com" [suffix] Proxying request from user {am=1}d9331e46a19a9d6ffac45999467fd418 to realm example.com [suffix] Preparing to proxy authentication request to realm "example.com" ++[suffix] returns updated [eap] Request is supposed to be proxied to Realm example.com. Not doing EAP. ++[eap] returns noop ++[unix] returns notfound [files] users: Matched entry DEFAULT at line 203 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop WARNING: Empty section. Using default return values. Sending Access-Request of id 200 to 1.2.3.4 port 1812 User-Name = "{am=1}d9331e46a19a9d6ffac45999467fd418" NAS-IP-Address = 172.16.4.6 NAS-Port-Type = 27 NAS-Port = 1 Calling-Station-Id = "00-10-e7-41-4b-14" NAS-Identifier = "001001001000131001" WiMAX-GMT-Timezone-offset = 0 Framed-MTU = 1490 Service-Type = Framed-User WiMAX-Release = "1.0" WiMAX-Accounting-Capabilities = IP-Session-Based WiMAX-BS-Id = 0x303031303031303031303030313331303031 EAP-Message = 0x02010036017b616d3d317d6439333331653436613139613964366666616334353939393436 37666434313840736361726c65742e616e Message-Authenticator = 0x00000000000000000000000000000000 Proxy-State = 0x3333 Proxying request 47 to home server 1.2.3.4 port 1812 Sending Access-Request of id 200 to 1.2.3.4 port 1812 User-Name = "{am=1}d9331e46a19a9d6ffac45999467fd418" NAS-IP-Address = 172.16.4.6 NAS-Port-Type = 27 NAS-Port = 1 Calling-Station-Id = "00-10-e7-41-4b-14" NAS-Identifier = "001001001000131001" WiMAX-GMT-Timezone-offset = 0 Framed-MTU = 1490 Service-Type = Framed-User WiMAX-Release = "1.0" WiMAX-Capability = 0x0105312e30020301 WiMAX-Accounting-Capabilities = IP-Session-Based WiMAX-BS-Id = 0x303031303031303031303030313331303031 EAP-Message = 0x02010036017b616d3d317d6439333331653436613139613964366666616334353939393436 37666434313840736361726c65742e616e Message-Authenticator = 0x00000000000000000000000000000000 Proxy-State = 0x3333 Going to the next request Waking up in 0.9 seconds. rad_recv: Access-Reject packet from host 1.2.3.4 port 1812, id=200, length=24 Proxy-State = 0x3333 +- entering group post-proxy {...} [eap] No pre-existing handler found ++[eap] returns noop Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> {am=1}d9331e46a19a9d6ffac45999467fd418(a)example.com attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 47 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 47 Sending Access-Reject of id 33 to 3.4.5.6 port 49157 Waking up in 4.9 seconds. Cleaning up request 47 ID 33 with timestamp +2476 Ready to process requests. David Peterson Engineer Wireless Connections 166 Milan Ave., Norwalk, Oh. 44857 ACCessing the Future Today!! ofc. 419.660.6100 ext 2287 cell 419-706-7355 fax 419-668-4077 <http://www.wirelessconnections.net/> http://www.wirelessconnections.net This transmission and any files attached to it, may contain confidential and/or privileged information and intended only for the named recipient. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, retransmission, dissemination, disclosure, copying or any use of the information or files contained is strictly prohibited. If you have received this transmission in error, please notify the sender by reply transmission and delete this electronic mail

2 1

Wimax module with Freeradius 2.1.8 on Ubuntu
by Lindsay, Joel 30 Mar '10

30 Mar '10

Hi, I am using ubuntu and wanted to install freeradius. After installing the default unbuntu version of freeradius, I realised that it does not support WiMAX. I then removed the old version, downloaded the latest version of freeradius (2.1.8) and built my own package according to the build instructions on the freeradius Wiki. This did not appear to build the wimax portions as freeradius crashed stating it could not find the shared rlm_wimax.so file (when I ran the server with wimax eneabled in the defaults file. I built this file myself and linked it into the directory where all the other freeradius libraries go. This allowed me to start freeradius, but on the first authentication request, I get a segmentation fault. I attempted to recompile from source using ./configure -with-experimental-modules and make. Unfortunately this too failed to compile the WiMAX module. Does anyone know what I am doing wrong here? Thanks for the help! __________________________________________________________ Joel Lindsay

3 2

Help: Radius Accounting Request and Message Authenticator
by Alessio Grasso 30 Mar '10

30 Mar '10

Hi all, I'm a ICLoS's software engineering and I'm developing a WiMax ASN. I had already develop the client authentication and authorization modules for freeradius 2.1.8, successfully (EAP-TTLS). Now I'm building the Radius Accounting module but I have a problem with the Request-Authenticator find in the message of Accounting-Request. When I send a Radius Accounting-Request, the server's log shows: Received packet from 192.168.2.130 with invalid Message-Authenticator! (Shared secret is incorrect.) Dropping packet without response. I think it's wrong to calculate HMAC-MD5 (is it exactly the same to the case of Authentication Request?). I'm studing on the RFC 2866 but I found that there are only 16 octets to zero in the Authenticator field. Where can I found further informations? Thanks in advance, Alessio Grasso

2 1