Attribute of User-name in Access-Accept paket does not match request User-name.

[s_hira at nifty.com]

hello.

I use EAP-TLS authentication in freeRADIUS v2.1.10.

Windows7 Computer authentication in EAP-TLS.
　Access-Request : User-Name = host/user
　Access-Accept  : User-Name = user

=== degug message ===
rad_recv: Access-Request packet from host 192.168.1.102 port 4181, id=236, len
gth=168
	User-Name = "host/user"
	Cisco-AVPair = "ssid=tsunami2"
	NAS-IP-Address = 192.168.1.102
	Called-Station-Id = "00409635c604"
	Calling-Station-Id = "0013ce2ce98c"
	NAS-Identifier = "AP340-35c604"
	NAS-Port = 37
	Framed-MTU = 1400
	State = 0xf63891eaf5349cad6a56444fd9199aec
	NAS-Port-Type = Wireless-802.11
	Service-Type = Login-User
	EAP-Message = 0x020c00060d00
	Message-Authenticator = 0xa007aa9e6ef0359c5b6b5edffe00ecbc
===
Sending Access-Accept of id 236 to 192.168.1.102 port 4181
	Termination-Action = RADIUS-Request
	Session-Timeout = 1800
	MS-MPPE-Recv-Key = 0x27a0af9b85abaccd7314693a3d18bcf32b04534287bbc839219d99cb
9500a6a3
	MS-MPPE-Send-Key = 0x080829ecf636d5d7b8201accbf272cd5cf9fc4241a45dbf98fb2b580
139ada58
	EAP-Message = 0x030c0004
	Message-Authenticator = 0x00000000000000000000000000000000
	User-Name = "user"
===

hints file :
===
 DEFAULT Prefix == "host/"
===

When Stripped-User-Name was set, this value is set to the User-Name attribute 
of the Access-Accept packet.
Is this the wanted behaviour of v2.1.x?
(changed from v1.1.x?)

==========
Satoshi Hirabayashi