These notes assume that you already have a working wireless card, which you have tested on some other wireless network.
If your wireless card is not working, try to configure it using 'system-config-network' or some other tool that works on your system, or ask a friend for help. Come back when the card works and has been tested on another more easily accessible wireless network, so that you are sure that you have the right drivers for your wireless card and it has been properly recognised by your operating system.
In addition, please note that some of the helpdesk staff in Information Services are able to help users who wish to use a linux laptop to access the campus wireless service, but they will not physically change settings on user machines. That is the responsibility of users.
However, the Information Services web site now does give advice for linux users, and you should try their instructions, using NetworkManager, before trying mine. See:http://www.wireless.bham.ac.uk/start/configuration/Information about the old service is here
General information about configuration for use of UOBwifihttp://www.helpdesk.bham.ac.uk/laptopsurgery/linux.shtml
DO NOT use the certificate mentioned there for the new service.
The following information was provided by Chris Lea in Information Services on 26 Mar 2010.
He agreed that I could pass it on, after testing the new service.
The campus WIFI certificate is changing because JANET(UK) have changed the certifying authority for their certificate service.
Details here http://www.ja.net/services/scs/
The Globalsign certificates are due to expire this summer so we need to replace with new and get everyone validating authentications against the new certificate.
It has been decided by someone that the best (least painful) approach is to run a new wireless SSID: UOBwifi against the new cert whilst running the current service UOBWLAN to expiration. This will give people time to migrate to the new service before the old one is phased out.
E.g. linux users can fetch it using this command, or something similar:
This can be done in different ways, depending on the system you use.
If you use Fedora or something similar you may find my script and
files for profiling useful. They are available in this package
(Note added 12 Jun 2013: Superseded by new versions of wicd and NetworkManager)
In particular the wpa_supplicant.conf file:
Certificate: DIR /etc/cert/ containing /etc/cert/uob_root_linux.pem Text files specifying the profile (most optional) DIR /etc/uobwifi/ containing /etc/uobwifi/hosts /etc/uobwifi/hosts.allow /etc/uobwifi/hosts.deny /etc/uobwifi/resolv.conf DIR /etc/wpa_supplicant/ containing /etc/wpa_supplicant/uobwifi/ containing (essential) /etc/wpa_supplicant/uobwifi/wpa_supplicant.conf DIR /etc/sysconfig/ containing /etc/sysconfig/uobwifi/ containing (optionally) scripts /etc/sysconfig/uobwifi/firewall /etc/sysconfig/uobwifi/network Essential for telling wpa_supplicant what to do /etc/sysconfig/uobwifi/wpa_supplicant DIR /etc/sysconfig/network-scripts containing /etc/sysconfig/network-scripts/uobwifi/ containing /etc/sysconfig/network-scripts/uobwifi/ifcfg-eth1 and optionally /etc/sysconfig/network-scripts/uobwifi/ifcfg-eth0
Those files are copied into place by the startUOBwifi script, above, which then restarts the network service and wpa_supplicant service, then calls dhclient to obtain a dhcp connection for eth1.
You should make sure that you have previous versions of those files saved for use with other network services or local use.
School of Computer Science
The University of Birmingham