Bug 712803 – radtest script is not working with eap-md5 option

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 712803 - radtest script is not working with eap-md5 option

Summary:	radtest script is not working with eap-md5 option

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	freeradius (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	Unspecified Unspecified

Priority	medium Severity low
Target Milestone:	rc
Target Release:	---
Assigned To:	John Dennis
QA Contact:	Patrik Kis
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	846476
	Show dependency tree / graph

Reported:	2011-06-13 04:09 EDT by Karel Srot
Modified:	2012-08-07 17:14 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	freeradius-2.1.12-1.el6
Doc Type:	Bug Fix
Doc Text:	Cause: radtest with eap-md5 fails because it invokes radeapclient passing an ip family argument. Consequence: radtest fails because radeapclient fails to recognize ip family. Fix: radeapclient in the current freeradius release now recognizes the ip family argument. Result: radtest now works with eap-md5.
Story Points:	---
Clone Of:
Clones:	846476 (view as bug list)
Environment:
Last Closed:	2012-06-20 10:05:51 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2012:0881	normal	SHIPPED_LIVE	freeradius bug fix and enhancement update	2012-06-19 16:47:36 EDT

Groups: None (edit)

Description Karel Srot 2011-06-13 04:09:50 EDT

Description of problem:

Radtest script is not working with eap-md5 option. This is becasue radeapclient binary is used for eap-md5 and this binary doesn't support -4 option (for IPv4) which is passed to the binary.

Ugly workaround I have used:


# Set the address family
case "$family" in
	IPv4)
		[ "$radclient" = "$radeapclient" ] || OPTIONS="$OPTIONS -4"
		NAS_ADDR_ATTR="NAS-IP-Address"
		;;
	IPv6)
		OPTIONS="$OPTIONS -6"
		NAS_ADDR_ATTR="NAS-IPv6-Address"
		;;
	*)
		echo "ERROR: unknown address family ($family)" >&2
		usage
esac



Version-Release number of selected component (if applicable):
freeradius-2.1.10-5.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. radtest -t eap-md5 ....
  
Actual results:
Usage message

Expected results:
authentization working

Additional info:

Comment 6 John Dennis 2012-04-24 13:17:48 EDT

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause:

radtest with eap-md5 fails because it invokes radeapclient passing an ip family argument.

Consequence:

radtest fails because radeapclient fails to recognize ip family.

Fix:

radeapclient in the current freeradius release now recognizes the ip family argument.

Result:

radtest now works with eap-md5.

Comment 9 errata-xmlrpc 2012-06-20 10:05:51 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0881.html

Note You need to log in before you can comment on or make changes to this bug.