Defining clients in virtual servers
Is there any way to get one virtual server or the default server to proxy requests to a virtual server using proxy-to-realm without having the client configured globally in clients.conf or equivalent, but only in the virtual server. Or have the client defined globally but have the radius key overridden by the client specified in the virtual server config. So I have one virtual server listening on a specific IP and port, which looks at the nas ID and proxies to a realm correlated with that nas id. Essentially what I'm trying to achieve is to have clients with a dynamic (unknown) IP address, but different radius keys depending on the realm identified in the nas id.
On Apr 24, 2017, at 3:01 PM, Clayton Knorr <clayton.knorr@nuspire.com> wrote:
Is there any way to get one virtual server or the default server to proxy requests to a virtual server using proxy-to-realm without having the client configured globally in clients.conf or equivalent, but only in the virtual server.
No.
Or have the client defined globally but have the radius key overridden by the client specified in the virtual server config.
No.
So I have one virtual server listening on a specific IP and port, which looks at the nas ID and proxies to a realm correlated with that nas id.
Essentially what I'm trying to achieve is to have clients with a dynamic (unknown) IP address, but different radius keys depending on the realm identified in the nas id.
That isn't supported in v3. We're re-architecting the code so that this will work by design in v4. Alan DeKok.
Thanks for the response! If you give me an idea what direction to go to make this happen in 4.0 we might try being guinea pigs. -----Original Message----- From: Freeradius-Users [mailto:freeradius-users-bounces+clayton.knorr=nuspire.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Monday, April 24, 2017 3:19 PM To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: Defining clients in virtual servers On Apr 24, 2017, at 3:01 PM, Clayton Knorr <clayton.knorr@nuspire.com> wrote:
Is there any way to get one virtual server or the default server to proxy requests to a virtual server using proxy-to-realm without having the client configured globally in clients.conf or equivalent, but only in the virtual server.
No.
Or have the client defined globally but have the radius key overridden by the client specified in the virtual server config.
No.
So I have one virtual server listening on a specific IP and port, which looks at the nas ID and proxies to a realm correlated with that nas id.
Essentially what I'm trying to achieve is to have clients with a dynamic (unknown) IP address, but different radius keys depending on the realm identified in the nas id.
That isn't supported in v3. We're re-architecting the code so that this will work by design in v4. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Apr 24, 2017, at 5:08 PM, Clayton Knorr <clayton.knorr@nuspire.com> wrote:
Thanks for the response!
If you give me an idea what direction to go to make this happen in 4.0 we might try being guinea pigs.
This feature isn't supported yet, it's part of the next wave of re-architecture which should happen soon. -Arran Arran Cudbard-Bell FreeRADIUS Core Developer FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Is there any specific target date for the next wave? -----Original Message----- From: Freeradius-Users [mailto:freeradius-users-bounces+clayton.knorr=nuspire.com@lists.freeradius.org] On Behalf Of Arran Cudbard-Bell Sent: Monday, April 24, 2017 5:12 PM To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: Defining clients in virtual servers
On Apr 24, 2017, at 5:08 PM, Clayton Knorr <clayton.knorr@nuspire.com> wrote:
Thanks for the response!
If you give me an idea what direction to go to make this happen in 4.0 we might try being guinea pigs.
This feature isn't supported yet, it's part of the next wave of re-architecture which should happen soon. -Arran Arran Cudbard-Bell FreeRADIUS Core Developer FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
On Apr 25, 2017, at 9:28 AM, Clayton Knorr <clayton.knorr@nuspire.com> wrote:
Is there any specific target date for the next wave?
No, it's one of those it's done when it's done things. v4.0.x is a pretty fundamental re-architecture of how FreeRADIUS internals work. It touches everything from the event loops to attribute name/number-spacing. -Arran
participants (3)
-
Alan DeKok -
Arran Cudbard-Bell -
Clayton Knorr