Firewall Error (Linux, Bazzite)

[braydenthepope]

I've never done a bug report on github before so sorry if I'm doing things wrong.
Every time i try to add firewall rules on Alvr 20.14.1 or even the nightly build it errors out.
I opened the dashboard in terminal and it says:
Error: INVALID_ZONE: (default)
Error: INVALID_ZONE: (default)
Error: INVALID_ZONE: (default)
Error: INVALID_ZONE: (default)
[14:28:19.503 ERROR alvr_dashboard::data_sources] Setting firewall rules failed!
I'm pretty new to Linux (only have been using it since February) so maybe it's an issue on my end? I'm happy to try and give more info if possible! Thanks!

[GavinFF-SS]

Experiencing the same issue (Fedora 42 with the Hyprland desktop.)

[GriffintheFolf]

Also getting the same issue with Bazzite. Digging deeper into this, it seems the shell script used to set these rules is trying to find the "zones" currently in use. On my system:

$ firewall-cmd --get-active-zones
FedoraWorkstation (default)
  interfaces: enp6s0

However, I think at least part of the problem is that the script, when passing the output of the above command through grep, as in

for zone in $(firewall-cmd --get-active-zones | grep -P '^\w+'); do

it thinks that (default) is also the name of a firewall zone, even though it isn't. Case in point, if I recreate the commands manually:

$ firewall-cmd --zone="FedoraWorkstation" --list-services
alvr dhcpv6-client samba-client ssh
$ firewall-cmd --zone="(default)" --list-services
Error: INVALID_ZONE: (default)

It appears as though it did successfully add exceptions to the firewall (allowing ports 9943 and 9944 over TCP/UDP). But because the script thinks (default) is also a firewall zone, the firewall-cmd command tries to add it to this zone, throws up because it doesn't exist, and then the script returns an error status because it thinks the entire process failed.

[braydenthepope]

Huh, so I guess it must just be a false positive sort of thing then. I figured this was what was causing my issue of having no audio even when ALVR is listed as an audio source, but that must be unrelated..?

[GriffintheFolf]

As an aside, if I ignored the error message and clicked next, it seemed to work anyway. So this is probably more akin to an edge case involving Fedora specifically, and that the script still thinks it didn't work because of this misdetection of two zones rather than one.