eduroam (education roaming) is an encrypted, world wide roaming access service developed for the international research and education community. eduroam allows students, faculty, and staff from participating institutions to obtain wireless connectivity when visiting other participating institutions by simply opening their device. This makes connecting to the Internet easy and convenient for conferences, research, or other reasons.

Any member of the UCSB community with a valid UCSBnetID and current affiliation can use eduroam. They can also connect to participating institutions' wireless network service as long as they configure eduroam on their device(s).

Your account must have a current Academic Affiliate, Contractor, Employee, Extension, Pre-hire or Student affiliation type. Your account name must be entered in the form Logins will fail if "" is not included. Use your UCSBnetID password. Note: This might not be your actual email address. Do not change it to match your email address.

IMPORTANT: When planning to use eduroam at other participating institutions, we strongly recommend that you configure your device(s) while on the UCSB campus before you leave.

You must leave “” after your UCSBnetID. Appending is necessary to connect to the eduroam network both on and off campus. Note: This might not be your actual email address. Do not change it to match your email address.

Check the eduroam website for participating institutions in the US.

We strongly recommend that you configure your device for eduroam while on the UCSB campus before you leave. Once you are at a participating campus, all you have to do is turn on your device and it will connect automatically!

For general eduroam questions, contact the UCSB Network Operations Center (NOC) at while you are still on campus. We will not be able to provide assistance once you are away. The NOC does not provide device configuration and does not provide support for eduroam for visitors from other institutions.

Make sure you use Your_UCSBnetID@ucsb.edufor your username when configuring. Note: You must use (which might not be your actual email address) for eduroam to connect on and off campus. The IT Help Center at other institutions likely will not be able to help you troubleshoot your connection.

As long as your UCSBnetID remains active and you have a current affiliation, you can continue to connect to eduroam. Valid current affiliation types are Academic Affiliate, Contractor, Employee, Extension, Pre-hire, or Student. Graduates do not have one of these affiliation types unless they have made specific arrangements with a sponsoring academic department for an Academic Affiliate affiliation type.

Please see the eduroam website for news updates, and other relevant information.



This section describes basic account information.


You can verify your UCSBnetID password on the UCSBnetID Diagnostics page. This is also where you can make sure your account has a valid affiliation which is eligible for wireless service.

Each UCSBnetID account may have one or more "affiliations", which indicate the relationship between the account holder and UCSB. For example, a current student would have a "student" affiliation. The affiliation information is automatically updated as people join and leave the campus.

Affiliations eligible for wireless service include:

  • Academic Affiliate
  • Contractor
  • Employee
  • Extension
  • Pre-hire
  • Student

You can verify your UCSBnetID password and check your current affiliation information on the UCSBnetID Diagnostics page.

The UCSBnetID is an account in the campus Identity system. Most students would recognize it as the account name used to access UMail or GOLD. Faculty use a UCSBnetID to submit grades via eGrades.

Faculty, staff and students can create a UCSBnetID or change the password for their existing UCSBnetID by visiting the Identity Manager page.


Client Configuration

This section addresses various questions regarding client configuration installation, management and support.

Reference the eduroam settings to manually configure a device for the eduroam network.

Reference the UCSB Secure Settings to manually configure a device for the UCSB Secure network.


No special software is required to use the UCSB Wireless Web network, only a standard web browser is needed during the login process.

The eduroam network may require additional software. Some devices will not require any software installation, others will need to run a temporary program during configuration, and others may need to leave a program on the device for continued network access.

Android devices require the Cloudpath client application to complete the automatic setup process, but Cloudpath is not required if you choose to manually configure your Android device. Other operating systems may use Java during the setup process. Windows-based devices may need to download a configuration program if the Java-based configuration program is unable to run.

There are two pieces to remove, the configuration and the Cloudpath application.

  1. Remove the network from your WiF-Fi settings
    1. Go to Settings->Wi-Fi, then tap and hold the wireless network name (e.g. eduroam) and select "Forget network".
  2. Remove the Cloudpath application
    1. Go to Settings->Applications->All and tap on the Cloudpath application, then select "Uninstall."

Go to Settings->General->Profile and select the "UCSB Secure" profile, then select "Remove".

MacOS (e.g. MacBook)
Go to System Preferences->Profiles and select the "UCSB Secure" profile, then select the "-" (minus sign) in the lower left corner of the Profiles window to remove the profile.

