Bug 376803

Summary:	Cannot use KDE Connect on connected wifi using the proxy (squid)
Product:	[Applications] kdeconnect	Reporter:	raka.linuz
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED NOT A BUG
Severity:	critical	CC:	aleixpol, lion
Priority:	NOR
Version First Reported In:	1.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description raka.linuz 2017-02-22 14:02:04 UTC

I have trying to use KDE Connect on connected wifi using the proxy (squid), but I not have my laptop listed on my android phone. The squid configuration is allowed the KDE Connect dynamic ports (1714-1764). And the network iptables is redirect all tcp and udp connection to 3128 using intercept mode.

Comment 1 raka.linuz 2017-02-24 13:57:16 UTC

Also, KDE connect cannot use on public captive wifi. I'm tried it on McDonalds WiFi.

Comment 2 Lion Yang 2017-07-06 03:01:30 UTC

(In reply to raka.linuz from comment #1)
> Also, KDE connect cannot use on public captive wifi. I'm tried it on
> McDonalds WiFi.

Public WiFi usually has "AP Isolation". So it is impossible to broadcast or send message to anybody in this local network directly. It's a common security solution indeed.

Comment 3 Aleix Pol 2017-07-13 23:21:39 UTC

This is not something we can easily figure out. We can't adapt everyone's configuration.

If there's something specific that we should change to make your life easier, please tell us so and we'll look into it.