SOLVED. Modified my proxy.conf file as per another list post. You cannot just add the 'nostrip' option to the realm. You must remove the home_server and home_server_pool, but keep the options from the home_server and put them under the realm.
Here is my proxy.conf file contents:proxy server {default_fallback = no}home_server localhost {type = authipaddr = 127.0.0.1port = 1812secret = testing123require_message_authenticator = yesresponse_window = 20zombie_period = 40revive_interval = 120status_check = status-servercheck_interval = 30num_answers_to_alive = 3max_outstanding = 65536coa {irt = 2mrt = 16mrc = 5mrd = 30}}home_server_pool my_auth_failover {type = fail-overhome_server = localhost}realm example.com {auth_pool = my_auth_failovernostrip}realm LOCAL {}On Sun, Dec 9, 2012 at 11:09 AM, Dan Letkeman <danletkeman@gmail.com> wrote:
Alan,I have added 'nostrip' to the realm example.com and it looks like it has problems with that. Possibly some sort of loop?On Sun, Dec 9, 2012 at 9:58 AM, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
Hi,
EAP doesnt like the user-name being played around with....ensure that you 'nostrip'
> [eap] Identity does not match User-Name, setting from EAP Identity.
in your proxy.conf for the realm you are handling....or use 'stripped-user-name'
for the checks/handlers.
alan