The University supports two wireless network services, eduroam and the browser-based service (UniOfCam).

The wifi networks connect directly to the University network rather than being considered part of the Institute of Astronomy network which means that access to certain services including printers and Samba may be restricted.

eduroam

If you come from an educational institute that is participating in the international eduroam scheme you will be able to connect immediately to our wireless network without further authentication by selecting the eduroam SSID.

If you are from the IoA and need help setting up your access to eduroam please see the University Computing Service page and if you still have questions send an email to helpdesk.

Browser-based service (UniOfCam)

The University of Cambridge also provides a browser-based service which has the SSID: UniOfCam.

In order to access this service, you need to authenticate by:

• entering your Raven credentials if you are a University of Cambridge user
• entering the details from a temporary access ticket if you are external to the University of Cambridge. For assistance with acquiring a temporary access ticket please contact the IoA receptionist
• The receptionist can also generate batches of tickets that are suitable for conferences and meetings.
• All members of staff including Postdocs can create wireless access tickets for 7 days for visitors at: https://www.wireless.cam.ac.uk/lapwing/tickets.py.
• For urgent requests, when the IOA receptionist is unavailable the IoA computing helpdesk can be contacted.

Before arrival, academic visitors should be advised to register at their home institutes for the international academic wireless network Eduoram.

Requesting temporary access tickets

Reception can provide access tickets for visitors. IoA staff are encouraged to email reception before visitors arrive to ask for temporary wireless access tickets. With ticket requests for a group event we ask the event organiser to maintain a list which tabulates the ticket-id and name of person associated with that ticket (which should be handed into helpdesk). This is for two reasons:

• If a specific ticket gets mislaid by the user, we can rescind that ticket as we will have its id.
• In case of any network abuse we can quickly track down the relevant user.