Bug 392006 - No connection with different subnets
Summary: No connection with different subnets
Status: RESOLVED NOT A BUG
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (other bugs)
Version First Reported In: 1.2.1
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-18 17:14 UTC by Sefa Eyeoglu
Modified: 2018-09-27 06:55 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sefa Eyeoglu 2018-03-18 17:14:36 UTC 
KDE Connect (unclear if kdeconnectd or android app) is unable to find devices, which are on a different subnet.

I have following network setup:

 NET1 (10.10.10.0/24)     NET2 (10.10.11.0/24)
 - PC1    (10.10.10.10)   - PHONE1 (10.10.11.23)
 - PHONE1 (10.10.10.56)

If PC1 and PHONE1 are on the same network (10.10.10.0/24) KDE Connect works flawlessly. If PHONE1 moves to a different subnet, because of physical location, PHONE1 does not discover PC1 and the other way around. 

There are static routes (10.10.11.0/24 -> NET2, 10.10.10.0/24 -> NET2) so devices are able to communicate between each other. (No NAT between NET1 and NET2)

If there are any logs I could attach I can easily provide them.
Comment 1 Sefa Eyeoglu 2018-09-27 06:55:57 UTC 
I changed my network setup and don't have this issue anymore. Closing this for now.