Thanks for the prompt responses, Alan.
I have a one follow up question before I head off and start poking
through code, doxygen and writing some code.
Vinit Karandikar wrote:
So if I could run 10 copies of radclient in one process (each in a
different thread for example), I can write code to co-ordinate what each
thread should do for each test case.
The server comes with a RADIUS API. You can use the API to create an
application that sends and receives RADIUS packets.
Aha ! Where can I find information on this API for what you correctly
described as "very custom" development that I'm looking to do ?
Hope this illustrates the functionality I mentioned as desired in my
original email.
In BOTH cases, the AAA server is expected to forward RADIUS requests to
a different network element and it behooves a test application to see
both ends.
What you're describing is a RADIUS simulator for a specific test
environment. That doesn't exist. It is a *very* custom piece of software.
FreeRADIUS can do a lot of this, but you will still need to write all
of the custom rules for processing, timing, etc.
The point once again is just to ask if
a) there is already a tool that can simulate multiple network elements
and co-ordinate between them to know when to expect a packet and when to
initiate traffic
... for your specific environment, and your specific test cases.
The answer to that is "no".
Alan DeKok.
------------------------------
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
