(RADIATOR) which attribute?
hugh at open.com.au
Mon Jul 8 18:27:00 CDT 2002
Hello Shon -
You would do something like this:
<Handler Client-Identifier = Carrier1>
<Handler Client-Identifier = Carrier2>
<Handler Client-Identifier = Carrier3>
If you have any other questions, please ask.
On Tue, 9 Jul 2002 00:44, Shon Stephens wrote:
> i am working on a wifi project where several carriers proxy their
> radius packets to me. i need to be able to process some of these
> packets differently. unfortunately, every request, no matter what
> carrier it originates from, will have the same realm. i was going to
> (attempt) to write a preprocessing hook and assign a custom attribute
> based on the ip address of the radius server that proxied the
> requests to me, however i am not confident that i can do so. the
> nas-ipaddress attribute in my situation, is the address of the wifi
> access point, and the nas-identifier is a code associated with said
> access point. what attribute would the ip address of the proxying
> radius server be. i know that in my <client> statement i just put the
> address in there, without an attriubute name.
> 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.
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
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