Automatic report from sources (radiusd) between 06.11.2007 - 07.11.2007 GMT
CVS log entries from 06.11.2007 (Tue) 09:00:01 - 07.11.2007 (Wed) 09:00:01 GMT ===================================================== Summary by authors ===================================================== Author: aland File: radiusd/src/modules/rlm_ldap/rlm_ldap.c; Revisions: 1.188 File: radiusd/raddb/radiusd.conf.in; Revisions: 1.188.2.4.2.19 ===================================================== Log entries ===================================================== Description: Note that reject_delay = 0 is a good idea Modified files: File: radiusd/raddb/radiusd.conf.in; Revision: 1.188.2.4.2.19; Date: 2007/11/06 21:55:08; Author: aland; Lines: (+6 -3) ------------------------------- Description: If there's no User-Name, ldap is a NOOP, not a failure Modified files: File: radiusd/src/modules/rlm_ldap/rlm_ldap.c; Revision: 1.188; Date: 2007/11/06 21:55:40; Author: aland; Lines: (+3 -3) ===================================================== Summary of modified files ===================================================== File: radiusd/raddb/radiusd.conf.in Revisions: 1.188.2.4.2.19 Authors: aland (+6 -3) ------------------------------- File: radiusd/src/modules/rlm_ldap/rlm_ldap.c Revisions: 1.188 Authors: aland (+3 -3) -- Automatic cron job from /web/pages/us.freeradius.org/bin/new_makelog.pl
Automatic cvs log generator wrote:
CVS log entries from 06.11.2007 (Tue) 09:00:01 - 07.11.2007 (Wed) 09:00:01 GMT ===================================================== Summary by authors ===================================================== Author: aland File: radiusd/src/modules/rlm_ldap/rlm_ldap.c; Revisions: 1.188 File: radiusd/raddb/radiusd.conf.in; Revisions: 1.188.2.4.2.19
===================================================== Log entries ===================================================== Description: Note that reject_delay = 0 is a good idea
Why ? Unless someone sets the timeout on the NAS to be <= 2 then the default of 1 should be fine... Or is there some more complicated / interesting reason ?
Modified files: File: radiusd/raddb/radiusd.conf.in; Revision: 1.188.2.4.2.19; Date: 2007/11/06 21:55:08; Author: aland; Lines: (+6 -3) ------------------------------- Description: If there's no User-Name, ldap is a NOOP, not a failure Modified files: File: radiusd/src/modules/rlm_ldap/rlm_ldap.c; Revision: 1.188; Date: 2007/11/06 21:55:40; Author: aland; Lines: (+3 -3) ===================================================== Summary of modified files ===================================================== File: radiusd/raddb/radiusd.conf.in Revisions: 1.188.2.4.2.19 Authors: aland (+6 -3) ------------------------------- File: radiusd/src/modules/rlm_ldap/rlm_ldap.c Revisions: 1.188 Authors: aland (+3 -3)
-- Arran Cudbard-Bell (A.Cudbard-Bell@sussex.ac.uk) Authentication, Authorisation and Accounting Officer Infrastructure Services | ENG1 E1-1-08 University Of Sussex, Brighton EXT:01273 873900 | INT: 3900
Arran Cudbard-Bell wrote:
File: radiusd/raddb/radiusd.conf.in; Revisions: 1.188.2.4.2.19
...
Note that reject_delay = 0 is a good idea
Why ? Unless someone sets the timeout on the NAS to be <= 2 then the default of 1 should be fine... Or is there some more complicated / interesting reason ?
1.1.x doesn't properly handle reject_delay > 0. 2.x does. Alan DeKok.
Alan DeKok wrote:
Arran Cudbard-Bell wrote:
File: radiusd/raddb/radiusd.conf.in; Revisions: 1.188.2.4.2.19
...
Note that reject_delay = 0 is a good idea
Why ? Unless someone sets the timeout on the NAS to be <= 2 then the default of 1 should be fine... Or is there some more complicated / interesting reason ?
1.1.x doesn't properly handle reject_delay > 0.
2.x does.
Ok. On a completely different subject, do you mind the 'known issues' bit I added to the HP Procurve section of the wiki. It's not strictly FreeRadius related, but is Radius related... ish... http://wiki.freeradius.org/HP Do any NAS vendors handle User-Name attributes in access-accept packets correctly ?!
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
On Wednesday 07 November 2007 14:16:08 Arran Cudbard-Bell wrote:
Do any NAS vendors handle User-Name attributes in access-accept packets correctly ?!
It works on an Ascend Max-TNT as long as it's configured to change the user-name (I think this is the default). I've tried to get it working on a Cisco before, but eventually gave up and forced everyone to use a realm. Kevin Bonner
Arran Cudbard-Bell wrote:
On a completely different subject, do you mind the 'known issues' bit I added to the HP Procurve section of the wiki. It's not strictly FreeRadius related, but is Radius related... ish...
Issues with AP's or NASes belong on the Wiki.
Do any NAS vendors handle User-Name attributes in access-accept packets correctly ?!
Yes. Some do. Alan DeKok.
participants (4)
-
Alan DeKok -
Arran Cudbard-Bell -
Automatic cvs log generator -
Kevin Bonner