Internal vs external proxy server

[Alan DeKok]

On Aug 20, 2019, at 5:53 PM, Artis Caune <artis.caune at gmail.com> wrote:
> 
> On Wed, 21 Aug 2019 at 06:25, Alan DeKok <aland at deployingradius.com> wrote:
> Did not work when added to dialup server post-auth but it worked in parent.
> Internal servers don't print attributes in -X so I used
> "%{debug_attr:reply:}"
> I can see all attributes when dialup replies to parent (radproxy)

 Sure, that's good.

> radproxy is virtual server as well btw:
> server {
>  listen {
>    ...
>    virtual_server = radproxy
>  }
> }
> 
> In radproxy server I could see all attributes with
> "%{debug_attr:proxy-reply:}" within post-proxy and post-auth.

  Yes.

> So I added this to radproxy post-auth and it worked:
> post-auth {
>  update {
>    &reply += &proxy-reply
>  }
> }
> 
> Does it looks good ? Feels like cleaner solution than listening virtual
> servers on localhost.

  Yes, that's good.

> 
> I'm moving multiple radius servers (radiator, freeradius 1.1 and freeradius
> 2.2) to v3.
> Yes v1.1, don't ask!

  Wow.  But it's a testament to the stability of the server.  I've seen people running 7-8 year-old versions, because "it works".

  Alan DeKok.