eduroam (education roaming) is the secure, world-wide roaming access service developed for the international research and education community. It's used to describe an authenticated access network available in UCD and in Universities worldwide. The service provides extended access to logged-in UCD staff, students and visitors from other institutions.
To find out more view the promotional video.
Go to https://cat.eduroam.org and select download your eduroam installer.
A List of institutions will appear. Select University College Dublin.
Your operating system should be automatically detected. It can also be selected manually by clicking the All platforms link.
When the prompt requests your username, this is your Connect username followed by @ucd.ie . Your password is your Connect password.
For example students will be firstname.lastname@example.org and staff will be email@example.com
It is important to note that the realm"@ucd.ie" is the same for both staff and students.
Note: At present older IOS, Blackberry, Nokia and Windows phones have difficulties accessing the eduroam service.
All usernames will have to contain the home institution’s realm name. Here at UCD our realm is 'ucd.ie'.
When authenticating to eduroam you should use firstname.lastname@example.org where "username" is your UCD Connect username. The realm (the part after the "@") is always "ucd.ie" for both UCD staff and students. The password used should be your UCD Connect password. Any fields labelled "domain" should be left blank
eduroam is can be used in all locations where UCD Wireless is available.
eduroam supports the following network services:
- Client access for all IP protocols except windows filesharing off campus.
- IPSEC and GRE based VPN protocols.
- Inbound access is not permitted (i.e. you may not run a server service).
- Full eduroam roaming is currently permitted.
Using eduroam outside UCD
Test that eduroam works for you in UCD before you leave. If you can't get it working here, you're likely to have problems elsewhere as well.
Search for (and read) any documentation the remote site has on eduroam before you leave. Forewarned is forearmed.
The remote site may use different network encryption to that used in UCD (e.g. WEP vs WPA2). If so, you will need to change that part of your network configuration.
The authentication part of the configuration is specific to the home institution (UCD) so that shouldn't be changed. It includes the EAP methods (EAP-TTLS-PAP), certificates and server verification. Do not change any of those.
Don't forget to include the realm (ucd.ie) when you're authenticating. Usually this just means using email@example.com rather than simply username. Note that whilst this may look like an email address, it isn't. The realm is generally not what clients refer to as a domain. Domains should be left blank.
The technical details of the UCD service are listed below. You may check these with your own IT service provider to ensure compatibility. You may well find that the open access "UCD Wireless" service is adequate to your needs. UCD Wireless is available almost everywhere in all our buildings.
|Media||Wireless LAN IEEE 802.11b/g and a/n|
|SSID||"eduroam". The SSID is broadcast in all available locations.|
|Encryption||802.11i. WPA2/CCMP/AES is supported. WPA/TKIP will be implemented for legacy devices. WEP of any key length is not allowed.|
|Authentication||802.1x. Local (UCD) users will be authenticated using EAP-TTLS-PAP only. Visitors will use an EAP type supported by their home institution.|
|Blocked ports/protocols||All TCP\UDP ports are available for client use. IPSEC VPN clients may be used. Microsoft style VPN clients may also be used. No server services are permitted.|