Students may contact the Collaborate Student Support Center for assistance with device configuration.

Faculty and Staff
Faculty and staff should contact their department's IT support staff to inquire if they can assist you. Please note that personally-owned devices (i.e. those not owned by UCSB) are often not supported by departmental IT staff.

Other issues
If you suspect a problem with a wireless access point, your wireless account information or other issues, please contact us for further assistance.

To help automate configuration of groups of settings — like those needed for a wireless network — Apple came up with a system where the necessary information could be placed in a "mobileconfig" file. This file could be loaded on an Apple device and thus greatly simplify the configuration process.

When the built-in Safari browser is presented with a mobileconfig file, the browser will pass the file to the System Preferences management process. The System Preferences management process will do things like prompting the user for approval of the new settings, gather necessary username and password information, etc., and then add the settings to the system. Unfortunately, Apple reportedly does not provide information to developers of other browsers, such as Chrome, which would allow them to also pass mobileconfig files to the System Preferences manager. For this reason we have to use Safari to process Apple's standard mobileconfig files.


Technical Details

This section provides specifications and addresses technical questions, which are more detailed than necessary for most users.


This is a list of all wireless settings used by the eduroam network. The information is not specific to any particular operating system. Not all settings are available or required in all operating systems. This information is provided for those who want to manually configure their wireless device.

SSID: eduroam
Mode: Infrastructure (not ad-hoc)
IPv4 address and DNS settings: Automatic via DHCP
Security Mode: WPA2-Enterprise
Encryption Type: AES
CA certificate: CA certificate: AAA Certificate Services Root (look for AAACertificateServices)
                Also known as Comodo_AAA_Services_root.pem on Linux systems
Connect to these servers OR "Domain":
Outer Authentication: PEAP
Outer (or anonymous) identity:
Inner Authentication: MSCHAPv2
Username (or Inner identity): [Your_UCSBnetID]
Password: [Your password]

PLEASE NOTE: You must include on both the Outer Identity and Inner Identity (Username), otherwise your login request will not be sent to UCSB for processing and your login will fail.

This is a list of all wireless settings used by the UCSB Secure network. The information is not specific to any particular operating system. Not all settings are available or required in all operating systems. This information is provided for those who want to manually configure their wireless device.

Mode: Infrastructure (not ad-hoc)
IPv4 address and DNS settings: Automatic via DHCP
Security Mode: WPA2-Enterprise
Encryption Type: AES
CA certificate: AddTrust External Root (look for addtrustexternalcaroot.crt)
Connect to these servers:
Outer Authentication: PEAP
Outer (or anonymous) identity: anonymous
Inner Authentication: MSCHAPv2
Username (or Inner identity): [Your UCSBnetID]
Password: [Your password]

Some campus services limit or permit access to wireless clients. Clients of the wireless networks may be assigned IP addresses in the subnets listed below.

  • (Campus wireless users)
  • (Campus wireless users)
  • (Campus wireless users)
  • (Campus wireless users)
  • (Campus wireless users)
  • (Campus wireless users)

WPA2-Enterprise is a set of technical specifications created by a group known as the Wi-Fi Alliance in order to standardize authentication protocols between wireless clients and enterprise wireless access points. In simpler terms, it's an attempt to take what people like about their home wireless access and improve it for large campus and corporate environments ("enterprise" environments).

One of the biggest differences between a home access point and a campus access point is the campus access point must serve many more people. A home access point typically has one password (often known as WPA2-PSK, or Pre-Shared Key) to restrict access to a few people, but this kind of shared password system does not work in a large environment. Instead, the campus access points must be able to authenticate access based on each user's individual password.

One additional improvement is that WPA2-Enterprise can support per-user encryption between the user's device and the access point. A home access point using WPA2-PSK allows each person with the password to see some of the traffic of the other users.

The WPA2-Enterprise specifications include several kinds of authentication processes. UCSB has selected PEAP-MSCHAPv2 because it is commonly available on client devices and has good protection for passwords during the authentication process.

Operating systems known to support WPA2-Enterprise include:

  • Android 2.1 or newer
  • Apple MacOS 10.4 or newer
  • Apple iPad and iPhone
  • Windows XP with Service Pack 3 or later
  • Window Vista or newer (including Windows 10)

