RE: (RADIATOR) which attribute?
if i wanted to use ClientListSQL, how would I do this? thanks, shon -Original Message- From: Hugh Irvine [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 7:27 PM To: Shon Stephens; '[EMAIL PROTECTED]' Subject: Re: (RADIATOR) which attribute? Hello Shon - You would do something like this: Client .. Identifier Carrier1 . /Client Client .. Identifier Carrier1 . /Client Client .. Identifier Carrier2 . /Client Client .. Identifier Carrier3 . /Client ... Handler Client-Identifier = Carrier1 .. /Handler Handler Client-Identifier = Carrier2 .. /Handler Handler Client-Identifier = Carrier3 .. /Handler If you have any other questions, please ask. regards Hugh 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. thanks, shon === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' 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 [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) which attribute?
Hello Shon - You should use a GetClientQuery in your ClientListSQL clause. This is explained in section 6.6.2 in the Radiator 3.1 manual. (doc/ref.html). regards Hugh On Wed, 10 Jul 2002 01:32, Shon Stephens wrote: if i wanted to use ClientListSQL, how would I do this? thanks, shon -Original Message- From: Hugh Irvine [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 7:27 PM To: Shon Stephens; '[EMAIL PROTECTED]' Subject: Re: (RADIATOR) which attribute? Hello Shon - You would do something like this: Client .. Identifier Carrier1 . /Client Client .. Identifier Carrier1 . /Client Client .. Identifier Carrier2 . /Client Client .. Identifier Carrier3 . /Client ... Handler Client-Identifier = Carrier1 .. /Handler Handler Client-Identifier = Carrier2 .. /Handler Handler Client-Identifier = Carrier3 .. /Handler If you have any other questions, please ask. regards Hugh 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. thanks, shon === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' 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 [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) which attribute?
Hello Shon - You would do something like this: Client .. Identifier Carrier1 . /Client Client .. Identifier Carrier1 . /Client Client .. Identifier Carrier2 . /Client Client .. Identifier Carrier3 . /Client ... Handler Client-Identifier = Carrier1 .. /Handler Handler Client-Identifier = Carrier2 .. /Handler Handler Client-Identifier = Carrier3 .. /Handler If you have any other questions, please ask. regards Hugh 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. thanks, shon === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' 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 [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
