Richard Shaw wrote: > On Tue, Feb 23, 2016 at 7:31 AM, Timothy Murphy <gayleard@xxxxxxxxxx> > wrote: > >> I see that I have to open ports 1714-1764, TCP and UDP. >> I'm running firewalld on the laptop. >> I give the command "firewall-config" and authenticate. >> Clicking on zone "internal" I see that kde-connect is ticked. >> And when I go to Ports I see that ports 1714-1764 are listed, TCP and >> UDP. And all this remains set if I reboot. > Let's try the simple stuff first... Is your default zone for your network > connection also "internal"? Thank you very much. That was indeed the issue. After changing the default zone to "internal" everything works fine. But I don't understand the reasoning behind this. This use of the term "zone" seems to me misleading and bizarre. I run shorewall on my home server, and there the "zone" can be "net", "local", etc. Any changes made to a particular zone come into effect on restarting shorewall. It would not make sense in this context to choose a "default zone". Incidentally, restarting firewalld does not seem to me to work properly, as a window comes up asking for authentication. I don't recall any other service requiring this, and it would seem to prevent remote restarting. -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
