Bug 358440 - Should be aware of firewalls
Summary: Should be aware of firewalls
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kdeconnect (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
: 398892 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-01-23 18:37 UTC by Daniel
Modified: 2020-03-10 20:19 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel 2016-01-23 18:37:20 UTC
Fedora has FirewallD enabled by default. There should be an indicator in the KDE Connect system settings module when a firewall is blocking  incoming connections to the ports used by Kde Connect Will help new users adopt the program.
Comment 1 Albert Vaca Cintora 2016-01-23 19:28:38 UTC
In that case it would be great if you can ask the Fedora packagers to add a script to allow kdeconnect on the firewall when it is installed. Could you contact them?
Comment 2 Daniel 2016-01-23 22:57:24 UTC
The Fedora package ships with a FirewallD profile that can be turned on through the GUI client or `firewall-cmd --add-service kde-connect`. However, it’s so unlikely that they will enable more services by default that I wouldn’t even ask. The default policy for Fedora Workstation and KDE spins only include dhcp, mdns, and samba-client. All other services must be added by the users themselves and I’m not aware of any packages that enable themselves (including apache and smtp servers).

Which in short brings me back to the generic solution of: detect when ports are blocked by any kind of firewall and display a warning in the UI used to discover and pair devices.
Comment 3 Rex Dieter 2016-09-13 14:04:00 UTC
marking confirmed wishlist
Comment 4 Aleix Pol 2018-01-16 22:55:44 UTC
What's the status of this? Is KDE Connect usable in Fedora/Red Hat?
Comment 5 Rex Dieter 2018-01-17 17:42:12 UTC
fedora's kdeconnect packaging includes a firewalld definition/profile for ports used (per comment #2), and installs it as

/usr/lib/firewalld/services/kde-connect.xml

It's contents are:
<service>
<short>KDE Connect</short>
<description>
KDE Connect allows intercommunicating with mobile devices to receive messages and notifications.
</description>
<port protocol="tcp" port="1714-1764"/>
<port protocol="udp" port="1714-1764"/>
</service>

This allows users to use firewalld UI's (like firewall-config) to easily allow this communication if they wish (by opting-in to allow it).

It cannot be enabled automatically or by default (by policy)


As this wishlist is stated, I'm not sure kde-connect itself can tell whether it's communications are being blocked by a firewall (like firewalld).


As an aside, I've also lobbied fedora's kde-sig to use 'Fedora Workstation' firewall zone by default (which would allow this out of the box), but that proposal was rejected.
Comment 6 Aleix Pol 2018-01-18 03:25:24 UTC
Would it make sense to have the file installed by kde connect instead of it being a patch by the distribution?
Comment 7 Nicolas Fella 2018-09-27 14:30:47 UTC
*** Bug 398892 has been marked as a duplicate of this bug. ***