Whether a particular operating system will work on the wireless network depends in part upon the capabilities of the wireless network card. Sometimes an update of the wireless card's software (or driver) can help.

Many Linux-based systems support WPA2-Enterprise, though installation of optional software may be required.



Even while using the best wireless networks, problems will occur. This is particularly true when there are many people with lots of client devices. The following items should help resolve some of the more common issues.


There are several reasons why you might be unable to reach the UCSB Wireless Web login page. Check the following items to avoid the most common problems.

Make sure you've selected the UCSB Wireless Web network
Sometimes people accidentally select the wrong wireless network, so double-check the wireless network name.
Visit a regular HTTP web site, not an encrypted HTTPS site
Web site addresses look like and usually start with "http". Some web site addresses start with "https", which means encryption is being used while communicating with the site. These HTTPS addresses can't be captured and redirected to the login page. Solution: Use HTTP by visiting a site like ""
Use the DNS servers provided by DHCP, do not use custom DNS servers
Computers use DHCP to get information needed to join a network, including a list of DNS servers. If your device has been configured to use a specific list of DNS servers, remove these servers and accept the servers provided by DHCP. The UCSB Wireless Web network uses DNS servers at and

If you use Windows and join the eduroam or UCSB Secure network for the first time, the connection may fail with a "Windows Security Alert". The message will likely say, "The Credentials provided by the server could not be validated." This is due to Windows not recognizing digital certificates used to help protect the login process. The automatic configuration utility on this site solves this problem by adding the certificate directly on your windows computer.

There are several reasons a device which previously worked on UCSB Secure may no longer work.

  • Your password has changed, but your device's configuration was not updated with the new password.
  • Your account was administratively disabled.
  • You have reached the maximum number of concurrent authenticated devices.


Wireless Coverage

Wireless isn't helpful if it's not available in your area. Issues regarding coverage are discussed below.


