- Freeradius-Users - lists.freeradius.org

Whitelisting LAN
by Randeep 16 Sep '15

16 Sep '15

Hi all, We are using FreeRadius for Hotspot and PPPoE authentication in out network. But the authentication is required only when the user connects to internet. We have iptv services available in our network. This shouldnt be affected when restricting the bandwidth and applying the FUP. The problem is when the FUP is applied even the iptv services in LAN gets affected. How can we whitelist the LAN ips so that local services will not get affected by applying radius policies? Regards, Randeep

1 0

proxy/home-server, could be set dynamically?
by Jorge Pereira 15 Sep '15

15 Sep '15

Hi, The "home-server", could be set dynamically? because today I have used the below approach. # 1) list of tens and tens of homeservers that is used the ident based on NAS-Identifier home_server coa_SAME_NAS_IDENTIFIER1 { type = coa secret = hello ipaddr = 1.2.3.4 port = 3799 proto = udp revive_interval = 10 status_check = none check_interval = 10 num_answers_to_alive = 3 } home_server_pool coa_pool_SAME_NAS_IDENTIFIER1 { type = fail-over home_server = coa_SAME_NAS_IDENTIFIER1 } ..... same thing to another servers. # 2) in the recv-coa, I have recv-coa { ...... update control { &Home-Server-Pool := "coa_pool_%{NAS-Identifier}" } ...... } --------- Conclusion: I would like to know if have some way to set a values of Home-Server dynamically. -- Jorge Pereira

2 1

3.0.x: user-password length decoding sometimes wrong?
by Stefan Winter 15 Sep '15

15 Sep '15

Hi, ugh. I just updated to 3.0.x from a few minutes ago to be prepared for the MS-CHAP key problem and iOS 9. That seems to work - good. But I have a problem with good old PAP but only for requests originating from one of the clients - and consistently. That client is insanely old and has ancient library versions. So it may well be doing something subtly wrong in the requests it sends; but still, this worked for a FreeRADIUS server versions since a decade. But not in current 3.0.x. What I see coming in (decoded in -X) is: (137) Received Access-Request Id 89 from 158.64.1.50:8010 to 158.64.2.220:1812 length 80 [...] (137) User-Password = "12345678\000\000\000\000\021" That's an 8 char password (12345678 is the equivalent of correct; i.e. redacted in this mail but it otherwise fits). On other clients, the same password comes in as User-Password = "12345678" as expected; a tcpdump between for both clients reveals that the on-the-wire length of User-Password is the same (16 chars net, to account for padding). Current 3.0.x then does SSHA password comparison between what it got and the contents in our DB, and finds that the SSHA hash of the above first string does not match our stored password hash, while the second one does. So it's a Accept/Reject difference and our users are not happy. Now since padded-and-encrypted parsing differences are the exact problem that was fixed for 3.0.9, I suspect that fixing that had a side-effect on PAP password length extraction. It looks like the old client uses \0-then-something-random as padding (I also saw requests with jsut one \0 and then more garbage) while newer clients pad with \0\0\0\0 until the attribute ends. And that the latter works, while the former doesn't :-) I realise that all \0 is what RFC2865 chapter 5.2 mandates as padding text. So, yes, our client is at fault. Still, is there any chance that the server-side parsing could be made a little more forgiving? Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 PGP key updated to 4096 Bit RSA - I will encrypt all mails if the recipient's key is known to me http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66

3 2

EAP session problem
by Stefano Pardini 15 Sep '15

15 Sep '15

