Connecting Quest 3 to Eduroam

I had some issues connecting the Quest 3 to EduRoam, so i went googling and found this explanation which worked well for me:

tiborudvari.com/blog/connect-meta-quest-to-eduroam

1 like

Thanks a lot for the link! I managed to connect to eduroam in the past, but forgot the steps by now.

By the way, since eduroam is a bit limited (and needs a personal account), are you looking into using iotroam at BUAS?

1 like

Yeah, I had some issues as well, and most online sources didn’t help me either.

I know we have an iotroam, but I dont know about the current state of this network. Thank you for the tip, ill contact our tech support for this.

Our experiences with iotroam have been disappointing. For basic access to a network it’s fine, but iotroam blocks network traffic on most other ports. This severely limits its use in cases where a VR application needs to communicate to a remote server (like we do in most of our applications). Iotroam doesn’t even allow SSH access if both client and server are connected to it.

1 like

Well, iotroam is actually just an authentication layer, that controls who/what can access a particular network infrastructure, including optionally mapping devices to VLANs. By itself it imposes no limitations on network functionality, nor port access.

So any limitations you encounter are in the local UvA network setup, and is not under control of iotroam (or those limitations are implicitly the result of how the local iotroam configuration manages the devices). This decoupling is actually as intended, so that the local network setup can be chosen as needed (fully open, fully closed, somewhere in between), and to comply to any institution’s security policy, regardless of the authentication step.

Edit: some additions

Thanks for that clarification, Paul. In that case: Your Mileage May Vary! :grinning:
I would definitely like to hear about experiences from people at other organisations (if only to wave a stick at my ICT department…).