Cannot make KDE connect work
by OutSiderBR from LinuxQuestions.org on (#55X9E)
I tried to install KDE Connect app in my Motorola G5 S Plus, Android 8.1.0, and all went OK. I then tried to use KDE Connect in Slackware current, Plasma 4, and had no success. I found out that kdeconnectd was not running (Slackware default) and loaded it manually. I tried to debug the problem and got nowhere. Here is the check list:
1. Both devices are on the same network: 192.168.0.0. My notebook has both wlan0 at 192.168.0.14 and eth0 at 192.168.0.11. Mobile at 192.168.0.10.
2. Is the kdeconnectd process running:
ps -ef | grep kdeconnectd
****** 5646 1 0 14:31 ? 00:00:00 /usr/lib64/kde4/libexec/kdeconnectd
3. Is the process listening?
sudo netstat -tunelp | grep -i kdeconnect
tcp 0 0 0.0.0.0:1714 0.0.0.0:* LISTEN 1000 291383 5646/kdeconnectd
udp 0 0 0.0.0.0:49110 0.0.0.0:* 1000 291384 5646/kdeconnectd
udp 0 0 0.0.0.0:1714 0.0.0.0:* 1000 291382 5646/kdeconnectd
4. Maybe your firewall gets in the way?
sudo -H iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
5. Are the ports open/blocked?
sudo -H nc -z -v -n 192.168.0.10 1714-1716
(UNKNOWN) [192.168.0.10] 1716 (?) open
I can also telnet 192.168.0.10 1716
6. Check the kdeconnect home dir
ls -al /home/<user>/.config/kdeconnect/
/bin/ls: cannot access '/home/<user>/.config/kdeconnect/': No such file or directory
7. Check CLI interface
kdeconnect-cli -l
0 devices found
8. tcpdump on mobile app search shows:
sudo -H tcpdump -ieth0 -s0 -n -v host 192.168.0.10
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:38:00.968348 IP (tos 0x0, ttl 64, id 46316, offset 0, flags [+], proto UDP (17), length 1500)
192.168.0.10.45295 > 192.168.0.14.1716: UDP, bad length 1637 > 1472
15:38:00.968357 IP (tos 0x0, ttl 64, id 46316, offset 1480, flags [none], proto UDP (17), length 185)
192.168.0.10 > 192.168.0.14: ip-proto-17
15:38:00.969082 IP (tos 0x0, ttl 64, id 22631, offset 0, flags [+], proto UDP (17), length 1500)
192.168.0.10.45295 > 255.255.255.255.1716: UDP, bad length 1637 > 1472
15:38:00.969086 IP (tos 0x0, ttl 64, id 22631, offset 1480, flags [none], proto UDP (17), length 185)
192.168.0.10 > 255.255.255.255: ip-proto-17
Does this show that the mobile uses an MTU greater than the network supports ? This is the only signal I get from the mobile. Of course, I did not succeed to connect both systems. Maybe someone can help me.
I use slackware64-current with some weeks delay to avoid new bugs.
1. Both devices are on the same network: 192.168.0.0. My notebook has both wlan0 at 192.168.0.14 and eth0 at 192.168.0.11. Mobile at 192.168.0.10.
2. Is the kdeconnectd process running:
ps -ef | grep kdeconnectd
****** 5646 1 0 14:31 ? 00:00:00 /usr/lib64/kde4/libexec/kdeconnectd
3. Is the process listening?
sudo netstat -tunelp | grep -i kdeconnect
tcp 0 0 0.0.0.0:1714 0.0.0.0:* LISTEN 1000 291383 5646/kdeconnectd
udp 0 0 0.0.0.0:49110 0.0.0.0:* 1000 291384 5646/kdeconnectd
udp 0 0 0.0.0.0:1714 0.0.0.0:* 1000 291382 5646/kdeconnectd
4. Maybe your firewall gets in the way?
sudo -H iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
5. Are the ports open/blocked?
sudo -H nc -z -v -n 192.168.0.10 1714-1716
(UNKNOWN) [192.168.0.10] 1716 (?) open
I can also telnet 192.168.0.10 1716
6. Check the kdeconnect home dir
ls -al /home/<user>/.config/kdeconnect/
/bin/ls: cannot access '/home/<user>/.config/kdeconnect/': No such file or directory
7. Check CLI interface
kdeconnect-cli -l
0 devices found
8. tcpdump on mobile app search shows:
sudo -H tcpdump -ieth0 -s0 -n -v host 192.168.0.10
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:38:00.968348 IP (tos 0x0, ttl 64, id 46316, offset 0, flags [+], proto UDP (17), length 1500)
192.168.0.10.45295 > 192.168.0.14.1716: UDP, bad length 1637 > 1472
15:38:00.968357 IP (tos 0x0, ttl 64, id 46316, offset 1480, flags [none], proto UDP (17), length 185)
192.168.0.10 > 192.168.0.14: ip-proto-17
15:38:00.969082 IP (tos 0x0, ttl 64, id 22631, offset 0, flags [+], proto UDP (17), length 1500)
192.168.0.10.45295 > 255.255.255.255.1716: UDP, bad length 1637 > 1472
15:38:00.969086 IP (tos 0x0, ttl 64, id 22631, offset 1480, flags [none], proto UDP (17), length 185)
192.168.0.10 > 255.255.255.255: ip-proto-17
Does this show that the mobile uses an MTU greater than the network supports ? This is the only signal I get from the mobile. Of course, I did not succeed to connect both systems. Maybe someone can help me.
I use slackware64-current with some weeks delay to avoid new bugs.