Hi guys, I'm using PEAP/MSCHAPV2 and OpenLDAP password backend (and Samba3) to provide wpa2-enterprise authentication to wifi users inside an high school (with OpenWRT access point). Everything has been working very well for one year. Wonderful! Three days ago something very strange has started to happen. Wifi users can't create a TLS tunel (windows, linux, android) to provide the authentication. I didn't touch the configuration files in the last few months. Nothing has changed. The CA certificate is valid. This is my server. ********** root@service:/etc/freeradius# uname -a Linux service 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u3 i686 GNU/Linux root@service:/etc/freeradius# freeradius -v freeradius: FreeRADIUS Version 2.1.12, for host i486-pc-linux-gnu, built on Dec 16 2012 at 22:03:33 root@service:/etc/freeradius# cat /etc/debian_version 7.8 ********** I get the follow error message. rad_recv: Access-Request packet from host 192.168.11.45 port 38247, id=42, length=189 User-Name = "pippo" Called-Station-Id = "C0-4A-00-38-EB-B9:SchoolWiFi" NAS-Port-Type = Wireless-802.11 NAS-Port = 1 Calling-Station-Id = "64-6C-B2-8F-6B-E2" Connect-Info = "CONNECT 54Mbps 802.11g" Acct-Session-Id = "55EEABD1-00000033" X-Ascend-Home-Agent-UDP-Port = 1027076 X-Ascend-Multilink-ID = 1027076 X-Ascend-Num-In-Multilink = 1027073 Framed-MTU = 1400 EAP-Message = 0x02dc000a01706970706f Message-Authenticator = 0x87734c3becfa0235559ba872af4888c3 # Executing section authorize from file /etc/freeradius/sites-enabled/default +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop ++[digest] returns noop [suffix] No '@' in User-Name = "pippo", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 220 length 10 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[expiration] returns noop ++[logintime] returns noop Found Auth-Type = EAP # Executing group from file /etc/freeradius/sites-enabled/default +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 42 to 192.168.11.45 port 38247 EAP-Message = 0x01dd00061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xa0e49fa1a0398655bdbbb8b91da409d3 Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.11.45 port 38247, id=42, length=189 Sending duplicate reply to client OpenWrt port 38247 - ID: 42 Sending Access-Challenge of id 42 to 192.168.11.45 port 38247 Waking up in 2.0 seconds. Cleaning up request 0 ID 42 with timestamp +4 WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: !! EAP session for state 0xa0e49fa1a0398655 did not finish! WARNING: !! Please read http://wiki.freeradius.org/Certificate_Compatibility WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Ready to process requests. ********** freeradius -X ********** FreeRADIUS Version 2.1.12, for host i486-pc-linux-gnu, built on Dec 16 2012 at 22:03:33 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 /etc/freeradius/radiusd.conf including configuration file /etc/freeradius/proxy.conf including configuration file /etc/freeradius/clients.conf including files in directory /etc/freeradius/modules/ including configuration file /etc/freeradius/modules/mschap including configuration file /etc/freeradius/modules/sradutmp including configuration file /etc/freeradius/modules/acct_unique including configuration file /etc/freeradius/modules/counter including configuration file /etc/freeradius/modules/redis including configuration file /etc/freeradius/modules/ldap including configuration file /etc/freeradius/modules/always including configuration file /etc/freeradius/modules/inner-eap including configuration file /etc/freeradius/modules/digest including configuration file /etc/freeradius/modules/mac2ip including configuration file /etc/freeradius/modules/policy including configuration file /etc/freeradius/modules/files including configuration file /etc/freeradius/modules/passwd including configuration file /etc/freeradius/modules/dynamic_clients including configuration file /etc/freeradius/modules/smsotp including configuration file /etc/freeradius/modules/replicate including configuration file /etc/freeradius/modules/preprocess including configuration file /etc/freeradius/modules/expiration including configuration file /etc/freeradius/modules/krb5 including configuration file /etc/freeradius/modules/unix including configuration file /etc/freeradius/modules/echo including configuration file /etc/freeradius/modules/detail including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login including configuration file /etc/freeradius/modules/detail.example.com including configuration file /etc/freeradius/modules/sql_log including configuration file /etc/freeradius/modules/linelog including configuration file /etc/freeradius/modules/exec including configuration file /etc/freeradius/modules/checkval including configuration file /etc/freeradius/modules/chap including configuration file /etc/freeradius/modules/radutmp including configuration file /etc/freeradius/modules/logintime including configuration file /etc/freeradius/modules/perl including configuration file /etc/freeradius/modules/otp including configuration file /etc/freeradius/modules/attr_filter including configuration file /etc/freeradius/modules/smbpasswd including configuration file /etc/freeradius/modules/cui including configuration file /etc/freeradius/modules/ippool including configuration file /etc/freeradius/modules/pam including configuration file /etc/freeradius/modules/wimax including configuration file /etc/freeradius/modules/rediswho including configuration file /etc/freeradius/modules/pap including configuration file /etc/freeradius/modules/realm including configuration file /etc/freeradius/modules/detail.log including configuration file /etc/freeradius/modules/ntlm_auth including configuration file /etc/freeradius/modules/soh including configuration file /etc/freeradius/modules/mac2vlan including configuration file /etc/freeradius/modules/attr_rewrite including configuration file /etc/freeradius/modules/etc_group including configuration file /etc/freeradius/modules/opendirectory including configuration file /etc/freeradius/modules/expr including configuration file /etc/freeradius/eap.conf including configuration file /etc/freeradius/sql.conf including configuration file /etc/freeradius/sql/mysql/dialup.conf including configuration file /etc/freeradius/policy.conf including files in directory /etc/freeradius/sites-enabled/ including configuration file /etc/freeradius/sites-enabled/inner-tunnel including configuration file /etc/freeradius/sites-enabled/control-socket including configuration file /etc/freeradius/sites-enabled/default main { user = "freerad" group = "freerad" allow_core_dumps = no } including dictionary file /etc/freeradius/dictionary main { name = "freeradius" prefix = "/usr" localstatedir = "/var" sbindir = "/usr/sbin" logdir = "/var/log/freeradius" run_dir = "/var/run/freeradius" libdir = "/usr/lib/freeradius" radacctdir = "/var/log/freeradius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 76800 pidfile = "/var/run/freeradius/freeradius.pid" checkrad = "/usr/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 localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 require_message_authenticator = yes 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 coa { irt = 2 mrt = 16 mrc = 5 mrd = 30 } } home_server_pool my_auth_failover { type = fail-over home_server = localhost } 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 127.0.0.0/24 { require_message_authenticator = no secret = "radius014server" shortname = "OpenWrt" } client 192.168.11.0/24 { require_message_authenticator = no secret = "radius014server" shortname = "OpenWrt" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating module "exec" from file /etc/freeradius/modules/exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating module "expr" from file /etc/freeradius/modules/expr Module: Linked to module rlm_expiration Module: Instantiating module "expiration" from file /etc/freeradius/modules/expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating module "logintime" from file /etc/freeradius/modules/logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server { # from file /etc/freeradius/radiusd.conf modules { Module: Creating Auth-Type = digest Module: Creating Post-Auth-Type = REJECT Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating module "pap" from file /etc/freeradius/modules/pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating module "chap" from file /etc/freeradius/modules/chap Module: Linked to module rlm_mschap Module: Instantiating module "mschap" from file /etc/freeradius/modules/mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no allow_retry = yes } Module: Linked to module rlm_digest Module: Instantiating module "digest" from file /etc/freeradius/modules/digest Module: Linked to module rlm_unix Module: Instantiating module "unix" from file /etc/freeradius/modules/unix unix { radwtmp = "/var/log/freeradius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating module "eap" from file /etc/freeradius/eap.conf eap { default_eap_type = "peap" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no max_sessions = 4096 } 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 CA_path = "/etc/ssl/ca" pem_file_type = yes private_key_file = "/etc/ssl/radius.server.schoolnetwork.it.key" certificate_file = "/etc/ssl/radius.server.schoolnetwork.it.crt" CA_file = "/etc/certs/ca.crt" private_key_password = "my_key_password" dh_file = "/etc/ssl/radius.dh" random_file = "/dev/urandom" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" ecdh_curve = "prime256v1" cache { enable = no lifetime = 24 max_entries = 255 } verify { } ocsp { enable = no override_cert_url = yes url = "http://127.0.0.1/ocsp/" } } Module: Linked to sub-module rlm_eap_ttls Module: Instantiating eap-ttls ttls { default_eap_type = "md5" copy_request_to_tunnel = no use_tunneled_reply = no 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 = yes proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" soh = no } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no send_error = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating module "preprocess" from file /etc/freeradius/modules/preprocess preprocess { huntgroups = "/etc/freeradius/huntgroups" hints = "/etc/freeradius/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_realm Module: Instantiating module "suffix" from file /etc/freeradius/modules/realm realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating module "acct_unique" from file /etc/freeradius/modules/acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Linked to module rlm_files Module: Instantiating module "files" from file /etc/freeradius/modules/files files { usersfile = "/etc/freeradius/users" acctusersfile = "/etc/freeradius/acct_users" preproxy_usersfile = "/etc/freeradius/preproxy_users" compat = "no" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating module "detail" from file /etc/freeradius/modules/detail detail { detailfile = "/var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Linked to module rlm_radutmp Module: Instantiating module "radutmp" from file /etc/freeradius/modules/radutmp radutmp { filename = "/var/log/freeradius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Linked to module rlm_attr_filter Module: Instantiating module "attr_filter.accounting_response" from file /etc/freeradius/modules/attr_filter attr_filter attr_filter.accounting_response { attrsfile = "/etc/freeradius/attrs.accounting_response" key = "%{User-Name}" relaxed = no } 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 Module: Instantiating module "attr_filter.access_reject" from file /etc/freeradius/modules/attr_filter attr_filter attr_filter.access_reject { attrsfile = "/etc/freeradius/attrs.access_reject" key = "%{User-Name}" relaxed = no } } # modules } # server server inner-tunnel { # from file /etc/freeradius/sites-enabled/inner-tunnel modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_ldap Module: Instantiating module "ldap" from file /etc/freeradius/modules/ldap ldap { server = "ldapslave.server.schoolnetwork.it" port = 389 password = "mypass" identity = "cn=admin,dc=schoolnetwork,dc=it" net_timeout = 1 timeout = 4 timelimit = 3 tls_mode = no start_tls = no tls_require_cert = "allow" tls { start_tls = no require_cert = "allow" } basedn = "ou=Users,dc=schoolnwetwork,dc=it" filter = "(uid=%{%{Stripped-User-Name}:-%{User-Name}})" base_filter = "(objectclass=radiusprofile)" auto_header = no access_attr_used_for_allow = yes groupname_attribute = "cn" groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))" dictionary_mapping = "/etc/freeradius/ldap.attrmap" ldap_debug = 0 ldap_connections_number = 5 compare_check_items = no do_xlat = yes edir_account_policy_check = no set_auth_type = yes keepalive { idle = 60 probes = 3 interval = 3 } } rlm_ldap: Registering ldap_groupcmp for Ldap-Group rlm_ldap: Registering ldap_xlat with xlat_name ldap rlm_ldap: Over-riding set_auth_type, as there is no module ldap listed in the "authenticate" section. rlm_ldap: reading ldap<->radius mappings from file /etc/freeradius/ldap.attrmap rlm_ldap: LDAP radiusCheckItem mapped to RADIUS $GENERIC$ rlm_ldap: LDAP radiusReplyItem mapped to RADIUS $GENERIC$ rlm_ldap: LDAP radiusAuthType mapped to RADIUS Auth-Type rlm_ldap: LDAP radiusSimultaneousUse mapped to RADIUS Simultaneous-Use rlm_ldap: LDAP radiusCalledStationId mapped to RADIUS Called-Station-Id rlm_ldap: LDAP radiusCallingStationId mapped to RADIUS Calling-Station-Id rlm_ldap: LDAP lmPassword mapped to RADIUS LM-Password rlm_ldap: LDAP ntPassword mapped to RADIUS NT-Password rlm_ldap: LDAP sambaLmPassword mapped to RADIUS LM-Password rlm_ldap: LDAP sambaNtPassword mapped to RADIUS NT-Password rlm_ldap: LDAP dBCSPwd mapped to RADIUS LM-Password rlm_ldap: LDAP userPassword mapped to RADIUS Password-With-Header rlm_ldap: LDAP acctFlags mapped to RADIUS SMB-Account-CTRL-TEXT rlm_ldap: LDAP radiusExpiration mapped to RADIUS Expiration rlm_ldap: LDAP radiusNASIpAddress mapped to RADIUS NAS-IP-Address rlm_ldap: LDAP radiusServiceType mapped to RADIUS Service-Type rlm_ldap: LDAP radiusFramedProtocol mapped to RADIUS Framed-Protocol rlm_ldap: LDAP radiusFramedIPAddress mapped to RADIUS Framed-IP-Address rlm_ldap: LDAP radiusFramedIPNetmask mapped to RADIUS Framed-IP-Netmask rlm_ldap: LDAP radiusFramedRoute mapped to RADIUS Framed-Route rlm_ldap: LDAP radiusFramedRouting mapped to RADIUS Framed-Routing rlm_ldap: LDAP radiusFilterId mapped to RADIUS Filter-Id rlm_ldap: LDAP radiusFramedMTU mapped to RADIUS Framed-MTU rlm_ldap: LDAP radiusFramedCompression mapped to RADIUS Framed-Compression rlm_ldap: LDAP radiusLoginIPHost mapped to RADIUS Login-IP-Host rlm_ldap: LDAP radiusLoginService mapped to RADIUS Login-Service rlm_ldap: LDAP radiusLoginTCPPort mapped to RADIUS Login-TCP-Port rlm_ldap: LDAP radiusCallbackNumber mapped to RADIUS Callback-Number rlm_ldap: LDAP radiusCallbackId mapped to RADIUS Callback-Id rlm_ldap: LDAP radiusFramedIPXNetwork mapped to RADIUS Framed-IPX-Network rlm_ldap: LDAP radiusClass mapped to RADIUS Class rlm_ldap: LDAP radiusSessionTimeout mapped to RADIUS Session-Timeout rlm_ldap: LDAP radiusIdleTimeout mapped to RADIUS Idle-Timeout rlm_ldap: LDAP radiusTerminationAction mapped to RADIUS Termination-Action rlm_ldap: LDAP radiusLoginLATService mapped to RADIUS Login-LAT-Service rlm_ldap: LDAP radiusLoginLATNode mapped to RADIUS Login-LAT-Node rlm_ldap: LDAP radiusLoginLATGroup mapped to RADIUS Login-LAT-Group rlm_ldap: LDAP radiusFramedAppleTalkLink mapped to RADIUS Framed-AppleTalk-Link rlm_ldap: LDAP radiusFramedAppleTalkNetwork mapped to RADIUS Framed-AppleTalk-Network rlm_ldap: LDAP radiusFramedAppleTalkZone mapped to RADIUS Framed-AppleTalk-Zone rlm_ldap: LDAP radiusPortLimit mapped to RADIUS Port-Limit rlm_ldap: LDAP radiusLoginLATPort mapped to RADIUS Login-LAT-Port rlm_ldap: LDAP radiusReplyMessage mapped to RADIUS Reply-Message rlm_ldap: LDAP radiusTunnelType mapped to RADIUS Tunnel-Type rlm_ldap: LDAP radiusTunnelMediumType mapped to RADIUS Tunnel-Medium-Type rlm_ldap: LDAP radiusTunnelPrivateGroupId mapped to RADIUS Tunnel-Private-Group-Id conns: 0x930e4e0 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/freeradius/freeradius.sock" uid = "freerad" gid = "freerad" mode = "rw" } } listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 } ... adding new socket proxy address * port 51649 Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /var/run/freeradius/freeradius.sock Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Ready to process requests. *** a new request is coming... rad_recv: Access-Request packet from host 192.168.11.45 port 38247, id=42, length=189 User-Name = "pippo" Called-Station-Id = "C0-4A-00-38-EB-B9:SchoolWiFi" NAS-Port-Type = Wireless-802.11 NAS-Port = 1 Calling-Station-Id = "64-6C-B2-8F-6B-E2" Connect-Info = "CONNECT 54Mbps 802.11g" Acct-Session-Id = "55EEABD1-00000033" X-Ascend-Home-Agent-UDP-Port = 1027076 X-Ascend-Multilink-ID = 1027076 X-Ascend-Num-In-Multilink = 1027073 Framed-MTU = 1400 EAP-Message = 0x02dc000a01706970706f Message-Authenticator = 0x87734c3becfa0235559ba872af4888c3 # Executing section authorize from file /etc/freeradius/sites-enabled/default +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop ++[digest] returns noop [suffix] No '@' in User-Name = "pippo", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 220 length 10 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[expiration] returns noop ++[logintime] returns noop Found Auth-Type = EAP # Executing group from file /etc/freeradius/sites-enabled/default +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 42 to 192.168.11.45 port 38247 EAP-Message = 0x01dd00061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xa0e49fa1a0398655bdbbb8b91da409d3 Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.11.45 port 38247, id=42, length=189 Sending duplicate reply to client OpenWrt port 38247 - ID: 42 Sending Access-Challenge of id 42 to 192.168.11.45 port 38247 Waking up in 2.0 seconds. Cleaning up request 0 ID 42 with timestamp +4 WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: !! EAP session for state 0xa0e49fa1a0398655 did not finish! WARNING: !! Please read http://wiki.freeradius.org/Certificate_Compatibility WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Ready to process requests. *** nothing to do... another request is coming... *** rad_recv: Access-Request packet from host 192.168.11.45 port 38247, id=42, length=189 User-Name = "pippo" Called-Station-Id = "C0-4A-00-38-EB-B9:SchoolWiFi" NAS-Port-Type = Wireless-802.11 NAS-Port = 1 Calling-Station-Id = "64-6C-B2-8F-6B-E2" Connect-Info = "CONNECT 54Mbps 802.11g" Acct-Session-Id = "55EEABD1-00000033" X-Ascend-Home-Agent-UDP-Port = 1027076 X-Ascend-Multilink-ID = 1027076 X-Ascend-Num-In-Multilink = 1027073 Framed-MTU = 1400 EAP-Message = 0x02dc000a01706970706f Message-Authenticator = 0x87734c3becfa0235559ba872af4888c3 # Executing section authorize from file /etc/freeradius/sites-enabled/default +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop ++[digest] returns noop [suffix] No '@' in User-Name = "pippo", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 220 length 10 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[expiration] returns noop ++[logintime] returns noop Found Auth-Type = EAP # Executing group from file /etc/freeradius/sites-enabled/default +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 42 to 192.168.11.45 port 38247 EAP-Message = 0x01dd00061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x4b673bbe4bba2270a10d90dd5a1cfcf8 Finished request 1. Going to the next request Waking up in 4.9 seconds. Cleaning up request 1 ID 42 with timestamp +13 WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: !! EAP session for state 0x4b673bbe4bba2270 did not finish! WARNING: !! Please read http://wiki.freeradius.org/Certificate_Compatibility WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Ready to process requests. I make this test radtest -t mschap pippo 741F90F33547C38DD5C79837F0DE1F1F 127.0.0.1:1812 0 testing123 *** this is the server response Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /var/run/freeradius/freeradius.sock Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1 port 52032, id=63, length=136 User-Name = "pippo" NAS-IP-Address = 192.168.10.3 NAS-Port = 0 Message-Authenticator = 0xf3c699b88c2a8e909a986e8fd406a6e6 MS-CHAP-Challenge = 0xb375054eeeacd6af MS-CHAP-Response = 0x00010000000000000000000000000000000000000000000000004f983bbfb5f33661c81185f43bb8a0a35ea3be98b2c93795 server inner-tunnel { # Executing section authorize from file /etc/freeradius/sites-enabled/inner-tunnel +- entering group authorize {...} [suffix] No '@' in User-Name = "pippo", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop ++[control] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop [ldap] performing user authorization for pippo [ldap] expand: %{Stripped-User-Name} -> [ldap] ... expanding second conditional [ldap] expand: %{User-Name} -> pippo [ldap] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=pippo) [ldap] expand: ou=Users,dc=schoolnetwork,dc=it -> ou=Users,dc=schoolnetwork,dc=it [ldap] ldap_get_conn: Checking Id: 0 [ldap] ldap_get_conn: Got Id: 0 [ldap] attempting LDAP reconnection [ldap] (re)connect to ldapslave.server.schoolnetwork.it:389, authentication 0 [ldap] bind as cn=admin,dc=schoolnetwork,dc=it/my_pass to ldapslave.server.schoolnetwork.it:389 [ldap] waiting for bind result ... [ldap] Bind was successful [ldap] performing search in ou=Users,dc=schoolnetwork,dc=it, with filter (uid=pippo) [ldap] No default NMAS login sequence [ldap] looking for check items in directory... [ldap] userPassword -> Password-With-Header == "{SSHA}izUF50QnLSZMf+9fZ/TPKj4rHC/FJ4Qu" [ldap] sambaNtPassword -> NT-Password == 0x3734314639304633333534374333384444354337393833374630444531463146 [ldap] radiusCallingStationId -> Calling-Station-Id == "38-59-F9-A3-94-29" [ldap] looking for reply items in directory... [ldap] radiusTunnelPrivateGroupId -> Tunnel-Private-Group-Id:0 = "41" [ldap] radiusTunnelMediumType -> Tunnel-Medium-Type:0 = IEEE-802 [ldap] radiusTunnelType -> Tunnel-Type:0 = VLAN [ldap] user pippo authorized to use remote access [ldap] ldap_release_conn: Release Id: 0 ++[ldap] returns ok ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel Using Post-Auth-Type Reject WARNING: Unknown value specified for Post-Auth-Type. Cannot perform requested action. Delaying reject of request 0 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 0 Sending Access-Reject of id 63 to 127.0.0.1 port 52032 Tunnel-Private-Group-Id:0 = "41" Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Type:0 = VLAN Waking up in 4.9 seconds. Cleaning up request 0 ID 63 with timestamp +4 Ready to process requests. Ok, I know, there is an Auth-Type issue, but I think this is not the point because the LDAP server is properly interrogated. ********** sites-enables/inner-tunnel server inner-tunnel { listen { ipaddr = 127.0.0.1 port = 18120 type = auth } authorize { suffix # ntdomain update control { Proxy-To-Realm := LOCAL } eap { ok = return } ldap } authenticate { Auth-Type MS-CHAP { mschap } eap } session { radutmp } post-auth { } pre-proxy { } post-proxy { eap } } ********** sites-enabled/default authorize { filter_username preprocess auth_log suffix # ntdomain eap { ok = return } } authenticate { eap } preacct { preprocess } accounting { sql detail attr_filter.accounting_response } session { # radutmp # sql } post-auth { reply_log sql Post-Auth-Type REJECT { # log failed authentications in SQL, too. sql attr_filter.access_reject } } pre-proxy { } post-proxy { } ********** Thanks for the assist. I've been fighting with this for days. Stefano

