Multiple incoming requests from unknown clients

[Diego Matute]

Klaus,

Yes I did mean the server sending the request, not the supplicant. I
misunderstood how to handle adding additional user stores off the same
RADIUS server. I will be requiring the IP of the connecting service.

On Tue, Aug 14, 2012 at 5:43 PM, Klaus Klein <k.klein at gmx.de> wrote:

> Hi Diego,
>
> Am 14.08.2012 16:06, schrieb Diego Matute:
>
>  I could use NAS, but that would require the client to declare their IP
>> address.
>>
> From a FreeRADIUS server point of view the NAS is the _client_!
> Could it be that you meant the supplicant (the user or machine which wants
> to be authenticated) when youwrite "client"?
>
> Am 14.08.2012 00:40, schrieb Diego Matute:
>
>  What is the best practice for handling incoming requests which require
>> different policies (i.e. secret keys) whereby the client IP is unknown?
>>
> Pls. clarify "the client IP is unknown".
> Is this the IP of the NAS which sends an authentication request to the
> FreeRADIUS server ?
> Do you mean that you don't know through which configured NAS the
> authentication will take place?
> Do you refer to the IP of a supplicant?
>
> Cheers,
> Klaus
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/**
> list/users.html <http://www.freeradius.org/list/users.html>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20120814/e1464b08/attachment.html>