I have installed the KDE Connect application on my desktop and on my phone [Xiaomi Redmi 3S Prime]. However the desktop application would not detect my phone and vice versa. I have checked the ports. They are open. There is no firewall installed. I have also tried adding my PC manually by entering the IP address in the Android App and that did not work. I also tried restarting the kdeconnectd daemon, but that also didn't work. EDIT: Here are the things that I have tried. 1. Check if the kdeconnectd daemon is running. 2. Check if I have the ports blocked and if firewall is enabled. 3. Check if KDE Connect is listening on the port. Please help with all the solutions you can. PS. It might seem like a duplicate but I have tried almost all the solutions out there but none of it seems to work for me. Hence, I am here.

I was having an issue where KDEConnect peers on my LAN could not see each other intermittently. Because the peers are on APs that are physically connected to and bridged on my main router, I tried changing settings involving hairpin, multicast to unicast, etc, which no real improvement. Fortunately, this answer by [@A.B](https://unix.stackexchange.com/users/251756/a-b ) seems to have solved the issue with bridge family forwarding/routing. https://unix.stackexchange.com/questions/745847/nftables-doesnt-see-kde-connect-packets-between-two-machines-on-the-same-interf Steps 1 and 2 were pretty straightforward for me to implement permanently. However, I would like to convert Step 3 of the answer, which uses nftables, into a permanent solution using firewalld/firewall-cmd instead. The rest of my firewall setup is already defined in firewalld, and I would prefer to keep it all straight in there, and not layer raw nft stuff also. I mostly understand what the nft commands are doing, but not well enough to find their exact corollary in firewall-cmd. I would have asked this in a comment on that other question, but, alas, I need more rep first. So, how can I implement these nft commands in firewalld instead?

table bridge filter {
    chain conntrack {
        ct state vmap { invalid : drop, established : accept, related : accept }
    }

    chain kdeconnect {
        udp dport 1714-1764 counter accept
        tcp dport 1714-1764 counter accept
    }

    chain forward {
        type filter hook forward priority filter; policy drop;
        jump conntrack
        ether type ip6 drop     # just like OP did: drop any IPv6
        icmp type echo-request counter accept
        jump kdeconnect
        ether type arp accept   # mandatory for IPv4 connectivity
        counter
    }
}

Thanks!

This is the Error I get when I try to open my gnome extensions app:

These don't work: sudo update-rc.d kdeconnectd disable sudo systemctl disable kdeconnectd.service There is no script for it in /etc/init.d/ and the /usr/share/dbus-1/services/org.kde.kdeconnect.service file only has Exec=/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd set sysv-rc-conf, rcconf and bum don't list kdeconnect. /etc/xdg/autostart/kdeconnectd.desktop looks like this: [Desktop Entry] Type=Application Exec=/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd X-KDE-StartupNotify=false X-KDE-autostart-phase=0 X-GNOME-Autostart-enabled=false OnlyShowIn=KDE;GNOME;Unity;XFCE; NoDisplay=true (Kdeconnectd has port 1716 open all the time when running.) It's not just starting automatically when booting but also a while after ending the process without me opening it. I'm running Debian 9/KDE. Update: Debian issue now is here

I'm using nftables on a router running NixOS 22.11 (with the latest XanMod kernel patches and acpid as well as irqbalance enabled). The machine has 3 interfaces: enp4s0 which is connected to the internet and two local WiFi access points serving distinct IP LANs, wlp1s0 and wlp5s0. My nftables configuration is the following: I just allow inbound DNS, DHCP and SSH traffic on the the local networks, and as allow outbound and forwarded traffic to the internet along with SNAT.

table ip filter {
	chain conntrack {
		ct state vmap { invalid : drop, established : accept, related : accept }
	}
	chain dhcp {
		udp sport 68 udp dport 67 accept comment "dhcp"
	}
	chain dns {
		ip protocol { tcp, udp } th sport 53 th sport 53 accept comment "dns"
	}
    chain ssh {
        ip protocol tcp tcp dport 22 accept comment "ssh"
    }

	chain in_wan {
		jump dns
		jump dhcp
		jump ssh
	}
	chain in_iot {
		jump dns
		jump dhcp
	}
	chain inbound {
		type filter hook input priority filter; policy drop;
		icmp type echo-request limit rate 5/second accept
		jump conntrack
		iifname vmap { "lo" : accept, "wlp1s0" : goto in_wan, "enp4s0" : drop, "wlp5s0" : goto in_iot }
	}

	chain forward {
		type filter hook forward priority filter; policy drop;
		jump conntrack
		oifname "enp4s0" accept
	}
}

table ip nat {
	chain postrouting {
		type nat hook postrouting priority srcnat; policy accept;
		oifname "enp4s0" snat to 192.168.1.2
	}
}

table ip6 global6 {
	chain input {
		type filter hook input priority filter; policy drop;
	}

	chain forward {
		type filter hook forward priority filter; policy drop;
	}
}

With this simple configuration, I expected KDE Connect to not work as it requires ports 1714-1764 to be open . And indeed, if I connect my computer to wlp1s0 and my phone to wlp5s0 (so different interfaces), the devices cannot see each other, and I can see the packets through tcpdump as well as through nftables, either using logging rules or nftrace. But somehow if I now put both machines on the same interface, e.g. wlp1s0, KDE Connect works perfectly and the devices see each other. My best guess was that this happens because of connection tracking, but even if I add

chain trace_wan {
		type filter hook prerouting priority filter - 1; policy accept;
		iifname "wlp1s0" oifname "wlp1s0" meta nftrace set 1
	}

to the filter table, I can't see any packets when running nft monitor trace. Similarly I can't see any packets in the system journal when inserting a logging rule at index 0 in the forward chain. And yet when running tcpdump -i wlp1s0 port 1716 I can see packets I expected nftables to see as well:

14:33:59.943462 IP 192.168.2.11.55670 > 192.168.2.42.xmsg: Flags [.], ack 20422, win 501, options [nop,nop,TS val 3319725685 ecr 2864656484], length 0
14:33:59.957101 IP 192.168.2.42.xmsg > 192.168.2.11.55670: Flags [P.], seq 20422:20533, ack 1, win 285, options [nop,nop,TS val 2864656500 ecr 3319725685], length 111

Why can nftables not see those packets when the two devices are connected on the same interface ? How can I make nftables actually drop all these forwarded packets by default ? --- Additional information requested in the comments:

❯ ip -br link
lo               UNKNOWN         
enp2s0           DOWN            
enp3s0           DOWN            
enp4s0           UP              
wlp5s0           UP              
wlp1s0           UP              

❯ ip -4 -br address
lo               UNKNOWN        127.0.0.1/8
enp4s0           UP             192.168.1.2/24
wlp5s0           UP             192.168.3.1/24
wlp1s0           UP             192.168.2.1/24

❯ bridge link

❯ ip route
default via 192.168.1.1 dev enp4s0 proto static
192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.2
192.168.1.1 dev enp4s0 proto static scope link
192.168.2.0/24 dev wlp1s0 proto kernel scope link src 192.168.2.1
192.168.3.0/24 dev wlp5s0 proto kernel scope link src 192.168.3.1

❯ sysctl net.bridge.bridge-nf-call-iptables
sysctl: error: 'net.bridge/bridge-nf-call-iptables' is an unknown key

`

Zenmap shows me that port 1716/tcp is open and sudo fuser -v 1716/tcp tells me kdeconnectd is responsible for it. Why does kdeconnectd have the 1716 port opened all the time? And what would be best practice from a security standpoint for it? I'd like to use KDE Connect but not be vulnerable to any kind of attack that could exploit this open port. Would that be having it closed except when I want to explicitly use KDE Connect maybe? If that would be a good thing to do: how can I do that? I'm running Debian 9.1 with KDE and am still new to GNU/Linux. Edit: based on schweik's answer a current way seems to be running sudo chmod -x /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd && pkill kdeconnectd (after running KDE Connect) and sudo chmod +x /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd before running KDE Connect. It has to be run again after updating the package and one might also move the file. Check with sudo lsof -i.

How could I use KDEConnect over wireguard, that does no implement broadcasting?

When I try and browse my Android device using kdeconnectd by: 1. Right clicking on the kdeconnect-indicator icon in my system tray 2. Click on the dropdown with my phone's name 3. Click on "Browse device" I get the following error in the console, and nothing happens:

$ /usr/lib/kdeconnectd &
...
QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type in parameter list: NetworkPacket
/usr/bin/fusermount: entry for /run/user/1000/850013e6eeea839c not found in /etc/mtab

I am on KDE Neon 5.14. Using latest versions of KDE connect on Neon and Android. I am trying to browse my phone file system but getting this error: The process for the kdeconnect://92e92185f23aaf5b protocol died unexpectedly I have made sure KDE connect on android has all permissions and plugin is enabled on both sides. Here is the output of ~/.xsession-errors when trying this. kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so' QCoreApplication::arguments: Please instantiate the QApplication object first QCoreApplication::applicationDirPath: Please instantiate the QApplication object first QCoreApplication::applicationFilePath: Please instantiate the QApplication object first QCoreApplication::arguments: Please instantiate the QApplication object first KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = path = pid = 13797 KCrash: Arguments: kdeinit5: PID 13797 terminated. Could not find service for job "Job 13" with app name "org.kde.kdeconnectd" Could not find service for job "Job 13" with app name "org.kde.kdeconnectd" qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60266, resource id: 100663303, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60267, resource id: 83886155, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60271, resource id: 83886155, major code: 142 (Unknown), minor code: 3 trying to show an empty dialog trying to show an empty dialog qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60701, resource id: 83886155, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60702, resource id: 83886161, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60703, resource id: 83886173, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60704, resource id: 83886155, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60705, resource id: 83886161, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60706, resource id: 83886173, major code: 142 (Unknown), minor code: 3 Output of journalctl -xe at the time: Oct 21 16:07:22 neon org.kde.kdeconnect: kdeconnect.plugin.sftp: Mount device: "Xiaomi Redmi 4X" Oct 21 16:07:23 neon org.kde.kdeconnect: kf5.kio.widgets: KRun(0x55e19f43e5d0) ERROR 143 "The process for the kdeconnect://92e92185f23aaf5b protocol died unexpectedly." Oct 21 16:07:25 neon org.kde.kdeconnect: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9418, resource id: 42156835, major code: 40 (TranslateCoords), minor code: 0

I'm trying to get KDE Connect (version 1.4.0) to work at full capacity with my Android phone and Feren OS (UbuntuLTS+LinuxMint+KDE). Pairing, exchange of notifications, and even such a cute feature as pausing PC music player during outgoing/incoming phone calls work perfectly. However, when it comes to the menu items, only "Ring my phone" works. **"Share file" and "SMS Messages" don't do anything at all.** As for **"Browse this device"** (or clicking my phone shown under "Devices" in Dolphin sidebar), first there was a problem with the deviceID folder automatically created under /run/user/1000 which showed no owner, etc. resulting in an error message like inaccessible or unavailable or permissions problem. When I managed to create a folder with no ownership/permissions problems, I then received another error message: Error when accessing filesystem.sshfs Finished with exit code 1

I am a new iPhone owner. Previously, I installed [KDE Connect](https://community.kde.org/KDEConnect) on both my GNU/Linux laptop and Android device. This allowed me to pair the devices on my local network without knowing their local IP addresses, and transfer files between them without a cable. It appears that there is no Connect-compatible client on the Apple App Store (see footnote 1). I have found instructions for [pairing and transferring files to/from an iPhone with a cable](https://www.dedoimedo.com/computers/linux-iphone-6.html) . I don't want to rely on an internet connection. How can I: * pair a GNU/Linux system with an iPhone on a local wifi network * without knowing their respective IP addresses * and then transfer files between them? Installing packages/apps on either device is acceptable, but the apps must be libre licensed (even on the Apple App Store). ---- Footnote 1: > There was some development of a KDE Connect client app for iOS in 2014... but due to our experience and various technical and organizational factors it's unlikely that we will have official iOS support anytime soon.