Wireless service is provided at the locations in the coverage list shown below. Wireless signals are typically available beyond the areas in the coverage list, but these areas may have poor signal strength and unreliable connectivity, and thus are unsupported.

  • Arts bldg.534
  • Arts & Lectures, bldg.402
  • Arts Museum
  • Arts & Music Library
  • The Arbor, including line-of-sight exterior for 300 feet
  • Baseball Facility
  • Biology-III bldg.504
  • Bldg.434 (aka Women's Center) rm.121-125,141A-H,145,147.
  • Broida Lecture Halls 1610,1640
  • Broida Hall, floor1 (hallway 1000, rm.1015,1019,1409,1411,1413,1415,1417,1419)
  • Broida Hall, floor2 (hallway 2000, suite 2015,2233, rm.2014,2207-2209,2409,2411,2415,2419)
  • Broida Hall, floor3 (hallway 3000, suite 3019, rm.3302,3340,3409,3411,3413,3415,3417,3419)
  • Broida Hall, floor4 (hallway 4000, wing 4100, rm.4402,4406,4409,4411,4415,4417,4419)
  • Broida Hall, floor5 (hallway 5000, wing 5100, rm.5207,5223,5233)
  • Broida Hall, floor6 (hallway 6000, wing 6100,6200)
  • Broida Hall, rooftop (West platform 7020, East platform 7330)
  • BREN rm.1414,1424, 4th floor rooms 4016,4023-4033,4204,4205,4320-4344
  • Buchanan Hall
  • Bus Loop (South and East bus stops).
  • Campbell Hall
  • Cheadle Hall, bldg.552 1st floor Lobby, floor2, suite 1117,1317-1325,4125-4129,5203.
  • Chemistry bldg.557 rm.1171,1179.
  • Chicano Studies Center
  • Classrooms bldg.387 (West of Psychology)
  • College of Creative Studies
  • Coral Tree Cafe
  • Counseling and Career Services, bldg.599
  • Court Yard Cafe
  • Courtyard between Noble Hall and LSB
  • Davidson Library
  • Deveroux bldg. 7935, 7945, 7955.
  • EH&S (partial coverage)
  • Elings Hall (CNSI), bldg.266
  • Ellison Hall North rooms 1629,2610,2614,2616,2620,3620-3626
  • Ellison Hall South 1st floor, 3rd floor, 5th floor.
  • Embarcadero Hall (BofA) Building
  • Engineering Sciences Building
  • Engineering-II
  • Ergonomics Laboratory
  • Events Center
  • Faculty Club (temporary unavailable due to bldg renovation)
  • Girvetz Hall (except suite 1205, 1140)
  • Harder Stadium East (locker rooms and Arts suite)
  • Harder Office Bldg (rm.1001,1002,1004,1011-1015,1030,1032-1035,1037-1043,1051-1056)
  • Harder Pressbox
  • Harold Frank Hall
  • Hatlen Theater
  • HSSB wing 1100
  • HSSB Tower (except 4001,403x).
  • HSSB Arcade 1st floor, rm.2251,2252, 3rd floor, rm.4201,4202.
  • ICA Study Center
  • Isla Vista Theatre
  • Isla Vista Clinic (2nd floor)
  • Kerr Hall (suite 1110, IC Lab in 2160)
  • KCSB (Storke Publications)
  • KCSB in bldg.434 (Women's Center, rooms 0141A-H)
  • LSB bldg.235 rm.1001,1101.
  • Marine Science Bldg.520 (except 14xx, 4th floor NW)
  • Marine Science/Bio Tech Seawater Lab Bldg.555 rm.1010
  • Materials Research Lab
  • Military Science Bldg.451
  • Mosher Alumni House Bldg.517
  • Music Bldg.531 (0300,1200,1300,2200,2300 wing, LLCH rm.1313, rm.1145, rm.1101-1113,1125-1141 and adjacent Music Bowl courtyard)
  • North Hall (wing 1000,2000,3000,2100,rm.1115,rm.1110 and adjacent courtyard)
  • Old Gym East wing (bldg.479)
  • OSEB West wing (bldg.514)
  • Phelps (floor 2,6, wing 1300,1500,3500, rm.1160,1260,1401-1425,4312,5309-5316)
  • Physical Sciences North Bldg.657 (Rooms 2619,4670)
  • Physical Sciences South Bldg.672 (2nd floor)
  • Pollock Theater
  • Psychology Expansion (bldg.251 and courtyard)
  • Psychology (rm.1319,1902,1924)
  • Public Safety bldg.574 East wing.
  • Recreation Center (East wing offices, Main Gym 1030,1031,1041)
  • Recreation Center Pavilion Gym.
  • Recreation Center Expansion MAC (except locker rooms)
  • Robertson Gym (rm.1125,1131,1133, wings 1000A-1000B Orfalea Center, Audit Offices)
  • SAASB, courtyard, suites 1101, 1102, 1103 (except 1103B-1103F), 2103, 2201, 4th floor.
  • South Hall, 1st floor (rm.1623,1710-1714)
  • South Hall, 2nd floor (English Department)
  • South Hall, 3rd floor (rm.3501-3506,3519,3605,3607,3617,3635,3709)
  • South Hall, 4th floor (rm.4631)
  • South Hall, 5th floor (suite 5607, rm.5617,5631,5635,5701-5708)
  • South Hall, 6th floor
  • South Hall, Grad Tower
  • SSMS (bldg.276).
  • Student Health (including Patio area West of Bldg).
  • Student Resource Building
  • Surge-II (Bldg.570)
  • Theater and Dance.
  • Theater and Dance courtyard.
  • TB-Sycamore (Building 489)
  • TB-Tutorial Center (Building 477, west wing)
  • Trailers 698,384,699,697 and 380 (except rm.101C).
  • Trailers 378,379 (Communications Services).*
  • Trailers 935,936 (ECI,CS).*
  • Trailers 942,939,937 (West of Broida Halls).
  • University Center.
  • Visitor's Center (SAASB, suite 1102).
  • Webb Hall (rm.1015,1025,1030,1100, suite 1006)
  • West Child Care Center

The eduroam network is available wherever UCSB wireless coverage is available. It is also available at other research and educational institutions world-wide. Participating institutions in the United States are available on a map. Information regarding international availability may be found at

Temporary wireless installations are not available since they require equipment and staff resources and do not provide a long-term campus benefit.

Expansion of the campus wireless network has been based solely on funding from departments and other projects or initiatives, such as Collaborate. No central campus funds have been allocated for expanding wireless coverage. Departments seeking expanded coverage may have their information technology support staff contact to request a quote. When requesting a quote, please include specific room numbers to be covered.