kdeconnect doesn't

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

kdeconnect doesn't

Gary Dale-8
I keep reading wonderful things about KDEconnect but I've yet to
experience them. My android phones can't see my Debian/Buster desktop
and vice versa. Both devices are on the same network and I'm not running
an internal firewall on my desktop.

I've been trying KDEconnect intermittently for many months, during which
time I've had a couple different Android phones, but have yet to have
any success. I have no indication of any other network issues on my home
network.

Both IP addresses (phone & desktop) are assigned via DHCP, which is
probably about as normal as you can get. Manually adding the desktop's
current IP address to the phone app doesn't help either.

Any ideas?

Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Eric Valette

I keep reading wonderful things about KDEconnect but I've yet to experience them. My android phones can't see my Debian/Buster desktop and vice versa. Both devices are on the same network and I'm not running an internal firewall on my desktop. I've been trying KDEconnect intermittently for many months, during which time I've had a couple different Android phones, but have yet to have any success. I have no indication of any other network issues on my home network. Both IP addresses (phone & desktop) are assigned via DHCP, which is probably about as normal as you can get. Manually adding the desktop's current IP address to the phone app doesn't help either.
Any ideas?

I already reported this bug <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898320>, even upstream <https://bugs.kde.org/show_bug.cgi?id=394646>, even on the kdeconnect dev mailing list. Nobody answered. Its has been so for month.

Using wireshark I see packet exchanged netween android devices and PC  but probably the layout of the data are broken during network conversion when exchanged (arm 32 bits and amd64 64 bits) .

-- eric




Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Luigi Toscano
Eric Valette ha scritto:

>> I keep reading wonderful things about KDEconnect but I've yet to experience
>> them. My android phones can't see my Debian/Buster desktop and vice versa.
>> Both devices are on the same network and I'm not running an internal
>> firewall on my desktop. I've been trying KDEconnect intermittently for many
>> months, during which time I've had a couple different Android phones, but
>> have yet to have any success. I have no indication of any other network
>> issues on my home network. Both IP addresses (phone & desktop) are assigned
>> via DHCP, which is probably about as normal as you can get. Manually adding
>> the desktop's current IP address to the phone app doesn't help either.
>> Any ideas?
>
> I already reported this bug
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898320>, even upstream
> *<https://bugs.kde.org/show_bug.cgi?id=394646 
> <https://bugs.kde.org/show_bug.cgi?id=394646>*>, even on the kdeconnect dev
> mailing list. Nobody answered. Its has been so for month.

Most likely it's not reproducible for the developers.
>
> Using wireshark I see packet exchanged netween android devices and PC  but
> probably the layout of the data are broken during network conversion when
> exchanged (arm 32 bits and amd64 64 bits) .

If it was the case, it would have been broken for everyone. But for example it
works for me (and other people). So it can't simply be a matter of packages
mangled between different architectures.

You mention that you see packages, but do you see the specific packages for
kdeconnect? I don't see the firewall mentioned in the bug, I guess it was
disabled, but just to be sure... (even if probably Debian does not enable it
by default).

--
Luigi

Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Eric Valette
On 09/28/2018 02:29 PM, Luigi Toscano wrote:
> Eric Valette ha scritto:

> Most likely it's not reproducible for the developers.


But on the other hand no zsingle developper asked for any wireshark
traces on my machine or offered any hint beside remove/reinstall/purge
data...

>> Using wireshark I see packet exchanged netween android devices and PC  
>> but probably the layout of the data are broken during network
>> conversion when exchanged (arm 32 bits and amd64 64 bits) .
>
> If it was the case, it would have been broken for everyone. But for
> example it works for me (and other people). So it can't simply be a
> matter of packages mangled between different architectures.


What I can say it that machines do talk but refuses to connect. and no
firewall on the LAN. I did happen after upgrade but since It upgraded
both side before realizing there was a problem...


-- eric

Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Eric Valette
On 09/28/2018 02:33 PM, Eric Valette wrote:
> On 09/28/2018 02:29 PM, Luigi Toscano wrote:

>> If it was the case, it would have been broken for everyone. But for
>> example it works for me (and other people). So it can't simply be a
>> matter of packages mangled between different architectures.

What is strange is that android world devices see each others, linux
worlds devices see each other, android world and Linux world devices do
communicate at IP level (I have various application beside kdeconnect
that work (DLNA, tvheadend, juicessh,...)) but fail to recognize devices
as suitable for kdeconnect explained in the bug report.

