send an "coa" packet from "authorize {}" section

[Jorge Pereira]

Hi Matthew,

I know that is a nasty hack, but the problems are the "fancy vendors" that
has big and famous appliance completely out of standards. my approach about
this, It replaces the process of my web-portal to send a COA in my default
port 3799 and after a little fix[1] on FreeRadius I can pass/proxy the
packet to the other port (In this case, the appliance listening to acct,coa
and auth in 1812)

It will be possible to override the destination port. This solves my whole
saga! :)

[1] https://github.com/FreeRADIUS/freeradius-server/pull/1299
--
Jorge Pereira

On Mon, Oct 5, 2015 at 5:21 AM, Matthew Newton <mcn4 at leicester.ac.uk> wrote:

> On Sun, Oct 04, 2015 at 04:47:55PM -0300, Jorge Pereira wrote:
> > This sound bad... I will look for some other solution. btw, I believe
>
> Very nasty hack, but you could always exec a script as part of
> authorize that calls radclient to send the coa and wait for a
> response. The script will need to make sure it times out quickly
> if it doens't receive an answer, and exec like this isn't very
> fast so if you've got a lot of auths/s then it'll bog the server
> down, but it should work.
>
> Matthew
>
>
> --
> Matthew Newton, Ph.D. <mcn4 at le.ac.uk>
>
> Systems Specialist, Infrastructure Services,
> I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom
>
> For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>