To Whom it may concern, I am looking at how to use cache_eap. https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/mods-avail... However, it disabled in this commit. https://github.com/FreeRADIUS/freeradius-server/commit/875aa768ae457dbc540c7... Is this still not working? James
On Mar 28, 2022, at 2:12 PM, Rouzier, James via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am looking at how to use cache_eap.
Why?
https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/mods-avail...
However, it disabled in this commit.
https://github.com/FreeRADIUS/freeradius-server/commit/875aa768ae457dbc540c7...
Is this still not working?
It doesn't work. On top of that, there's no benefit to caching EAP packets on proxy fail-over. The cost to doing it is large, the benefit is small, and it works only in very very limited situations. Alan DeKok.
Thanks for the reply. Our use case is to be able to run FreeRADIUS behind a “dumb” UDP load balancer that would load balance the RADIUS packets without having to look at the EAP state. We were hoping to leverage the eap cache for that purpose. What limited use cases can caching EAP packets be used for? James On 3/28/22, 2:55 PM, "Alan DeKok" <aland@deployingradius.com> wrote: On Mar 28, 2022, at 2:12 PM, Rouzier, James via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote: > I am looking at how to use cache_eap. Why? > https://urldefense.com/v3/__https://github.com/FreeRADIUS/freeradius-server/... > > However, it disabled in this commit. > > https://urldefense.com/v3/__https://github.com/FreeRADIUS/freeradius-server/... > > Is this still not working? It doesn't work. On top of that, there's no benefit to caching EAP packets on proxy fail-over. The cost to doing it is large, the benefit is small, and it works only in very very limited situations. Alan DeKok. - List info/subscribe/unsubscribe? See https://urldefense.com/v3/__http://www.freeradius.org/list/users.html__;!!Gj...
On Mar 28, 2022, at 3:46 PM, Rouzier, James via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Our use case is to be able to run FreeRADIUS behind a “dumb” UDP load balancer that would load balance the RADIUS packets without having to look at the EAP state.
Don't do that. It won't work. If you want to load-balance RADIUS with EAP, then you need a RADIUS-aware load balancer. What *might* work, *sometimes* is a UDP load balancer which hashes the source IP/port, and load balances based on that. It will work for most situations, but not all. A "dumb" UDP load balancer is one which just sprays input packets randomly across the back-end RADIUS servers. This will not work with EAP. Ever. It's impossible.
We were hoping to leverage the eap cache for that purpose.
It won't help. I have no idea why *caching* EAP will help fix a broken UDP load balancer. It won't.
What limited use cases can caching EAP packets be used for?
It doesn't matter. I've removed the cache_eap module because it doesn't do anything useful. There's no point in explaining why a deleted module won't work for your use-case. Alan DeKok.
participants (2)
-
Alan DeKok -
Rouzier, James