<div dir="ltr">Ok, thank you! It would be awesome if you succeed implementing it, because a lot of people is requesting this feature :D</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 16, 2014 at 4:54 PM, Achilleas Koutsou <span dir="ltr"><<a href="mailto:achilleas.k@gmail.com" target="_blank">achilleas.k@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Unfortunately, I haven't had time to do much of anything beyond work the past few months. Things will most likely be easier next month, so I'll try and finish it up then.<br>
<br>
Given my lack of progress, the pairing issue is still there.<br>
Also, I haven't made the new backend read IP addresses from the saved settings yet. That should be much simpler, of course.<br>
<br>
What I have done, however, is lots of testing! Especially testing a persistent pairing/connection through a VPN for several hours. I haven't had any issues with communication between devices through a VPN (while the two devices are on different physical networks), given that they are already paired from within the same network.<br>
<br>
I hope to have a patch for you by the end of October, unless someone beats me to it.<br>
<br>
Regards,<br>
Achilleas<span class=""><br>
<br>
On 16/09/14 16:32, Albert Vaca wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Hello Achilleas,<br>
<br>
Sorry for the long absence. Have you made any progress on this? Did you<br>
manage to solve the problems with the pairing? Actually KDE Connect<br>
should listen to the VPN interface, but you may have to restart it.<br>
<br>
Regards,<br>
Albert<br>
<br>
<br>
On Wed, Aug 6, 2014 at 3:16 PM, Achilleas Koutsou <<a href="mailto:achilleas.k@gmail.com" target="_blank">achilleas.k@gmail.com</a><br></span><div><div class="h5">
<mailto:<a href="mailto:achilleas.k@gmail.com" target="_blank">achilleas.k@gmail.com</a>><u></u>> wrote:<br>
<br>
Greetings all,<br>
<br>
New guy here.<br>
<br>
I've been slowly working on implementing a new feature for KDE connect<br>
that will allow two devices to communicate through separate networks or<br>
through an alternative or non-local network (such as a VPN).<br>
Specifically, I wanted to address Bug 326509 [1] (feature request).<br>
<br>
My initial attempt started by adding a new backend for handling<br>
connections through VPNs automatically. There are two problems with this<br>
approach:<br>
- In order to be a general solution, it would have to accommodate all<br>
types of VPNs and VPN interfaces.<br>
- Some VPNs, e.g., OpenVPN in routing mode configured as a tunnel with a<br>
tun interface, don't allow broadcast packets, which is necessary for KDE<br>
Connect to work.<br>
<br>
My current approach is to add a new backend and menu for manually<br>
specifying IP addresses of foreign devices. This can also accommodate<br>
hostnames and non-standard port numbers. This was actually Albert Vaca's<br>
original idea which he shared with me when I first contacted him about<br>
working on this issue. Given the nature of KDE Connect, specifically the<br>
fact that it's designed and meant to Just Work, the manual IP input<br>
interface should probably be hidden in an advanced menu.<br>
<br>
So far, I've forked the repositories to my GitHub account (both KDE [2]<br>
and Android [3] repositories). On the Android side, I've got a few<br>
things working, mostly hard coded hacks as proof of concept. Specifying<br>
the VPN IP of my desktop in the Android app actually works, but the<br>
pairing is a bit flaky, probably because the KDE side isn't listening on<br>
the VPN interface (?).<br>
<br>
In general, when I'm finished with this, it should be possible to pair<br>
and connect two devices that aren't on the same network or when<br>
broadcast isn't possible, as long as the two devices are able to<br>
communicate with one another. This should also work when a device is<br>
behind a NAT/firewall, as long as the specified port is forwarded<br>
appropriately.<br>
<br>
This message is intended both as an introduction for myself, to let you<br>
know how I'm thinking about the problem, see if there's anything I<br>
missed about how the connectivity should (or could) work and to ask if<br>
anyone else has any ideas for solving this issue.<br>
<br>
So, what do you all think?<br>
<br>
Cheers.<br>
<br>
--<br>
Achilleas<br>
<br>
<br>
[1] - <a href="https://bugs.kde.org/show_bug.cgi?id=326509" target="_blank">https://bugs.kde.org/show_bug.<u></u>cgi?id=326509</a><br>
[2] - <a href="https://github.com/achilleas-k/kdeconnect-kde" target="_blank">https://github.com/achilleas-<u></u>k/kdeconnect-kde</a><br>
[3] - <a href="https://github.com/achilleas-k/kdeconnect-android/tree/manualip" target="_blank">https://github.com/achilleas-<u></u>k/kdeconnect-android/tree/<u></u>manualip</a><br>
______________________________<u></u>_________________<br>
KDEConnect mailing list<br></div></div>
<a href="mailto:KDEConnect@kde.org" target="_blank">KDEConnect@kde.org</a> <mailto:<a href="mailto:KDEConnect@kde.org" target="_blank">KDEConnect@kde.org</a>><br>
<a href="https://mail.kde.org/mailman/listinfo/kdeconnect" target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/kdeconnect</a><br>
<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>