Internal vs external proxy server

Artis Caune artis.caune at gmail.com
Tue Aug 20 23:53:58 CEST 2019


On Wed, 21 Aug 2019 at 06:25, Alan DeKok <aland at deployingradius.com> wrote:

>   add:
>
>         update {
>                 &outer.reply += &reply
>         }
>
>   And it will copy the reply over to the parent.
>

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)

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.

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.


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





>   We're not going to "fix" this in v3, unfortunately.  People rely on the
> existing behaviour, and we can't really change that.
>

Sounds good, looking forward to v4


More information about the Freeradius-Users mailing list