I've always run my wifi as a simple Access Point (same subnet) as my wired lan. KDE connect worked well in this environment, allowing KDEConnect to talk to all my machines. Now I've got my WIFI as a separate subnet** (a more traditional setup) and of course KDE Connect can not see the workstations, and vise versa. I suppose I could turn on wifi in addition to the Gigibit cat-5e interfaces but in some cases that would entail buying wifi cards and also messing around with the routing. Anybody know of any way to get around this limitation of kde-connect not being able to cross a subnet? Can I do this with the suse firewall in the lan server that is upstream of the wifi router? (KdeConnect seems to talk on tcp 1716.) ** Why did I do this? I got a Google Wifi triple router package which sets up a mesh network between all the thee dispersed routers which talk to each other on some side channel and therefore I have strong and booming fast wifi everywhere. It is the neatest thing since sliced bread but it has some limitations as to how it will talk to it's upstream (the lan). It will only act as a router, not a simple AP at this version. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org