4 9

Specific, complicated, detailed user rights possibility?
by Mart Pirita 14 Sep '15

14 Sep '15

Hi, We have idea to use radius for rights and ldap for authentication. So that radius acts proxy for external ldap and this part is working. But we need more detailed setup, for example, the idea is to allow user1 access some switches and disable user1 to access some other switches. And then even more specific rights, for example, switches which user1 can access, he have some switch with read-only and some other switch with read-write rights. And do it with groups, not using different configuration for every user, for example, so that users are listed in as groups, and these groups are used in access configurations? Huntgroups may be the solution, but as far I know, huntgroups are for device, and not for user rights. Also I don't know, can one and same device IP exist in many different huntgroups and can one huntgroup include other huntgroups? Is such setup possible and if yes, then how? -- Mart

2 5

Re: Freeradius with LNS & Provider BRAS
by Neil Morris 14 Sep '15

14 Sep '15

Thanks Alan. Here¹s the thing.. My SP tell me I am sending the the correct details, its just that the info for the specific user that they tell me is whats causing the issue.. I have take some of my config from the following link¹ https://supportforums.cisco.com/discussion/11294066/session-vrf-mpls-vpn-usi ng-radius-attribute Using the users file how to I separate the radcheck / radreply sections as this to appears to be part if not all of my issue Kind Regards, Neil From: Alan Buxey <A.L.M.Buxey(a)lboro.ac.uk> Date: Friday, 11 September 2015 15:27 To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org>, Neil Morris <nmorris(a)tibus.com> Subject: Re: Freeradius-Users Digest, Vol 125, Issue 34 You aren't sending them what they request. Read your email and see the differences eg service-type Alan From: Neil Morris <nmorris(a)tibus.com> Date: Friday, 11 September 2015 15:02 To: <freeradius-users(a)lists.freeradius.org> Subject: Re: Freeradius with LNS & Provider BRAS Alan, Firstly thanks for you responses to date! I do appreciate it.. Apologies for the lack of detail here is more info FreeRADIUS Version 2.1.12 I have deployed using just the local users file with x3 test accounts including the information that the provider has requested I respond with to complete the auth between our LNS and their BRAS. I had x1 connection up and stable for 3weeks. I shipped out x2 more routers and I start to see some strange behaviour. FR authenticates the session fine but on the router console the interface is reset straight away and so the loop of authentication continues. Running FR in debug/verbose I can see the sessions being authenticated as I would expect with all of the relevant user attributes being passed. The below is what the SP has requested I return to their BRAS; mydom.net.uk Cleartext-Password := ³password" Service-Type = Outbound-User, Tunnel-Type = L2TP, Tunnel-Medium-Type = IP, Tunnel-Password = password, Tunnel-Server-Endpoint = 89.x.y.134, Tunnel-Client-Auth-ID = ³MY-LNS" The following is an example of a user account and the Cisco AVP that I am sending; test(a)mydom.net.uk Cleartext-Password := ³test" Service-Type = Framed-User, Framed-Protocol = PPP, Framed-MTU = 1440, Framed-IP-Address = 10.31.253.253, Framed-IP-Netmask = 255.255.255.255, Framed-Route = "0.0.0.0 0.0.0.0 89.x.y.134", Cisco-AVPair = "ip:vrf-id=VRF_417858", Cisco-Avpair += "ip:route#1=vrf VRF_417858 10.31.249.0 255.255.255.0 10.31.253.253 tag 417858", Cisco-AVPair += "ip:ip-unnumbered=Loopback417858" The SP is advising me that from their debugs I am sending them everything after the username & password as listed above.. They mention that I should have 2 instances for RADIUS or that I change the radius system I use.. Regards Neil Message: 5 Date: Fri, 11 Sep 2015 08:19:56 -0400 From: Alan DeKok <aland(a)deployingradius.com> To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Subject: Re: Freeradius with LNS & Provider BRAS Message-ID: <D70545FB-75A6-41F2-8E25-4E3FE3E06CC0(a)deployingradius.com> Content-Type: text/plain; charset=iso-8859-1 On Sep 11, 2015, at 7:09 AM, Neil Morris <nmorris(a)tibus.com> wrote: > I am looking for some guidance. I am using the users file which contains x3 > user accounts aswell as the domain suffix & the necessary authentication > details for the providers RADIUS server. Under the user accounts I have a > number of cisco avp with VRF & static address etc for the LNS That's a bit vague, but OK. > Whoever The provider is telling me that I am passing all the LNS relate > info to their RADIUS which is causing the tunnel build to fail. That's even more vague. > Is there > something major that I am missing here in relation to my config? A good description of the problem? Alan DeKok. ------------------------------

