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

Re: freeradius2.1.6 module errors (Doug Hardie)
by ramesh p 12 Aug '09

12 Aug '09

I'am trying to log only "Stop" packets, and i'm not storing start,Tunnel-Stop, Tunnel-start,Failed etc... packets Please advice. Thanks, Rams. On Wed, Aug 12, 2009 at 3:30 PM, < freeradius-users-request(a)lists.freeradius.org> wrote: > Send Freeradius-Users mailing list submissions to > freeradius-users(a)lists.freeradius.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freeradius.org/mailman/listinfo/freeradius-users > or, via email, send a message with subject or body 'help' to > freeradius-users-request(a)lists.freeradius.org > > You can reach the person managing the list at > freeradius-users-owner(a)lists.freeradius.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Freeradius-Users digest..." > > > Today's Topics: > > 1. Re: freeradius2.1.6 module errors (Doug Hardie) > 2. Freeradius with jradius (shivashankar) > 3. Help with passwords (David Jansen) > 4. Re: Help with passwords (Alan DeKok) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 11 Aug 2009 16:05:21 -0700 > From: Doug Hardie <bc979(a)lafn.org> > Subject: Re: freeradius2.1.6 module errors > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Message-ID: <EBEB797D-D771-46BE-BA70-C8BE1F2959FA(a)lafn.org> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > > On 11 August 2009, at 06:54, ramesh p wrote: > > > Am doing it correctly? Please suggest? > > Obviously not since FreeRADIUS is telling you it doesn't understant > the Acct-Type of Ignore. I suspect you are not getting a good answer > is that I (for one) do not understand what you are trying to > accomplish. You use the term ignore which implies to me that you want > FreeRADIUS to drop any non Stop packets and not respond at all. That > means that the NAS will continue to retry every one of those packets > for some predetermined number of times wasting bandwidth. I would > recommend providing some details on what you want to accomplish and > someone may be able to show you how to do that. > > > > > Thanks, > > Rams. > > > > 4. freeradius2.1.6 module errors (ramesh p) > > > > > > ---------------------------------------------------------------------- > > > > Message: 4 > > Date: Tue, 11 Aug 2009 12:50:30 +0530 > > From: ramesh p <rock786143(a)gmail.com> > > Subject: freeradius2.1.6 module errors > > To: FreeRadius users mailing list > > <freeradius-users(a)lists.freeradius.org> > > Message-ID: > > <6b6aa6710908110020r50a6d15aked46497f07cdadc7(a)mail.gmail.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > > Hi All, > > > > I have placed a small module "IGNORE" to ignore packets other than > > "Stop" > > type. > > > > modified acct_users file as: > > > > DEFAULT Acct-Status-Type == "Tunnel-Stop", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Tunnel-Start", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Start", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Failed", Acct-Type := "IGNORE" > > #DEFAULT Acct-Status-Type == "Checkpoint", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Accounting-On", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Accounting-Off", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Tunnel-Reject", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Tunnel-Link-Start", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Tunnel-Link-Stop", Acct-Type := "IGNORE" > > DEFAULT Acct-Status-Type == "Tunnel-Link-Reject", Acct-Type := > > "IGNORE" > > > > and added the following in accounting section of main configuration > > file : > > > > Acct-Type IGNORE { > > > > ok > > > > } > > > > The above configuration was working in 1.1.6 version. However getting > > following error in 2.1.6 version. > > Module: Instantiating files > > files { > > usersfile = "/usr/local/fnmt/freeradius2//etc/raddb/users" > > acctusersfile = "/usr/local/fnmt/freeradius2//etc/raddb/ > > acct_users" > > preproxy_usersfile = > > "/usr/local/fnmt/freeradius2//etc/raddb/preproxy_users" > > compat = "no" > > } > > /usr/local/fnmt/freeradius2//etc/raddb/acct_users[25]: Parse error > > (check) > > for entry DEFAULT: Unknown value IGNORE for attribute Acct-Type > > > > > > Errors reading /usr/local/fnmt/freeradius2//etc/raddb/acct_users > > /usr/local/fnmt/freeradius2//etc/raddb/modules/files[7]: Instantiation > > failed for module "files" > > > > please help. > > > > Thanks, > > Rams. > > Please help > >

1 0

Help with passwords
by David Jansen 12 Aug '09

12 Aug '09

Hi, Although passwords are filtered in radius log i do still see unencrypted passwords in auth-detail-%% files in /var/log/radius/radacct. How can I get rid of these passwords? Kind regards David Jansen

2 1

Freeradius with jradius
by shivashankar 12 Aug '09

12 Aug '09

