https://bugs.kde.org/show_bug.cgi?id=440688
MikeC <mike.cloa...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOT A BUG
Status|REPORTED |RESOLVED
--- Comment #1 from MikeC <mike.cloa...@gmail.com> ---
I have found the solution to this issue. The problem was that the nftables
firewall did not flush the firewall rules when the nftables service was
stopped. A recent change to nft meant that previous behaviour that stopping
the nftables service would flush the ruleset was changed, and it is now
necessary to manually flush the ruleset after stopping the firewall. Once the
nft rules are flushed kdeconnect works perfectly.
Additionally when I added the port range 1714-1764 to the nftables rules for
udp and tcp, and restarted the nftables firewall kdeconnect continues to work
perfectly with the firewall running.
So I will close this bug now.
--
You are receiving this mail because:
You are watching all bug changes.
