OK I now have part one of this done - radacct now holds the LNS IP address thank you.

I just want to clarify one small thing if I may ...

With the CoA I currently have one CoA server enabled on port 3799 on the radius server. How should I forward the CoA to the LNS ? Do I setup 2 CoA servers either on different ports or IPs within FreeRadius and each send to a different LNS, or Can FreeRadius itself do a SQL query based on the AcctUniqueId and use that to get the IP to forward to ?

Or have I again got this totally wrong ?

Thanks in advance I do appreciate your help

Richard Palmer | Director | Merula Limited

Company Registered in England and Wales No. 3243995

5 Avro Court, Huntingdon, Cambridgeshire, PE29 6XS

Phone 01480 222940 | Support 0845 330 0666

Support Email support@merula.net

--- Original message ---
Subject: Re: coa / proxy question
From: Alan DeKok <aland@deployingradius.com>
To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
Date: Monday, 06/01/2014 3:29 PM

Richard J Palmer wrote:
What I would ideally like to do (simple solution) is send the coa
request to both LNS routers - one will obviously say 'no match' the
other will correctly affect the session. With the pool set to failover I
find that second LNS is not sent the coa as the first LNS replied
(albeit saying no match), load balance works 50/50.

   That's a terrible solution.

Is there a simple way to configure coa to send the request to both here.

   No. Packets go to ONE destination, and ONLY one destination.

I'm also open to any betrter routes to do this

   Add a column to the accounting table. It should be "LNS IP Address".
Then, update the accounting queries to store Packet-Src-IP-Address there.

   For CoA, you just look up the session in the accounting table, and
sent the CoA packet to the LNS IP Address.

   Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html