https://bugs.kde.org/show_bug.cgi?id=508960
--- Comment #6 from Anish Murthy <[email protected]> --- (In reply to Anish Murthy from comment #5) > (In reply to Andy Holmes from comment #3) > > The protocols listed in your log are not actually related to KDE Connect, so > > the output there is a bit misleading. For example, `tftp-mcast` just happens > > to be associated with port 1758, which is in the 1739-1764 range used by KDE > > Connect. > > > > The fact that these ports are in LISTEN indicates the local device is > > waiting for a remote device to accept a file transfer. I would expect these > > to timeout eventually, but it's also curious that the remote device isn't > > connecting at all. > > > > I assume that at least one file transfer works? If not, this probably a > > firewall or network configuration problem. If not, you might need to collect > > debug logs from the other device (presumably Android). > > I am able to send files when the device first starts and all these protocols > haven't started listening yet. > When I run psof, I see that they're all listed as from the command > `kdeconnec` with the same process number. I'm unsure of how much I'm > supposed to hide, but I've attached a screenshot. Let me know if I need to > add any other info. The command was `sudo lsof -i :1739-1764`. I miswrote psof in the last comment. -- You are receiving this mail because: You are watching all bug changes.
