I'm going down the road of issuing my first RFP for wireless replacement for a
set of buildings. My team and I have never issued an RFP before, so we're a
bit unsure about everything that we should include (or shouldn't include) in
the RFP.
Has anyone issued a wireless RFP that wouldn't mind
One of the reasons that I'm holding off is the requirement for Prime
Infrastructure 1.4, which has the warning of PI 1.4 will not be directly
upgradable to one of the major release of the product and might have to wait
for the following major release to be able to upgrade. Since I don't need
There is a recently formed netplus-eduroam-admins listserv created by the
eduroam-US organization to discuss technical problems like this, and it
recently has been having a very similar conversation about required RADIUS
attributes, etc. (See
What does everyone use for Wi-Fi troubleshooting and spectrum analysis? I've
got some localized issues this year in the dorms that were not present in
previous years that I need to get to the root cause of, and am thinking it is
probably interference based. Therefore, I'm looking at
Just as an FYI for those running Cisco, I noticed today that 7.0.235.3 was
released on Sep 11 2012 for both 4400 series and 5508 series controllers. One
of the resolved caveats is bug CSCua29504 which is the Windows 8
802.11w-capable client bug.
Chris Wieringa
On 9/3/2012 at 5:55 AM, Anders
It is possibly to do WPA2-Enterprise with only EAP-MSCHAPv2 authentication, and
this is what would be considered completely vulnerable now. Don't do this
anymore if you are doing it.
AFAIK, if you are using WPA2-Enterprise with PEAP/EAP-MSCHAPv2 you should still
be fine. While you could
It is hard to say exactly why it isn't adding it in without seeing some actual
configuration or server debugging text, but there are a few areas you can
check.
First, make sure that you have the dictionary with that radius attribute
loaded. It should be loaded by default, but it doesn't
We went through the transition when we started buying 802.11n devices. For the
most part, we advertised this change as preparing our network for higher
wireless speeds with 802.11n.
When we cut over to WPA2/AES only on our main SSID we additionally dropped
802.11b support. We were finding
