Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.networking > #4439

Re: KDEConnect between Android phone and Linux XFCE PC

From Charlie Gibbs <cgibbs@kltpzyxm.invalid>
Newsgroups comp.os.linux.networking
Subject Re: KDEConnect between Android phone and Linux XFCE PC
Date 2019-07-24 00:21 +0000
Organization NewsGuy - Unlimited Usenet $23.95
Message-ID <qh889j0uur@news3.newsguy.com> (permalink)
References <qh4n0g$i0h$1@news.albasani.net> <qh7gjf01q3d@news2.newsguy.com> <qh7k10$q1m$1@news.albasani.net>

Show all headers | View raw


On 2019-07-23, Clark Smith <noaddress@nowhere.net> wrote:

> On Tue, 23 Jul 2019 17:36:47 +0000, Charlie Gibbs wrote:
>
>> On 2019-07-22, Spyridon Metaxas <SMet@somewhere.world> wrote:
>> 
>>> 	I have the following setup:
>>>
>>> 	A PC running Linux with the XFCE desktop, with IP address
>>> 192.168.127.166. This is a wired network.
>>>
>>> 	An Android phone with IP address 192.168.129.141. This is a WiFi
>>> network.
>>>
>>> 	From the PC I can ping the Android phone.
>>>
>>> 	From the Android phone I can ssh into the PC.
>>>
>>> 	When I launch KDEConnect in the PC and the phone, they cannot
>>> detect each other in their respective KDEConnect instances. However,
>>> they can each detect other devices.
>>>
>>> 	Although I am not positive, it would seem to be the case that
>>> KDEConnect in the PC is only detecting other devices with 192.168.127
>>> IP addresses, whereas the Android phone only sees other devices in the
>>> same WiFi as it is.
>>>
>>> 	What can I do, if anything, to get these two devices to see each
>>> other in KDEConnect?
>> 
>> Change the phone's IP address to 192.168.127.xxx, or change your netmask
>> from 255.255.255.0 to 255.255.0.0.
>
> 	Thanks. The netmask in the PC is 255.255.240.0. Shouldn't this be 
> enough already? The phone is getting its networking parameters by DHCP.

No.  Let's look at it binary:

Phone:    1100 0000 1010 1000 1000 0001 1000 1101
PC:       1100 0000 1010 1000 0111 1111 1010 0110
Netmask:  1111 1111 1111 1111 1110 0000 0000 0000
                              ^
Those third octets being on either side of 128 means that the high-order
bits are different, so you have to mask the whole thing off.  Either that,
or you must change one or both IP addresses.  Since the phone is getting
its address from DHCP, it might be easier to change the PC's address to
192.168.129.xxx if you can't change the netmask.

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  "Alexa, define 'bugging'."

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

KDEConnect between Android phone and Linux XFCE PC Spyridon Metaxas <SMet@somewhere.world> - 2019-07-22 16:07 +0000
  Re: KDEConnect between Android phone and Linux XFCE PC Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2019-07-23 17:36 +0000
    Re: KDEConnect between Android phone and Linux XFCE PC Clark Smith <noaddress@nowhere.net> - 2019-07-23 18:35 +0000
      Re: KDEConnect between Android phone and Linux XFCE PC Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2019-07-24 00:21 +0000
        Re: KDEConnect between Android phone and Linux XFCE PC Spyridon Metaxas <SMet@somewhere.world> - 2019-07-24 12:51 +0000
        Re: KDEConnect between Android phone and Linux XFCE PC Jerry Peters <jerry@example.invalid> - 2019-07-24 22:31 +0000

csiph-web