-- eric


Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Andy Wood
In reply to this post by Luigi Toscano
On Friday, 28 September 2018 13:29:08 BST Luigi Toscano wrote:
[...]
> If it was the case, it would have been broken for everyone. But for example
> it works for me (and other people). So it can't simply be a matter of
> packages mangled between different architectures.

No problem here with current version in buster (1.3.1-1) on amd64, and version
1.8.4 in Lollipop from F-Droid.

Andy.



Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Luigi Toscano
In reply to this post by Eric Valette
Eric Valette ha scritto:

> On 09/28/2018 02:33 PM, Eric Valette wrote:
>> On 09/28/2018 02:29 PM, Luigi Toscano wrote:
>
>>> If it was the case, it would have been broken for everyone. But for example
>>> it works for me (and other people). So it can't simply be a matter of
>>> packages mangled between different architectures.
>
> What is strange is that android world devices see each others, linux worlds
> devices see each other, android world and Linux world devices do communicate
> at IP level (I have various application beside kdeconnect that work (DLNA,
> tvheadend, juicessh,...)) but fail to recognize devices as suitable for
> kdeconnect explained in the bug report.
>


Can you by chance try to see if any of your Android devices sees kdeconnect
instance running on a PC on a different network? A friend's PC, or so.

--
Luigi

Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Eric Valette
On 09/28/2018 03:18 PM, Luigi Toscano wrote:
> Eric Valette ha scritto:

> Can you by chance try to see if any of your Android devices sees
> kdeconnect instance running on a PC on a different network? A friend's
> PC, or so.

No I unfortunately cannot. But I'm also dubious about the information it
would provide:
        1) As kdeconnect Linux sees other Linux both sides, kdeconnect on
Linuxes is connected to the network and does correctly receives packets
and decodes packets when they are emitted via Linux kdeconnect,
        2) As kdeconnect Android sees other Android both sides, kdeconnect on
Android is connected to the network and does receives packets and
decodes packets when they are emitted via Android kdeconnect,
        3) Android devices and Linux devices do talk at IP level as wireshark
shows; so it is not a network level 2 problem, remains the data
exchanged or the way they are validated,

That is why I suggest that under *yet to understand circumstances* the
data exchanged between kdeconnect Android kdeconnect Linux and  are
either wrong or the check used to validate them is wrong.

-- eric

Reply | Threaded
Open this post in threaded view
|

Info on versions for me

Eric Valette
In reply to this post by Andy Wood

Just to add my config : Linux : debian unstable => kdeconnect 1.3.1 (all tested linuxes) and two mobiles tested : android Oreo (8.1.0) 1.8.x and even tested beta versions 1.9, and android nougat 7.1.x  kdeconnect 1.8.x from play store.


-- eric

Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Gary Dale-8
In reply to this post by Gary Dale-8
On 2018-09-27 11:59 PM, Gary Dale wrote:

> I keep reading wonderful things about KDEconnect but I've yet to
> experience them. My android phones can't see my Debian/Buster desktop
> and vice versa. Both devices are on the same network and I'm not
> running an internal firewall on my desktop.
>
> I've been trying KDEconnect intermittently for many months, during
> which time I've had a couple different Android phones, but have yet to
> have any success. I have no indication of any other network issues on
> my home network.
>
> Both IP addresses (phone & desktop) are assigned via DHCP, which is
> probably about as normal as you can get. Manually adding the desktop's
> current IP address to the phone app doesn't help either.
>
> Any ideas?
>
I note also that I have a laptop running Debian/Stretch that also fails
to see or be seen using kdeconnect. While this suggests a firewall
issue, I don't have one running AFAIK.

The default Debian installation of iptables is supposedly allow all and
I've run iptables commands to open the default kdeconnect ports but that
didn't work either.

This shouldn't be an issue but I have also had 3 different routers since
I first tried to use kdeconnect. It didn't work with any of them handing
out IP addresses....

To recap: I have a Stretch laptop, Buster desktop and Android phone.
They are all running kdeconnect but none of them can see the others.

Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Johannes Zarl-Zierl
Am Freitag, 28. September 2018, 20:39:01 CEST schrieb Gary Dale:
> This shouldn't be an issue but I have also had 3 different routers since
> I first tried to use kdeconnect. It didn't work with any of them handing
> out IP addresses....