3 4

https Radius authentication problem
by Timmy 13 Sep '15

13 Sep '15

Dear All Radius Developers, I am doing a web Radius authentication. I am also reading Mr. Alan DeKok's article about its security issue. https://github.com/FreeRADIUS/mod_auth_radius For http connection to the website, we know that the password is not encrypted. Now I set up a SSL certificate for the website in question. How do you rate the security of this https Radius authentication? Is the password, being sent over the internet, also encrypted by the usual SSL layer? Hope to receive your helpful response. Yours Faithfully, Timmy

3 4

rlm_detail header not expanding \t
by Matthew Newton 12 Sep '15

12 Sep '15

In v2 I do: detail { ... header = "%t\t%{Client-IP-Address}" ... } which gives e.g. Wed Sep 9 16:55:16 2015 127.0.0.1 ... in the detail file. Building a config for v3, the same gives: Wed Sep 9 16:55:16 2015127.0.0.1 i.e. the \t is silently discarded and expands to nothing. I can get around it by putting a physical tab char in the config, but is this intended? Have stared at the radius_xlat code for too many minutes and figured it'd be quicker to ask... :) Cheers, Matthew -- Matthew Newton, Ph.D. <mcn4(a)le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp(a)le.ac.uk>

3 10

FreeRadius and AD authentication
by Dennis Xu 11 Sep '15

