Specifying an IP address isn't enough to connect to a different subnet?

[skomorokh]

Thanks for your helpful replies---had some more time to look into this today
and Achilleas Koutso nailed it, seems I had been inadvertently NATing
traffic between my wired and wireless subnets this whole time.

This was especially obvious with tcpdump as it showed the gateway rather
than the phone as the origin of the UDP traffic.

On 2016-07-20 02:13 PM, skomorokh wrote:
> Hi!
> 
> I have a not-so-uncommon setup where wireless devices are on 192.168.3.* and
> wired on 192.168.2.* and I want to use KDE Connect between my
> phone-on-wireless and my wired desktop.
> 
> However, it's not clear to me how---I added the exact IP and they can't see
> each other. Meanwhile, I am able to connect successfully when I run the same
> (current Ubuntu) version of KDE Connect on my laptop on the same subnet as
> the phone. The laptop can also successfully SYN to the TCP port (1714) that
> the program has bound on the desktop so it seems like there is connectivity.
> 
> Am I wrong to expect this to have worked? Are broadcasts required even with
> an IP specified? Anything else you might suggest I try to help narrow down
> the issue?
> 
> Thanks much,
> Jason
>