We are pleased to announce the deployment of the new 802.11a wireless service in EECS. 11a offers a much higher link speed (54mb as opposed to 11mb for 802.11b), less interferences, and the possibility of stronger encryption.

For the first phase, we will deploy a non-encrypted 802.11a service. If you have a 802.11a wireless interface, you should be able to connect to “EECS-11a” SSID (there is no other keys required, but your system has to be registered in the EECS wireless network). The service will now require users to authenticate prior to routing. Once you start your browser (please be sure that javascript is turned on), it should redirect you to the authentication page. Use your EECS LDAP username and password for authentication. The lease will expire after a certain period of inactivity, so one can always reconnect to https://1.1.1.1/login.html to re-authenticate. Please note that you should only accept the certificate for the current session when you use the https://1.1.1.1/login.html to reauthenticate. Do not accept the certificate “forever” or you might encounter problems when you roam around EECS. Due to caching problems with firefox, you might be receiving an error about certificates. Please use another browser to authenticate before using firefox.

We have tested only a limited number of 802.11a devices, so it is possible that your 802.11a network device is not fully supported.

Due to limited staffing, we regret to say that we might not be able to get to your specific device immediately.

We know IBM and Dell laptops with built-in 802.11a work, as well as Avaya 802.11a cards (you must install the driver for this).

If you have problem using 802.11a, please let us know what kind of configuration you have. 802.11b service remains your best alternative.

EECS guest wireless will stay on 802.11b.