Any suggestions on load tests to assess the Radius server reliability
and the 802.1x authentication process?
We have a freeRadius/PEAP-MSCHAP-v2 set up.
Was wondering if there are any tried and tested methods to build a
reliability study before rolling out the service as production.
Thanks
I'm not sure if you can afford it, but I believe that Spirent has a load
tester for such a scenario:
http://www.spirentcom.com/documents/3768.pdf
Frank
-Original Message-
From: Archana Vemulapalli [mailto:[EMAIL PROTECTED]
Sent: Monday, March 27, 2006 9:19 AM
To:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 17:24 -0700 03/24/2006, Chris Hessing wrote:
A bit more info on the MacBook issue. The chipset that is used in the
MacBooks is an Atheros a/b/g chipset.
Can you actually make the MacBook Pro connect to an 802.11a network?
-BEGIN PGP
We are using Cisco 1240 series AP's. I seem to
remember
an instructor for Terrawave saying that when clustering AP's
for user density to space them approximately 3 ft a part.
I don't remember if the recommendation applied to 802.11G
or to 802.11A. Does anyone remember any such
When co-locating APs for user density/capacity, they should be on
non-overlapping channels (1/6/11 for 802.11b/g) and should be spaced
some distance (3 feet is a good rule of thumb) apart from one another.
This applies to both 802.11b/g and 802.11a.
The reason you want to do this is to
I did some homegrown load testing against FreeRADIUS using the eapoltest
diagnostic program that comes with wpa_supplicant. You're going to
have a very very hard time getting FreeRADIUS to show a problem with
load even with thousands of clients reauthenticating regularly. The
only time you
