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

[Achilleas Koutsou]

I'd like to know a bit more about the network setup. The laptop can ping
the desktop, but I wonder if there is an issue with the desktop pinging the
laptop or any other wireless device? The wireless devices are on a subnet,
but is that subnet NATed?

On Fri, 22 Jul 2016, 15:38 vineet garg, <grgvineet at gmail.com> wrote:

> Oh! I though he was talking about same subnet. Broadcasts are only used
> for device discovery. Since KDE connect directly connects using IP in all
> the cases, so even connectivity can be established by both devices in any
> manner than KDE connect should work fine too. But I will still say he
> should try pinging from both the sides. Sometimes the firewall is
> configured to only incoming data if a request for data is made by device.
> So it might happen that firewall is blocking incoming connections. Even
> router can be configured to do so, or any other software firewall may
> prevent incoming packets from different subnet.
>
> On Jul 22, 2016 5:16 PM, "Nerijus Baliunas" <nerijus at users.sourceforge.net>
> wrote:
>
>> He already said that "The laptop can also successfully SYN to the TCP
>> port (1714)".
>>
>> On Fri, 22 Jul 2016 16:42:14 +0530 vineet garg <grgvineet at gmail.com>
>> wrote:
>>
>> > Can you just try pinging one device from other. This will tell whether
>> both
>> > the devices can see each other or not. If ping fails, probably a router
>> > configuration issue else further investigation is needed.
>> >
>> > On Jul 22, 2016 4:06 PM, "Albert Vaca" <albertvaka at gmail.com> wrote:
>> >
>> > > I'm not sure what might be wrong, maybe your router is somehow
>> blocking
>> > > packets between the two networks? Broadcasts aren't needed when using
>> > > direct IP connections, so my intuition says it should work (or there
>> is a
>> > > bug with direct connections).
>> > >
>> > > On Wed, Jul 20, 2016 at 8:13 PM, skomorokh <skomorokh at harmless.ca>
>> 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
>> > >> _______________________________________________
>> > >> KDEConnect mailing list
>> > >> KDEConnect at kde.org
>> > >> https://mail.kde.org/mailman/listinfo/kdeconnect
>> > >>
>> > >
>> > >
>> > > _______________________________________________
>> > > KDEConnect mailing list
>> > > KDEConnect at kde.org
>> > > https://mail.kde.org/mailman/listinfo/kdeconnect
>> > >
>> > >
>>
>> Regards,
>> Nerijus
>> _______________________________________________
>> KDEConnect mailing list
>> KDEConnect at kde.org
>> https://mail.kde.org/mailman/listinfo/kdeconnect
>>
> _______________________________________________
> KDEConnect mailing list
> KDEConnect at kde.org
> https://mail.kde.org/mailman/listinfo/kdeconnect
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20160723/27efe242/attachment.html>