It may very well be an issue. Some routers provide firewalling and isolation
between hosts on the same network. If you use a pre-configured router by your
ISP, they might have configured some isolation between the hosts. (And if all
threee routers have been from the same ISP, they should be configured the
same).

By any chance, do your Linux PCs use a wired connection? The fact that the PCs
can talk to each other, but not to the phone(s) could be caused by the router
isolating wired network ports from wireless ones.

  Johannes





Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Gary Dale-8
On 2018-09-28 04:15 PM, Johannes Zarl-Zierl wrote:

> Am Freitag, 28. September 2018, 20:39:01 CEST schrieb Gary Dale:
>> This shouldn't be an issue but I have also had 3 different routers since
>> I first tried to use kdeconnect. It didn't work with any of them handing
>> out IP addresses....
> It may very well be an issue. Some routers provide firewalling and isolation
> between hosts on the same network. If you use a pre-configured router by your
> ISP, they might have configured some isolation between the hosts. (And if all
> threee routers have been from the same ISP, they should be configured the
> same).
>
> By any chance, do your Linux PCs use a wired connection? The fact that the PCs
> can talk to each other, but not to the phone(s) could be caused by the router
> isolating wired network ports from wireless ones.
>
The three routers were from different ISPs. In fact one was not provided
by an ISP but rather was an older unit that I installed DD-WRT onto and
used it to provide an inner network separate from the one talking
directly to the ISP that I connected third-party devices to (thermostat,
solar panels, roomba). It died after a few months so now I'm connecting
directly through the ISP's router/modem again.

Prior to that I had a different router/modem from a different ISP.

My laptop connects with both wireless and wired connections.


Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Gary Dale-8
In reply to this post by Gary Dale-8
On 2018-09-27 11:59 PM, Gary Dale wrote:

> I keep reading wonderful things about KDEconnect but I've yet to
> experience them. My android phones can't see my Debian/Buster desktop
> and vice versa. Both devices are on the same network and I'm not
> running an internal firewall on my desktop.
>
> I've been trying KDEconnect intermittently for many months, during
> which time I've had a couple different Android phones, but have yet to
> have any success. I have no indication of any other network issues on
> my home network.
>
> Both IP addresses (phone & desktop) are assigned via DHCP, which is
> probably about as normal as you can get. Manually adding the desktop's
> current IP address to the phone app doesn't help either.
>
> Any ideas?
>
I managed to get kdeconnect to work between my laptop and my phone by
installing ufw and opening the kdeconnect ports in it. However the same
solution doesn't work on my desktop, which is where I really need it. I
rarely use my laptop.

My laptop is running Stretch and ufw seems to work fine on it. However
the version of ufw on Buster seems to have a problem that looks similar
to one reported 5 years ago on Github
(https://github.com/sovereign/sovereign/issues/73).

Basically, I installed ufw but the enable operation fails with the
message "ERROR: Could not load logging rules". A not very good
workaround of turning logging off failed to resolve the problem.

However ufw reports that it is active and I could add the port rules to
it. The status shows as:

# ufw status verbose
Status: active
Logging: off
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip

To                         Action      From
--                         ------      ----
1714:1764/udp              ALLOW IN    Anywhere
1714:1764/tcp              ALLOW IN    Anywhere
1714:1764/udp (v6)         ALLOW IN    Anywhere (v6)
1714:1764/tcp (v6)         ALLOW IN    Anywhere (v6)

but my phone still can't see the desktop and vice versa.

The only thing I can think of is my phone and laptop were probably
connected via wifi while my desktop is wired. However I can connect my
phone to my desktop using sshdroid.

Any ideas?

Reply | Threaded
Open this post in threaded view
|

Re: kdeconnect doesn't

Michael Schuerig-2
On Donnerstag, 1. November 2018 05:17:00 CET Gary Dale wrote:

> I managed to get kdeconnect to work between my laptop and my phone by
> installing ufw and opening the kdeconnect ports in it. However the same
> solution doesn't work on my desktop, which is where I really need it. I
> rarely use my laptop.
[...]
> Any ideas?

Maybe this is affecting you

https://bugs.kde.org/show_bug.cgi?id=400178

Michael

--
Michael Schuerig
mailto:[hidden email]
http://www.schuerig.de/michael/