On 7. Sep 2018, at 10:24, Fabian Mauchle <fabian.mauchle(a)switch.ch> wrote: Hi Gopa, On 06.09.18, 17:44, "Gopa Kumar" <gopakumar.77(a)gmail.com> wrote: We have implemented RADSECPROXY for one of our customers as proof of concept. At feature level everything is looking fine. But currently we are seeing several issues on scaling. Do you have any tools that can be recommended for scale/performance testing of RADSEC. I always found performance testing of radius hard. Best thing I've done so far is use eapol_test and start lots of processes in parallel. But still this does not reflect any real distribution of realms and such. And it also doesn't cover any packet loss or slow home server situations. There is currently one known limitation: there can be at most 255 outstanding requests on a configured server; additional requests to that server will be dropped. (this is being worked on) If you see other issues, please describe them in more detail. Please make sure to use the latest version of radsecproxy (1.7.2). Best regards, Fabian -- SWITCH Fabian Mauchle, Network Engineer Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland Phone +41 44 268 15 30, direct +41 44 268 15 39 fabian.mauchle(a)switch.ch, http://www.switch.ch _______________________________________________ radsecproxy mailing list radsecproxy(a)lists.nordu.net https://lists.nordu.net/listinfo/radsecproxy