<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 9 Oct 2013, at 10:16, Fajar A. Nugraha <<a href="mailto:list@fajar.net">list@fajar.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">On Wed, Oct 9, 2013 at 3:41 PM, Alex Sharaz <span dir="ltr"><<a href="mailto:alex.sharaz@york.ac.uk" target="_blank">alex.sharaz@york.ac.uk</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">While we have 900 switches doing mac and 802.1x based auth, we can have 6000+ users on our wireless network all authenticating to RADIUS via 3 RAS clients. Looking at the back end server log files, it does look as if, in general, all wireless RADIUS auths head for the same back end server.<br>
<br>
I was wondering if there's a way off having a bit more granularity in terms of how the f5 load balances incoming RADIUS requests.<br>
<br></blockquote><div><br></div><div>Have you asked F5?</div><div><br></div><div>At the very least, common load balancers (e.g. "keepalived" on linux, a frontend for ipvs) should have the option of distributing traffic to backends based on source IP. Since you say you have 3 RAS clients, it should work somewhat.</div>
<div><br></div></div></div></div></blockquote>You had a nose round the f5 site and subscribed to some of the communities. Shall we say that the response wasn't that great!</div><div>A</div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>-- </div><div>Fajar</div></div></div></div>
-<br>List info/subscribe/unsubscribe? See <a href="http://www.freeradius.org/list/users.html">http://www.freeradius.org/list/users.html</a></blockquote></div><br></body></html>