Open Meister1593 opened 2 months ago
Just wanted to chime in to say that I’ve been experiencing an issue to this yesterday when first trying to connect my headset. Despite experimenting with both the stable and nightly build. I tried doing what was suggested here by adding arguments to the firewall, but aside from the recognition of SteamVR addons, I still wasn’t able to maintain a stable connection and remain in a connection error cycle.
For reference, I am running EndeavorOS with the native version of Steam. I used the ALVR launcher obtained from Github to utilize both the current stable and nightly releases of ALVR on both my computer and Quest 3 client.
I have pretty much the exact same setup as @EsteemedScholar, and was able to get it working by temporarily disabling firewalld until reboot: systemctl stop firewalld
Probably not a great solution, but it got it working for me :D
I am experiencing what seems like the same issue on a similar setup (Quest 2, Endeavour, native Steam runtime, ALVR 20.11.1 streamer and client). Disabling firewalld
worked, but so did adding the alvr
service that the setup wizard adds to the public
zone. It seems like previously it was only added/enabled on the home
zone. I'm not sure why it no longer works in that zone only, and needs to be added to the public zone.
For some reason people started to get
broken pipe OS error 32
if their firewall isn't configured properly We need to investigate why exactly this happens (firewall should be handled by setup wizard already?) and maybe explicitly check for that error and say if it's related to firewall, instead of generic os error 32.