(RADIATOR) associating clients with handlers
skendric at fhcrc.org
Wed Sep 6 11:18:29 CDT 2006
i'm stumbling over how to associate clients with handlers
i'm using Radiator 3.15 with patches under Windows 2003
here's a snippet from my radius.cfg
[... global parameters ...]
[... log file stuff ... ]
#### Client Definitions ####
#### Handle APC gear ####
# Handle administrative users
AddToReply Service-Type = "Administrative-User"
# Log it
i can see from a packet sniffer the Access-Request packets arriving at
my Radiator server from the 220.127.116.11 ... but no response from Radiator
setting Trace to 4, i can see in logfile:
*** Received from 18.104.22.168 port 32813 ....
User-Name = "skendric"
User-Password = "[...]"
NAS-Identifier = "foo.fhcrc.org"
Wed Sep 6 09:07:17 2006: WARNING: Could not find a handler for
skendric: request is ignored
-so, why does Radiator think the *client* name is 'skendric'? to my way
of thinking, the client's name is 'foo.fhcrc.org' ... or, at the very
-what am i misunderstanding about how to use Client-Identifiers?
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