(RADIATOR) Problems with TTLS session resume

Roy Badami roy.badami at globalgraphics.com
Fri Sep 3 10:33:28 CDT 2004


I'm trying to get TTLS session resumption to work with the Odyssey
Client.

In particular.  It works when I hit the "reauthenticate" button, but
in particular I'd like it to work in the following circumstances:

   * Client briefly goes out of coverage, then reassociates with the AP
   * Client roams from one AP to another.

The problem is that in the first case the NAS Port will change; in the
second the NAS ID will change too.  As a result EAP.pm is unable to
retrieve the context (the key has changed).

Changing 

    my $key = "eap:$nas_id:$nas_port:$calling_station:$rad_user_name";

to

    my $key = "eap:$calling_station:$rad_user_name";

in EAP.pm allows me to resume a session after straying out of
coverage.  I assume it will fix the roaming case too -- assuming
Odyssey Client does the right thing -- though I can't test that since
my test network only has a single AP.

Is there any reason not to do this?  If not, could this be made an
option?

      -roy


--
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.


More information about the radiator mailing list