Dear Maintainer,

I have been upgrading my system recently, as I do every day
since I use testing, and with the advent of the 64b time
support I had to reinstall all KDE due to a pebkac.

After that kdeconnect refused to connect to my other systems
and phones. After a bit of investigations, I found out that
it only listen on IPv6 and not on IPv4.

As there isn't (as far as I know) a way to configure it to
use what I want, I can't make it chat with other kdeconnect
instances on my LAN.

```bash
thomas@localhost:~$ sudo netstat -tnlp | grep kdeconnect
tcp6       0      0 :::1716                 :::*                    LISTEN      13425/kdeconnectd
thomas@localhost:~$ sudo netstat -tnlp | grep ssh # as an example of service listening on both protos
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1809/sshd: /usr/sbi
tcp6       0      0 :::22                   :::*                    LISTEN      1809/sshd: /usr/sbi
thomas@localhost:~$ LC_ALL=C sudo fuser -v -n tcp 1716
                     USER        PID ACCESS COMMAND
1716/tcp:            thomas    13425 F.... kdeconnectd
thomas@localhost:~$ LC_ALL=C sudo fuser -v -n udp 1716
                     USER        PID ACCESS COMMAND
1716/udp:            thomas    13425 F.... kdeconnectd
```

tag 1067873 = wontfix
summary 1067873 0 This is a PEBKAC: iptables was empty but not nftables.

Thanks for the hint about nftables.  I had the same problem and this pointed
me in the right direction.  (In my case I just uninstalled both iptables and
nftables as I don’t use either one.)

Hello,

I have the same problem

# netstat -tnlp | grep kdeconnect
tcp6       0      0 :::1716                 :::*
                    LISTEN      2431/kdeconnectd

But I dont understand the solution proposed. I am using iptables.

Can someone give more details on the solution ?

Regards

Hi all,

just for future reference, I've arrived to this bug report trying to solve exactly this, and the
comment about nftables gave me the clue.

I have a laptop with an unstable installation, and I think it's now default to install firewalld
rejecting incoming connections.

This is why kdeconnect was not working for me; not really the fact that ipv6 was managing
the connections ; once I added an exception for kdeconnect to be able to receive incoming
connections it started working properly.

Adding

<service name="kdeconnect"/>

in /etc/firewalld/zones/public.xml fixed it for me ( actually I did it through the plasma-
firewall KCM config module)

Greetings all,