<html>
<head>
<style>
.sw_message P{margin:0px;padding:0px;}
.sw_message {FONT-SIZE: 12pt;FONT-FAMILY:Tahoma,Arial,Helvetica,sans-serif;background:white;}
.sw_message blockquote{margin-left:5px;padding-left:5px;border-left:2px solid #144fae;color: #144fae;}
.sw_message blockquote blockquote{border-left:2px solid #006312;color: #006312;}
.sw_message blockquote blockquote blockquote{border-left:2px solid #8e5656;color: #8e5656;}
.sw_message blockquote blockquote blockquote blockquote{border-left:2px solid #888;color: #888;}
</style>
</head>
<body class="sw_message">
<div>OK I now have part one of this done - radacct now holds the LNS IP address thank you.</div><div><br></div><div>I just want to clarify one small thing if I may ...</div><div><br></div><div>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 ?</div><div><br></div><div>Or have I again got this totally wrong ?</div><div><br></div><div>Thanks in advance I do appreciate your help</div><div> </div><div id="editor_signature"><div>-- </div><div>Richard Palmer | Director | Merula Limited</div><div><i>Company Registered in England and Wales No. 3243995</i></div><div>5 Avro Court, Huntingdon, Cambridgeshire, PE29 6XS</div><div>Phone 01480 222940 | Support 0845 330 0666</div><div>Support Email support@merula.net</div><br></div><div> </div><blockquote type="cite">--- Original message --- <br><b>Subject:</b> Re: coa / proxy question <br><b>From:</b> Alan DeKok <aland@deployingradius.com> <br><b>To:</b> FreeRadius users mailing list <freeradius-users@lists.freeradius.org> <br><b>Date:</b> Monday, 06/01/2014 3:29 PM<br><br>Richard J Palmer wrote:<br><blockquote type="cite"> What I would ideally like to do (simple solution) is send the coa<br> request to both LNS routers - one will obviously say 'no match' the<br> other will correctly affect the session. With the pool set to failover I<br> find that second LNS is not sent the coa as the first LNS replied<br> (albeit saying no match), load balance works 50/50.<br></blockquote><br> That's a terrible solution.<br><br><blockquote type="cite"> Is there a simple way to configure coa to send the request to both here.<br></blockquote><br> No. Packets go to ONE destination, and ONLY one destination.<br><br><blockquote type="cite"> I'm also open to any betrter routes to do this<br></blockquote><br> Add a column to the accounting table. It should be "LNS IP Address".<br> Then, update the accounting queries to store Packet-Src-IP-Address there.<br><br> For CoA, you just look up the session in the accounting table, and<br>sent the CoA packet to the LNS IP Address.<br><br> Alan DeKok.<br>-<br>List info/subscribe/unsubscribe? See <a target="_blank" href="http://www.freeradius.org/list/users.html">http://www.freeradius.org/list/users.html</a><br></blockquote><br>
</body></html>