11 Sep '15

I have installed FreeRadius 3.04 on RHEL7 and configured FreeRadius and Samba according to the following docs: http://wiki.freeradius.org/guide/FreeRADIUS-Active-Directory-Integration-HO… http://deployingradius.com/documents/configuration/active_directory.html Both wbinfo and ntlm_auth tests worked fine: [root@rotator mods-available]# wbinfo -a dxu001%xxxxxxx plaintext password authentication failed Could not authenticate user dxu001%xxxxxxxx with plaintext password challenge/response password authentication succeeded [root@rotator mods-available]# ntlm_auth --request-nt-key --domain=cfs.uoguelph.ca --username=dxu001 Password: NT_STATUS_OK: Success (0x0) [root@rotator mods-available]# When I tried to authenticate using username dxu001, the authentication failed. Below is the debug outputs: server inner-tunnel { (15) server inner-tunnel { (15) Request: EAP-Message = 0x020700411a0207003c31ea301dc50a02a3039d53ef8da042028d0000000000000000416ca750de3cd86e2f16a1533433d62264a5a1946f17c6c400647875303031 FreeRADIUS-Proxied-To = 127.0.0.1 User-Name = 'dxu001' State = 0x20b8045120bf1e31a648ded5aa0c1cba Chargeable-User-Identity = 0x00 Location-Capable = Civix-Location Calling-Station-Id = '90-18-7c-17-97-6c' Called-Station-Id = '04-fe-7f-93-7c-a0:test-secure' NAS-Port = 1 Acct-Session-Id = '55f2fb67/90:18:7c:17:97:6c/97' NAS-IP-Address = 131.104.45.66 NAS-Identifier = 'WLC_TEST' Service-Type = Framed-User Framed-MTU = 1300 NAS-Port-Type = Wireless-802.11 Event-Timestamp = 'Sep 11 2015 12:05:06 EDT' (15) # Executing section authorize from file /etc/raddb/sites-enabled/inner-tunnel (15) authorize { (15) [chap] = noop (15) [mschap] = noop (15) suffix : Checking for suffix after "@" (15) suffix : No '@' in User-Name = "dxu001", looking up realm NULL (15) suffix : No such realm "NULL" (15) [suffix] = noop (15) update control { (15) Proxy-To-Realm := 'LOCAL' (15) } # update control = noop (15) eap : Peer sent code Response (2) ID 7 length 65 (15) eap : No EAP Start, assuming it's an on-going EAP conversation (15) [eap] = updated (15) [files] = noop (15) [expiration] = noop (15) [logintime] = noop (15) [pap] = noop (15) } # authorize = updated (15) Found Auth-Type = EAP (15) # Executing group from file /etc/raddb/sites-enabled/inner-tunnel (15) authenticate { (15) eap : Expiring EAP session with state 0x20b8045120bf1e31 (15) eap : Finished EAP session with state 0x20b8045120bf1e31 (15) eap : Previous EAP request found for state 0x20b8045120bf1e31, released from the list (15) eap : Peer sent method MSCHAPv2 (26) (15) eap : EAP MSCHAPv2 (26) (15) eap : Calling eap_mschapv2 to process EAP data (15) eap_mschapv2 : # Executing group from file /etc/raddb/sites-enabled/inner-tunnel (15) eap_mschapv2 : Auth-Type MS-CHAP { (15) mschap : Creating challenge hash with username: dxu001 (15) mschap : Client is using MS-CHAPv2 Executing: /usr/bin/ntlm_auth --request-nt-key --username=%{%{Stripped-User-Name}:-%{%{User-Name}:-None}} --domain=%{%{mschap:NT-Domain}:-CFS.UOGUELPH.CA} --challenge=%{%{mschap:Challenge}:-00} --nt-response=%{%{mschap:NT-Response}:-00}: (15) mschap : EXPAND --username=%{%{Stripped-User-Name}:-%{%{User-Name}:-None}} (15) mschap : --> --username=dxu001 (15) ERROR: mschap : No NT-Domain was found in the User-Name (15) mschap : EXPAND --domain=%{%{mschap:NT-Domain}:-CFS.UOGUELPH.CA} (15) mschap : --> --domain=CFS.UOGUELPH.CA (15) mschap : Creating challenge hash with username: dxu001 (15) mschap : EXPAND --challenge=%{%{mschap:Challenge}:-00} (15) mschap : --> --challenge=43f96f7805c5bb5a (15) mschap : EXPAND --nt-response=%{%{mschap:NT-Response}:-00} (15) mschap : --> --nt-response=416ca750de3cd86e2f16a1533433d62264a5a1946f17c6c4 Program returned code (1) and output 'Reading winbind reply failed! (0xc0000001)' (15) mschap : External script failed (15) ERROR: mschap : External script says: Reading winbind reply failed! (0xc0000001) (15) ERROR: mschap : MS-CHAP2-Response is incorrect (15) [mschap] = reject Any ideas? Thanks!

