←back to thread

KDE Connect: Enabling communication between all your devices

(community.kde.org)
475 points snthd | 1 comments | 12 Oct 25 12:04 UTC | HN request time: 0.199s | source
Show context
karmakaze ◴[12 Oct 25 17:09 UTC] No.45559827[source]▶
I was wondering what "the network" here means:

> To achieve this, KDE Connect:

    implements a secure communication protocol over the network, and allows any developer to create plugins on top of it.
    Has a component that you install on your desktop.
    Has a KDE Connect client app you run on your phone.
Looking further it is only for the local network (with ways to extend it e.g. VPNs).
replies(2): >>45563974 #>>45601211 #
creatonez ◴[13 Oct 25 01:56 UTC] No.45563974[source]▶
It has bluetooth support now as well
replies(1): >>45573849 #
m463 ◴[13 Oct 25 22:08 UTC] No.45573849[source]▶
it also talks about using a VPN and what ports to open in a firewall.

I don't know how it handles the harder part, the "device on internet" talks to "device in my house"

most phones and apps use this "harder part" to interpose their corporate server for more than TURN/STUN and continue to "collect all the data" or "insert a subscription"

replies(2): >>45578146 #>>45654417 #
Oxodao ◴[14 Oct 25 10:00 UTC] No.45578146[source]▶
Did you get this to work with wireguard though?

As long as my phone is connected to wireguard KDEConnect does NOT see any other computer, apparently because it wont forward ICMP broadcast according to the internet.

I would really like to have a solution to this issue but since its baked in WG i don't think this is possible

replies(4): >>45583491 #>>45654475 #>>45654639 #>>45661288 #
1. 1oooqooq ◴[21 Oct 25 11:39 UTC] No.45654639[source]▶
mdns is a really awful protocol. it was already bad in the era it was born, being just an evolution of Microsoft NetBIOS out something. today in the age of wifi and overlay networks, i just consider it information leak with zero benefits.

so, the rfc have a section on how the mdns server have to evolve to handle multiple interfaces and own that. but in reality nobody gives a damn because the maintainer (redhat ibm) is it in the context it was invented (work networks on the 00s), so everyone (like many comments below) just work around in all the wrong ways making other things more complicated.

"just do these hundreds changed on wireguard, your firewall, install this reverse proxy... now your service that only exists to route things automatically can look like it works" heh.