-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-03-05 a las 16:25 -0800, John Andersen escribió:
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.
Why do you say that it is more traditional? :-? :-o
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.)
You have to put all machines, cable and wifi, all in the same network. Yes or Yes. Alternatively, you have to add routes on every single machine telling them what gateway to use to connect to the other network, ie, a machine that sees both networks and knows how to route, ie, your new WiFi router. Alternatively, put everything on the 10.*.*.* network instead. Choose your poison. It is not a limitation of kdeconnect. Nothing can cross a subnet unless you route it. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAli8wE8ACgkQja8UbcUWM1w+FQEAndaXmbC+8pqPuIYaF9tck0/h DQoiAbyRY80EDRXzzQcBAJLNga+ZZuvzFeRqaZxyNfgAZOsTm/4Lt+3wbeJAWiLd =Pogz -----END PGP SIGNATURE-----