(RADIATOR) associating clients with handlers

[Stuart Kendrick]

hi,

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 ####
[...]
<Client 140.107.6.12>
	Secret foozle
	Identifier apc-gear
</Client>


#### Handle APC gear ####
<Handler Client-Identifier=apc-gear>
	RejectHasReason
	AuthByPolicy	ContinueWhileIgnore

	# Handle administrative users
	<AuthBy LSA>
		Domain COMPANY
		Group UPSManagement
		AddToReply Service-Type = "Administrative-User"
	</AuthBy>

	# Log it
	AuthLog mgmt-authlog
	AcctLogFileName		%L/Acct/%Y-%m-%d-acct
</Handler>
[...]

i can see from a packet sniffer the Access-Request packets arriving at 
my Radiator server from the 140.107.6.12 ... but no response from Radiator


setting Trace to 4, i can see in logfile:

*** Received from 140.107.6.12 port 32813 ....
Code:       Access-Request
Identifier: 34
Authentic:  [...]
Attributes:
         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 
least, 140.107.6.12

-what am i misunderstanding about how to use Client-Identifiers?


insights appreciated,

--sk

stuart kendrick
fhcrc

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