Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

firewalld prevents the use of GNOME Public folder #41

Closed
A6GibKm opened this issue Apr 10, 2020 · 4 comments
Closed

firewalld prevents the use of GNOME Public folder #41

A6GibKm opened this issue Apr 10, 2020 · 4 comments

Comments

@A6GibKm
Copy link

A6GibKm commented Apr 10, 2020

When I try to access my public files on another machine on my network using nautilus I get HTTP Error could not connect: No route to host. Disabling firewalld.service fixes it, but it is not desirable.
@A6GibKm
Copy link
Author

A6GibKm commented Apr 10, 2020 •
edited

update: firewall-cmd --set-default-zone=FedoraWorkstation solves it. Why this is not the default zone?

Also note that this worked in f31.

@tpopela
Copy link
Contributor

tpopela commented Apr 14, 2020

Thank you @A6GibKm for the bug report! It's a fallout after we moved from using the fedora-release-workstation to fedora-release-silverblue. Opened https://src.fedoraproject.org/rpms/firewalld/pull-request/5 (for F32) and https://src.fedoraproject.org/rpms/firewalld/pull-request/4 (for Rawhide)

@tpopela tpopela closed this as completed Apr 14, 2020
@A6GibKm
Copy link
Author

A6GibKm commented Apr 14, 2020

Thanks!

@A6GibKm
Copy link
Author

A6GibKm commented Apr 14, 2020

By any chance, could this also affect IoT edition? I remember having an issues where firewalld didn't allow to run a pihole or mount a http server for my local network.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tpopela @A6GibKm