hi , i configured Jradius with Freeradius. but i don't know how to wirte java code and compile in jradius. is any doucment.? could u plz help. . Regard's shiva shankar -- View this message in context: http://www.nabble.com/Freeradius-with-jradius-tp24931286p24931286.html Sent from the FreeRadius - User mailing list archive at Nabble.com.

1 0

Re: freeradius2.1.6 module errors
by ramesh p 11 Aug '09

11 Aug '09

Am doing it correctly? Please suggest? Thanks, Rams. > > 4. freeradius2.1.6 module errors (ramesh p) > > > ---------------------------------------------------------------------- > > Message: 4 > Date: Tue, 11 Aug 2009 12:50:30 +0530 > From: ramesh p <rock786143(a)gmail.com> > Subject: freeradius2.1.6 module errors > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Message-ID: > <6b6aa6710908110020r50a6d15aked46497f07cdadc7(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi All, > > I have placed a small module "IGNORE" to ignore packets other than "Stop" > type. > > modified acct_users file as: > > DEFAULT Acct-Status-Type == "Tunnel-Stop", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Tunnel-Start", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Start", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Failed", Acct-Type := "IGNORE" > #DEFAULT Acct-Status-Type == "Checkpoint", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Accounting-On", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Accounting-Off", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Tunnel-Reject", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Tunnel-Link-Start", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Tunnel-Link-Stop", Acct-Type := "IGNORE" > DEFAULT Acct-Status-Type == "Tunnel-Link-Reject", Acct-Type := "IGNORE" > > and added the following in accounting section of main configuration file : > > Acct-Type IGNORE { > > ok > > } > > The above configuration was working in 1.1.6 version. However getting > following error in 2.1.6 version. > Module: Instantiating files > files { > usersfile = "/usr/local/fnmt/freeradius2//etc/raddb/users" > acctusersfile = "/usr/local/fnmt/freeradius2//etc/raddb/acct_users" > preproxy_usersfile = > "/usr/local/fnmt/freeradius2//etc/raddb/preproxy_users" > compat = "no" > } > */usr/local/fnmt/freeradius2//etc/raddb/acct_users[25]: Parse error > (check) > for entry DEFAULT: Unknown value IGNORE for attribute Acct-Type* > * > *Errors reading /usr/local/fnmt/freeradius2//etc/raddb/acct_users > /usr/local/fnmt/freeradius2//etc/raddb/modules/files[7]: Instantiation > failed for module "files" > > please help. > > Thanks, > Rams. > Please help >

2 1

FreeRADIUS 2.1.6 and Cisco 802.1x MAC Authentication with mac-auth-bypass
by Amaru Netapshaak 11 Aug '09

11 Aug '09

Hello! I am struggling with a mac-auth-bypass problem with my Cisco 6509s and my FreeRADIUS server. The 6509 sends the radius server the request, FreeRADIUS authenticates it as OK, but yet my port remains in the "authfail" state on the switch. Does anyone have any ideas? Here is my debug output from the radius box: The first part is the debug output / freeradius startup, the 2nd part is a request I get from my switch to authenticate some "azbycx" user, so I just added it to users for now, and then the 3rd part is the request/response for my MAC address to be authenticated. Thanks for your help! (root@nms) % ./radiusd -X FreeRADIUS Version 2.1.6, for host i386-unknown-freebsd7.2, built on Aug 6 2009 at 16:34:56 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/freeradius/etc/raddb/radiusd.conf including configuration file /usr/local/freeradius/etc/raddb/proxy.conf including configuration file /usr/local/freeradius/etc/raddb/clients.conf including files in directory /usr/local/freeradius/etc/raddb/modules/ including configuration file /usr/local/freeradius/etc/raddb/modules/acct_unique including configuration file /usr/local/freeradius/etc/raddb/modules/always including configuration file /usr/local/freeradius/etc/raddb/modules/attr_filter including configuration file /usr/local/freeradius/etc/raddb/modules/attr_rewrite including configuration file /usr/local/freeradius/etc/raddb/modules/chap including configuration file /usr/local/freeradius/etc/raddb/modules/checkval including configuration file /usr/local/freeradius/etc/raddb/modules/counter including configuration file /usr/local/freeradius/etc/raddb/modules/detail including configuration file /usr/local/freeradius/etc/raddb/modules/detail.example.com including configuration file /usr/local/freeradius/etc/raddb/modules/detail.log including configuration file /usr/local/freeradius/etc/raddb/modules/digest including configuration file /usr/local/freeradius/etc/raddb/modules/echo including configuration file /usr/local/freeradius/etc/raddb/modules/etc_group including configuration file /usr/local/freeradius/etc/raddb/modules/exec including configuration file /usr/local/freeradius/etc/raddb/modules/expiration including configuration file /usr/local/freeradius/etc/raddb/modules/expr including configuration file /usr/local/freeradius/etc/raddb/modules/files including configuration file /usr/local/freeradius/etc/raddb/modules/inner-eap including configuration file /usr/local/freeradius/etc/raddb/modules/ippool including configuration file /usr/local/freeradius/etc/raddb/modules/krb5 including configuration file /usr/local/freeradius/etc/raddb/modules/ldap including configuration file /usr/local/freeradius/etc/raddb/modules/linelog including configuration file /usr/local/freeradius/etc/raddb/modules/logintime including configuration file /usr/local/freeradius/etc/raddb/modules/mac2ip including configuration file /usr/local/freeradius/etc/raddb/modules/mac2vlan including configuration file /usr/local/freeradius/etc/raddb/modules/mschap including configuration file /usr/local/freeradius/etc/raddb/modules/otp including configuration file /usr/local/freeradius/etc/raddb/modules/pam including configuration file /usr/local/freeradius/etc/raddb/modules/pap including configuration file /usr/local/freeradius/etc/raddb/modules/passwd including configuration file /usr/local/freeradius/etc/raddb/modules/perl including configuration file /usr/local/freeradius/etc/raddb/modules/policy including configuration file /usr/local/freeradius/etc/raddb/modules/preprocess including configuration file /usr/local/freeradius/etc/raddb/modules/radutmp including configuration file /usr/local/freeradius/etc/raddb/modules/realm including configuration file /usr/local/freeradius/etc/raddb/modules/smbpasswd including configuration file /usr/local/freeradius/etc/raddb/modules/smsotp including configuration file /usr/local/freeradius/etc/raddb/modules/sql_log including configuration file /usr/local/freeradius/etc/raddb/modules/sqlcounter_expire_on_login including configuration file /usr/local/freeradius/etc/raddb/modules/sradutmp including configuration file /usr/local/freeradius/etc/raddb/modules/unix including configuration file /usr/local/freeradius/etc/raddb/modules/wimax including configuration file /usr/local/freeradius/etc/raddb/eap.conf including configuration file /usr/local/freeradius/etc/raddb/policy.conf including files in directory /usr/local/freeradius/etc/raddb/sites-enabled/ including configuration file /usr/local/freeradius/etc/raddb/sites-enabled/default including configuration file /usr/local/freeradius/etc/raddb/sites-enabled/inner-tunnel including configuration file /usr/local/freeradius/etc/raddb/sites-enabled/control-socket group = radius user = radius including dictionary file /usr/local/freeradius/etc/raddb/dictionary main { prefix = "/usr/local/freeradius" localstatedir = "/usr/local/freeradius/var" logdir = "/var/log/radius" libdir = "/usr/local/freeradius/lib" radacctdir = "/var/log/radius/radacct" hostname_lookups = yes max_request_time = 20 cleanup_delay = 5 max_requests = 2048 allow_core_dumps = no pidfile = "/var/run/radiusd.pid" checkrad = "/usr/local/freeradius/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = yes auth_badpass = yes auth_goodpass = yes } security { max_attributes = 50 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 = 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 = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 netmask = 32 require_message_authenticator = no secret = "test1111" shortname = "localhost" nastype = "other" } client nhed-nms { ipaddr = 172.16.0.2 netmask = 32 require_message_authenticator = no secret = "test1111" shortname = "nhed-nms" nastype = "other" } client Hib_C6K { ipaddr = 172.16.0.1 netmask = 32 require_message_authenticator = no secret = "test1111" shortname = "Hib_C6K" } 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/radius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "md5" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no 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/freeradius/etc/raddb/certs/server.pem" certificate_file = "/usr/local/freeradius/etc/raddb/certs/server.pem" CA_file = "/usr/local/freeradius/etc/raddb/certs/ca.pem" private_key_password = "whatever" dh_file = "/usr/local/freeradius/etc/raddb/certs/dh" random_file = "/usr/local/freeradius/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/usr/local/freeradius/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 = 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 = no proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating files files { usersfile = "/usr/local/freeradius/etc/raddb/users" acctusersfile = "/usr/local/freeradius/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/freeradius/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/radius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Linked to module rlm_attr_filter Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/usr/local/freeradius/etc/raddb/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_always Module: Instantiating ok always ok { rcode = "ok" simulcount = 0 mpp = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating preprocess preprocess { huntgroups = "/usr/local/freeradius/etc/raddb/huntgroups" hints = "/usr/local/freeradius/etc/raddb/hints" with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = no with_alvarion_vsa_hack = no } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating detail detail { detailfile = "/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Instantiating attr_filter.accounting_response attr_filter attr_filter.accounting_response { attrsfile = "/usr/local/freeradius/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 = 172.16.0.2 port = 0 } listen { type = "acct" ipaddr = 172.16.0.2 port = 0 } listen { type = "control" listen { socket = "/var/tmp/radiusd.sock" } } Listening on authentication address 172.16.0.2 port 1812 Listening on accounting address 172.16.0.2 port 1813 Listening on command file /var/tmp/radiusd.sock Listening on proxy address 172.16.0.2 port 1814 Ready to process requests. ============================================================================================================== rad_recv: Access-Request packet from host 172.16.0.1 port 1024, id=85, length=65 User-Name = "azbycx" NAS-IP-Address = 172.16.0.1 EAP-Message = 0x0255000b01617a62796378 Message-Authenticator = 0x37608640b025ad4025d8c51350583edd +- entering group authorize {...} ++? if ((Service-Type == 'Call-Check') || (User-Name =~ /^%{Calling-Station-ID}$/i)) (Attribute Service-Type was not found) ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "azbycx", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 85 length 11 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[unix] returns notfound [files] users: Matched entry azbycx at line 1 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] Found existing Auth-Type, not changing it. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] EAP Identity [eap] processing type md5 rlm_eap_md5: Issuing Challenge ++[eap] returns handled Sending Access-Challenge of id 85 to 172.16.0.1 port 1024 EAP-Message = 0x0156001604106fa6792845d7180ceea44d483cb7e3d7 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x087297780824931641b6155be504b595 Finished request 0. Going to the next request Waking up in 4.9 seconds. Cleaning up request 0 ID 85 with timestamp +4 Ready to process requests. ============================================================================================================== rad_recv: Access-Request packet from host 172.16.0.1 port 1024, id=85, length=100 NAS-IP-Address = 172.16.0.1 NAS-Port = 515 Service-Type = Call-Check Called-Station-Id = "00-50-3e-97-53-ff" Calling-Station-Id = "00-1c-23-12-3a-73" NAS-Port-Type = Ethernet Message-Authenticator = 0xcbf19506604c664a4b885a8c5a47a9a6 +- entering group authorize {...} ++? if ((Service-Type == 'Call-Check') || (User-Name =~ /^%{Calling-Station-ID}$/i)) ?? Evaluating (Service-Type == 'Call-Check') -> TRUE ?? Skipping (User-Name =~ /^%{Calling-Station-ID}$/i) ++? if ((Service-Type == 'Call-Check') || (User-Name =~ /^%{Calling-Station-ID}$/i)) -> TRUE ++- entering if ((Service-Type == 'Call-Check') || (User-Name =~ /^%{Calling-Station-ID}$/i)) {...} expand: %{Calling-Station-ID} -> 00-1c-23-12-3a-73 expand: %{Calling-Station-ID} -> 00-1c-23-12-3a-73 expand: %{Calling-Station-ID} -> 00-1c-23-12-3a-73 +++[request] returns notfound ++- if ((Service-Type == 'Call-Check') || (User-Name =~ /^%{Calling-Station-ID}$/i)) returns notfound ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "00-1c-23-12-3a-73", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[unix] returns notfound [files] users: Matched entry 00-1c-23-12-3a-73 at line 3 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns updated Found Auth-Type = PAP +- entering group PAP {...} [pap] login attempt with password "00-1c-23-12-3a-73" [pap] Using clear text password "00-1c-23-12-3a-73" [pap] User authenticated successfully ++[pap] returns ok Login OK: [00-1c-23-12-3a-73/00-1c-23-12-3a-73] (from client Hib_C6K port 515 cli 00-1c-23-12-3a-73) +- entering group post-auth {...} ++[exec] returns noop Sending Access-Accept of id 85 to 172.16.0.1 port 1024 Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "237" Finished request 1. Going to the next request Waking up in 4.9 seconds. Cleaning up request 1 ID 85 with timestamp +16 Ready to process requests.

1 0

freeradius2.1.6 module errors
by ramesh p 11 Aug '09

11 Aug '09

Hi All, I have placed a small module "IGNORE" to ignore packets other than "Stop" type. modified acct_users file as: DEFAULT Acct-Status-Type == "Tunnel-Stop", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Tunnel-Start", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Start", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Failed", Acct-Type := "IGNORE" #DEFAULT Acct-Status-Type == "Checkpoint", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Accounting-On", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Accounting-Off", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Tunnel-Reject", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Tunnel-Link-Start", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Tunnel-Link-Stop", Acct-Type := "IGNORE" DEFAULT Acct-Status-Type == "Tunnel-Link-Reject", Acct-Type := "IGNORE" and added the following in accounting section of main configuration file : Acct-Type IGNORE { ok } The above configuration was working in 1.1.6 version. However getting following error in 2.1.6 version. Module: Instantiating files files { usersfile = "/usr/local/fnmt/freeradius2//etc/raddb/users" acctusersfile = "/usr/local/fnmt/freeradius2//etc/raddb/acct_users" preproxy_usersfile = "/usr/local/fnmt/freeradius2//etc/raddb/preproxy_users" compat = "no" } /usr/local/fnmt/freeradius2//etc/raddb/acct_users[25]: Parse error (check) for entry DEFAULT: Unknown value IGNORE for attribute Acct-Type Errors reading /usr/local/fnmt/freeradius2//etc/raddb/acct_users /usr/local/fnmt/freeradius2//etc/raddb/modules/files[7]: Instantiation failed for module "files" please help. Thanks, Rams. Please help

1 0

convert redius request to soap request
by shivashankar 11 Aug '09

11 Aug '09

hi , give me assistence........ i new to freeradius how to convert radius request to SOAP request. is there any way to do this... -- View this message in context: http://www.nabble.com/convert-redius-request-to-soap-request-tp24911693p249… Sent from the FreeRadius - User mailing list archive at Nabble.com.

2 1

Re: [Daloradius-users] Batch PIN Code Authentication
by Deepak 11 Aug '09

11 Aug '09

> When you refer to PIN authentication does this mean that you would like that > Batch User Add > to create batch PIN users with Auth-Type := Accept (meaning, they > automatically authenticate ok > with just providing the PIN number). Is that what would make the current > Batch Add User page > suitable for batch PIN users? > > > Regards, > Liran. Exactly. Currently I can create the PIN users one by one. I have tried the batch add users with password length 0 but the attributes it produces is still User-Password instead of Auth-Type. Also tried with in Batch Add Users with username length = 0 and Password = 0 with custom prefix and added the custom attribute of Auth-Type:=Accept. This seems ok but it is producing double entry in the table. One with Username = something with password = blank and same user with Auth-Type:= Accept. At this point I don't know if this have the same effect as just having only one entry in the table. This is not a big deal. I am just suggesting that it would have been better with that option too. :-) What do you think? It will be less confusing for the users. Regards -- ============================== Registered Linux User #460714 Currently Using Fedora 10, CentOS 5.3 ==============================

1 0

Convention, Rule or Convenience?
by Deepak 10 Aug '09

10 Aug '09

Hi, Sounds like silly question to myself and having second thoughts about asking in the list. I am very new to radius and quite confused about this. Done some research on this too but could not find the answer I am looking for. It is something like this: 1) In "radcheck" table I can insert the username and associated attributes (check and reply) for that user. 2) The same thing can be done by creating a group in "radgroupreply" for reply attributes and creating a group in "radgroupcheck" for check attributes then assigning these group to the user. my question is: 1) Can the group I created in "radgroupcheck" contain the reply attributes or vice versa? What I mean is will that take effect if reply and check attributes are mixed in single (either gropucheck or groupreply)? 2) so the basic question is how does radius check these tables? (a) Is it the rule (hard coded in freeradius) that it will look for reply attributes in "groupreply" table and check attributes in "groupcheck" tables correspondingly? (b) OR it will just check the available (non empty group) table and whatever attributes are defined, it simply evaluates? I am asking this question from point of view that in case I don't use group tables, I can still mix both reply and check attributes in a single table in radcheck without using group. Reason for asking this question: I want to use as many groups as possible for flexibility reason but for certain reason I am allowed to use only one group (just assumed). In this condition, first option will be that I can avoid the group and put as many attributes for certain user in radcheck. Second option is I can mix the attributes in either group I create (groupreply or greoupcheck) and assign this group to the user. But I am not sure about my second option. So basically this is a question about how freeradius works internally in evaluating these attributes. Need some clarification. Thanks -- ============================== Registered Linux User #460714 Currently Using Fedora 10, CentOS 5.3 ==============================

2 1

2.1.6 Segfault (unlang: if (NAS-Port == 0) { reject }
by Michael Bryant 10 Aug '09

10 Aug '09

Hi, Reproducible on 2.1.6, default config with: These lines in the authorize section: if (NAS-Port == 0) { reject } And this command: echo "User-Name = test" | radclient 10.252.24.114 auth testing123 An Access-Request packet not containing the NAS-Port Attribute causes the server to segfault. Cheers --Mike P.S. Workaround: if (NAS-Port && NAS-Port == 0) {

3 2