I as a user want to roam with my laptop and mobile between various network environments and have KDEConnect work seamlessly without further user intervention. I try to explain the setups I envision. One looks like the following: WiFi (172.16.0.0/24) / \ / \ Laptop ---- ---- Mobile And things work fine. Then I roam into a different environment which looks like this: LAN (10.1.1.0/20) WiFi (192.168.3.0/24) \ / \ \ / \ ----Laptop ---- ---- Mobile In this environment, I need to setup the IP address of the laptop in the KDEConnect client on the mobile to get things working, because it seems that KDEConnect is tied to the LAN interface at that point (impression to the user, at least KDEConnect broadcast packets are sent out on the LAN when I search for devices using the laptop software). The default GW for the laptop of course is a router on the LAN. Setting up the IP address of the laptop in the mobile is impractical since it may change on a daily basis (DHCP). Giving the user a global interface selection (e.g. combo box) would prevent that if the KDEConnect daemon would only use that interface. I could imagine that the interface will mostly be the wifi based one. A selection of e.g. 'any' can be used to keep today's functionality.
The app sends broadcast packages as well. Can you check with Wireshark if the desktop receives those broadcasts?
That's what I did. Yes, it receives the broadcasts but then sends out the connection request via the wrong interface. I don't remember exactly, but it could have been the SYN packet of a TCP connection setup. I can redo that and provide the packet traces if you want me to. In my second case, the LAN interface has a cheaper metric than the WiFi one and serves as the interface to the default GW. Hence the decision of the kernel to send the SYN that way.
Is there any chance that a package sent to the 10.1.1.0/20 subnet ends up in the 192.168.3.0/24 subnet (i.e. is there routing between them or are they completely isolated?) Or is there some kind of firewall that may block the package? In a perfect world the package would automatically take the right way. Maybe a entry in the routing table could ensure that packages destinated to the 192... subnet use the appropriate interface. However, I understand that this might be above your power. I am able to tell the package which interface to use. Right now I'm trying to automatically determine which one is the right one.
(In reply to Nicolas Fella from comment #3) I am able to tell the > package which interface to use. Right now I'm trying to automatically > determine which one is the right one. With that I mean Qt gives me the possibility, but it's not implemented.
I might have a workaround for your problem. Instead of specifying an IP address you can specify a hostname to connect to (assuming that your PCs hostname does not change regularly)
Power BI is a powerful business analytics tool developed by Microsoft that enables users to connect to various data sources, transform and model data, and create interactive reports and dashboards for data analysis. With its extensive visualization options, data exploration capabilities, collaboration features, and integration with other Microsoft tools, Power BI empowers organizations to gain valuable insights and make informed decisions based on their data. https://www.sevenmentor.com/power-bi-training-in-pune.php