(RADIATOR) Authentication Issue - Odyssey and iPaq 5450

[Bon sy]

Hi Steve,
	From your calling station ID, it seems like you are using Cisco
wireless gear. I recently played with Meetinghouse client for ipaq 5450. I
could not get it to work too. But my problem is not on the radius
side. 

	Our Cisco wireless gear set up uses dynamic key, which Meetinghouse
client does not support. I have no experience with Odyssey client. Based
on your description, if this is the same issue as we encountered, the
solution (as Meetinghouse tech support suggested) is to roll back to use
only static encryption key for the client in order to get it to work. But
then it kind of defeats the whole purpose of setting up strong security
to begin with.

	I am currently exploring an alternative, which is to upgrade my
ipaq 5450 to run Mobile (Pocket PC) 2003. It claims to support 802.1x but
I am still waiting for my order. It would be great if anyone in this
list has experience to share in regard to whether Mobile 2003 will do the
trick with its zero configuration for supporting 802.1x connection..

	Thanks!

Bon


On Mon, 6 Oct 2003, Steve Caporossi wrote:

> I'm having an issue authenticating users with the iPaq 5450 (internal
> nic) and the Odyssey Client.  It appears that when the user 
> authenticates, Radiator initially issues an access-accept and then 
> follows it up with an access-reject.
> 
> I am only having this issue with the above device....all other clients 
> authenticate sucessfully.  Any ideas would be appreciated.
> 
> Attached are debugs and the config.  Radiator version 3.7.1 on RH7.3.
> 
> Thanks,
> -- 
> Steve Caporossi
> Network Systems Engineer
> Center for Computing and Information Technology
> Medical University of South Carolina
> 843.876.5083
> 
> 
> 

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.