1 1

Proxied Access-Challenge requests are missing AVPs
by Leonardo Arena 11 Sep '15

11 Sep '15

Hi list, I have a FreeRADIUS 3.0.3 proxy which forward all Cisco WAPs Wireless-802.11 authentication requests to a Windows NPS server. Clients use PEAP to authenticate. What I'm seeing is that the Access-Challenge from the NPS is forwarded without any AVPs, and of course the WAP silently drops it. Please find below the debug output and the relevant configuration files attached. Couldn't find really anything helpful in the ML archive. Could you please give me any suggestion of what could be wrong? Please let me know if further information is needed. Thank you in advance for your kind assistance. - leonardo Received Access-Request Id 111 from 10.97.6.140:1645 to 10.97.63.5:1812 length 216 User-Name = 'mbianchi' Framed-MTU = 1400 Called-Station-Id = 'DC-A5-F4-FE-BE-71:WRES-DEV' Calling-Station-Id = 'ac22.0ba5.9688' Cisco-AVPair = 'ssid=WRES-DEV' Service-Type = Login-User Cisco-AVPair = 'service-type=Login' Message-Authenticator = 0x98e4b1c896994939e0de6e25c17b96a0 EAP-Message = 0x0201000b016c6172656e61 NAS-Port-Type = Wireless-802.11 Cisco-NAS-Port = '374' NAS-Port = 374 NAS-Port-Id = '374' NAS-IP-Address = 10.97.6.140 NAS-Identifier = 'dev-rto004-r1-ap-1' (1) # Executing section authorize from file /etc/raddb/sites-enabled/default-bsn (1) authorize { (1) [preprocess] = ok (1) linelog_auth : EXPAND /var/log/radius/linelog_auth.log (1) linelog_auth : --> /var/log/radius/linelog_auth.log (1) linelog_auth : EXPAND %S, %{User-Name}, %{NAS-Identifier}(%{NAS-IP-Address}):%{NAS-Port-Id}, Calling-Station-Id: %{Calling-Station-Id}, Packet-Type: %{Packet-Type}, Service-Type: %{Service-Type} (1) linelog_auth : --> 2015-09-10 13:44:55, mbianchi, dev-rto004-r1-ap-1(10.97.6.140):374, Calling-Station-Id: ac22.0ba5.9688, Packet-Type: Access-Request, Service-Type: Login-User (1) [linelog_auth] = ok (1) suffix : No '@' in User-Name = "mbianchi", looking up realm NULL (1) suffix : No such realm "NULL" (1) [suffix] = noop (1) if (!updated) (1) if (!updated) -> TRUE (1) if (!updated) { (1) if (NAS-Port-Type == Wireless-802.11) (1) if (NAS-Port-Type == Wireless-802.11) -> TRUE (1) if (NAS-Port-Type == Wireless-802.11) { (1) update control { (1) &Proxy-To-Realm := 'my.domain.org' (1) } # update control = noop (1) } # if (NAS-Port-Type == Wireless-802.11) = noop (1) ... skipping else for request 1: Preceding "if" was taken (1) } # if (!updated) = noop (1) } # authorize = ok (1) Proxying request to home server 10.44.16.110 port 1812 Sending Access-Request Id 226 from 0.0.0.0:46821 to 10.44.16.110:1812 User-Name = 'mbianchi' Framed-MTU = 1400 Called-Station-Id = 'DC-A5-F4-FE-BE-71:WRES-DEV' Calling-Station-Id = 'ac22.0ba5.9688' Cisco-AVPair = 'ssid=WRES-DEV' Service-Type = Login-User Cisco-AVPair = 'service-type=Login' Message-Authenticator = 0x98e4b1c896994939e0de6e25c17b96a0 EAP-Message = 0x0201000b016c6172656e61 NAS-Port-Type = Wireless-802.11 Cisco-NAS-Port = '374' NAS-Port = 374 NAS-Port-Id = '374' NAS-IP-Address = 10.97.6.140 NAS-Identifier = 'dev-rto004-r1-ap-1' Proxy-State = 0x313131 Waking up in 0.3 seconds. Waking up in 0.4 seconds. Received Access-Challenge Id 226 from 10.44.16.110:1812 to 10.97.63.5:46821 length 95 Proxy-State = 0x313131 Session-Timeout = 30 EAP-Message = 0x010200061920 State = 0x1c5503ba00000137000102000a2c106e0000000000000000000000000000000c6d95d8e4 Message-Authenticator = 0xe5ba33c9fca2c5534a4e1302650ae8ca Sending Access-Challenge Id 111 from 10.97.63.5:1812 to 10.97.6.140:1645 (1) Finished request Waking up in 0.3 seconds. Waking up in 3.0 seconds. (0) Cleaning up request packet ID 110 with timestamp +12 Waking up in 1.6 seconds.

4 15