Bug 410769

Summary: No comms when phone is in AP mode
Product: [Applications] kdeconnect Reporter: tnemeth
Component: android-applicationAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED NOT A BUG    
Severity: normal CC: e.duisters1, tnemeth
Priority: NOR    
Version First Reported In: 1.10   
Target Milestone: ---   
Platform: Other   
OS: Android 9.x   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Notifications area on the PC
On the phone

Description tnemeth 2019-08-09 15:13:26 UTC
SUMMARY
    Hi. When I put my phone in AP mode and I connect my PC to my phone that
    way, no communications can be established between the phone and the PC
    KDE connect applications.


STEPS TO REPRODUCE
1. Enable Wifi AP mode in Android
2. Connect a PC to the Wifi AP
3. Try to find the PC from the phone APP


OBSERVED RESULT
    The PC cannot be detected.


EXPECTED RESULT
    As the PC and the phone are on the same network, they should be able to
    communicate.


SOFTWARE/OS VERSIONS
Windows: N/A
macOS: N/A
Linux/KDE Plasma: Debian Testing (kernel: 4.19.0) / 5.14.5
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
    Android KDE connect application version: 1.12.7 (from F-droid)
Comment 1 Erik Duisters 2019-08-09 16:50:51 UTC
Hi,

Pairing like that definitely works because that is how I circumvent my company laptops firewall. Do you have a firewall running by any change? If so see https://community.kde.org/KDEConnect#I_have_two_devices_running_KDE_Connect_on_the_same_network.2C_but_they_can.27t_see_each_other
Comment 2 Bug Janitor Service 2019-08-24 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 tnemeth 2019-08-24 08:56:41 UTC
Created attachment 122316 [details]
Notifications area on the PC

KDEconnect is not associated, doesn't show up in the active notification. When associated, it does. Wifi is connected to the phone AP, no FW running.
Comment 4 tnemeth 2019-08-24 08:57:57 UTC
(In reply to Erik Duisters from comment #1)
> Hi,

    Hi.
    Sorry for the tardiness, I did not see you comment notification in
    my mailbox.


> Pairing like that definitely works because that is how I circumvent my
> company laptops firewall.

    That's what I also wanted to do at work ;)


> Do you have a firewall running by any change?

    Indeed I manually set up a FW... However, when I activate the AP mode
    at home, my PC beeing connected to both my wired LAN and the phone AP,
    KDEconnect doesn't detect my phone. Neither the phone nor the PC can
    detect the other one.

    Is it because they have previously been associated through the wired
    LAN (usually my phone connects to my home AP) ?

    On my home PCs FW are disabled:

sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Thomas.
Comment 5 tnemeth 2019-08-24 09:04:13 UTC
Created attachment 122317 [details]
On the phone

AP activated, PC connected to the AP, not detected by the android app. Pḧone not detected by the PC app.
Comment 6 tnemeth 2019-08-26 09:37:46 UTC
I forgot to change the status with my last comment :(
Comment 7 tnemeth 2019-08-26 09:51:42 UTC
Just to add more... At work, using:
- kubuntu 18.04,
- kernel 4.15,
- Plasma 5.12.8,
- Frameworks 5.47.0
- Qt 5.9.5

With a special iptables rule to avoid blocking packets to/from the AP, both
systems can communicate with each other. Good :) I still don't know why it
doesn't work at home...
Comment 8 Erik Duisters 2019-08-26 15:20:01 UTC
(In reply to tnemeth from comment #7)
> Just to add more... At work, using:
> - kubuntu 18.04,
> - kernel 4.15,
> - Plasma 5.12.8,
> - Frameworks 5.47.0
> - Qt 5.9.5
> 
> With a special iptables rule to avoid blocking packets to/from the AP, both
> systems can communicate with each other. Good :) I still don't know why it
> doesn't work at home...

Did you try adding your desktop by ip adress on Android? You can do that from the overflow menu pair new devices page.
Comment 9 tnemeth 2019-08-26 17:00:06 UTC
(In reply to Erik Duisters from comment #8)
> Did you try adding your desktop by ip adress on Android? You can do that
> from the overflow menu pair new devices page.

    I did not try. And trying made it work. Thank you.
Comment 10 tnemeth 2019-08-26 17:01:23 UTC
Marking it as resolved/not-a-bug since there was no real problem here. However
autodetection should be better :)