I’ve been trying and failing to use kde connect with an android device and a laptop. I’m running opensuse 13.1 on the laptop and android 4.1.1 on my phone. The problem is that the two devices are unable to see each other, at all. If I turn off the firewall, everything is peachy. The devices communicate and I can enjoy the almost magical experience that kde connect brings to the linux desktop. If I activate the firewall, nothing works. I’ve tried to go to firewall-allowed service-Advanced and enter a UDP and TCP range of 1714:1764, but still nothing. I’ve tried to add a custom rule for the same port range , for UDP and TCP, but still no action. I’ve even tried to have both rules in place, but sadly no success. I have rebooted after each attempt, just in case that might alter the outcome, but nothing ever works. Does anybody have any idea on what I need to do to get it working?
So I would be happy to try and help as I have an Android phone, the latest openSUSE 13.1 installed and just installed kdeconnect-kde, but I don’t know how to start the application from openSUSE. I have downloaded the same app on the Android phone.
Thank You,
I don’t think you need to manually start it - it should just be running as a background process (at least that is how it works for me in 12.3).
But as nordlibris said, you’ll need to disable your firewall for the phone to be able to connect (or work out how ot punch a hole in the firewall).
All I did was disable my firewall and went into the app on my phone and told it to sync. Got a popup in the systray on KDE asking me to approve it and away it went.
in my opensuse 12.3 kdeconnect don’t see devices at all firewall or not…
This might be a silly question, but have you installed the mobile component from the play store? https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp
James,
- You need to be on the same LAN, so the phone must use wifi
- Start the app on openSUSE
- Start the app on the phone, it will show your computer as hostname.domain
- Press it, press “Send pair request”, accept it on the computer.
- Send a “Ping” through either device to check if it works.
- Have somebody call you, don’t answer and see the magic happening.
After I install the app on openSUSE I was unable to determine its running. Don’t know what I am looking for.
Thank You,
On 11/21/2013 10:56 AM, jdmcdaniel3 pecked at the keyboard and wrote:
> Knurpht;2599773 Wrote:
>> James,
>>
>> 1. You need to be on the same LAN, so the phone must use wifi
>> 2. Start the app on openSUSE
>> 3. Start the app on the phone, it will show your computer as
>> hostname.domain
>> 4. Press it, press “Send pair request”, accept it on the computer.
>> 5. Send a “Ping” through either device to check if it works.
>> 6. Have somebody call you, don’t answer and see the magic happening.
> After I install the app on openSUSE I was unable to determine its
> running. Don’t know what I am looking for.
>
> Thank You,
>
>
It is a widget that you need to add to your desktop.
Ken
yeeeaaa :)it woooorks.!!!
the tricks that solved has been first stop the firewall, second the phone and laptop must be in the same WAN not LAN, I don’t know if I said it correctly but it means that my laptop was wired connected to the router and phones to the same router but wireless, and it doesn’t works, when laptop was conncted wireless too it worked…
many thanks ciao pier
PS, the only feature is to see if somebody calls you?? I see only that, …I expected other controls…:-):-):-)
That Was the final Step I did not Understand, Thank You Very Much.
OK after setting up the Widget and disabling the openSUSE firewall it now works. I do get a notification on my PC for a phone call, but not sure what I expect to do with this setup. Can you explain to me what I do with it. How can we find out the firewall setting we need to add to keep from disabling it?
Thank You,
I have found a way to allow the firewall to run with Kdeconnect, but on reboot, it does not start working again. Basically, I turn off the firewall, connect to smart phone, turn firewall back on with the modifications made below. Kdeconnect continues to work with firewall turned on. Here is the status report of the running Firewall:
sudo /sbin/rcSuSEfirewall2 status
root's password:
SuSEfirewall2.service - SuSEfirewall2 phase 2
Loaded: loaded (/usr/lib/systemd/system/SuSEfirewall2.service; enabled)
Active: active (exited) since Thu 2013-11-21 15:25:57 CST; 38min ago
Process: 3788 ExecStop=/usr/sbin/SuSEfirewall2 systemd_stop (code=exited, status=0/SUCCESS)
Process: 3812 ExecStart=/usr/sbin/SuSEfirewall2 boot_setup (code=exited, status=0/SUCCESS)
Main PID: 3812 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/SuSEfirewall2.service
Nov 21 15:25:57 XPS-13-OPENSUSE.site systemd[1]: Starting SuSEfirewall2 phase 2...
Nov 21 15:25:57 XPS-13-OPENSUSE.site systemd[1]: Started SuSEfirewall2 phase 2.
The word is to open ports 1714-1764 for udp and tcp. My first problem was the newly rewritten YaST Firewall Editor is not allowing a range command like 1714:1764 to be entered meaning each port is a separate entry, a bug I suspect. I don’t like to run with the Firewall off and having to turn the firewall off to connect, then turn back on is a pain. Further if play with the firewall enough, it may refuse to start as well without another PC restart.
So, here is what I have done so far. You need to edit the firewall configuration file:
Alt-F2: kdesu /etc/sysconfig/SuSEfirewall2
Add the following code:
FW_SERVICES_ACCEPT_EXT="0/0,udp,,427
0/0,udp,,5353
0/0,tcp,,1714
0/0,tcp,,1715
0/0,tcp,,1716
0/0,tcp,,1717
0/0,tcp,,1718
0/0,tcp,,1719
0/0,tcp,,1720
0/0,tcp,,1721
0/0,tcp,,1722
0/0,tcp,,1723
0/0,tcp,,1724
0/0,tcp,,1725
0/0,tcp,,1726
0/0,tcp,,1727
0/0,tcp,,1728
0/0,tcp,,1729
0/0,tcp,,1730
0/0,tcp,,1731
0/0,tcp,,1732
0/0,tcp,,1733
0/0,tcp,,1734
0/0,tcp,,1735
0/0,tcp,,1736
0/0,tcp,,1737
0/0,tcp,,1738
0/0,tcp,,1739
0/0,tcp,,1740
0/0,tcp,,1741
0/0,tcp,,1742
0/0,tcp,,1743
0/0,tcp,,1744
0/0,tcp,,1745
0/0,tcp,,1746
0/0,tcp,,1747
0/0,tcp,,1748
0/0,tcp,,1749
0/0,tcp,,1750
0/0,tcp,,1751
0/0,tcp,,1752
0/0,tcp,,1753
0/0,tcp,,1754
0/0,tcp,,1755
0/0,tcp,,1756
0/0,tcp,,1757
0/0,tcp,,1758
0/0,tcp,,1759
0/0,tcp,,1760
0/0,tcp,,1761
0/0,tcp,,1762
0/0,tcp,,1763
0/0,tcp,,1764
0/0,udp,,1714
0/0,udp,,1716
0/0,udp,,1717
0/0,udp,,1716
0/0,udp,,1717
0/0,udp,,1718
0/0,udp,,1719
0/0,udp,,1720
0/0,udp,,1721
0/0,udp,,1722
0/0,udp,,1723
0/0,udp,,1724
0/0,udp,,1725
0/0,udp,,1726
0/0,udp,,1727
0/0,udp,,1728
0/0,udp,,1729
0/0,udp,,1730
0/0,udp,,1731
0/0,udp,,1732
0/0,udp,,1733
0/0,udp,,1734
0/0,udp,,1735
0/0,udp,,1736
0/0,udp,,1737
0/0,udp,,1738
0/0,udp,,1739
0/0,udp,,1740
0/0,udp,,1741
0/0,udp,,1742
0/0,udp,,1743
0/0,udp,,1744
0/0,udp,,1745
0/0,udp,,1746
0/0,udp,,1747
0/0,udp,,1748
0/0,udp,,1749
0/0,udp,,1750
0/0,udp,,1751
0/0,udp,,1752
0/0,udp,,1753
0/0,udp,,1754
0/0,udp,,1755
0/0,udp,,1756
0/0,udp,,1757
0/0,udp,,1758
0/0,udp,,1759
0/0,udp,,1760
0/0,udp,,1761
0/0,udp,,1762
0/0,udp,,1763
0/0,udp,,1764"
The code above goes just after the text already there shown here below:
## Type: string
## Default:
#
# Services to allow. This is a more generic form of FW_SERVICES_XXX_{IP,UDP,TCP}
# and more specific than FW_TRUSTED_NETS
#
# Format: space separated list of net,protocol,dport,sport,flags]]]
# Example: "0/0,tcp,22"
#
# Supported flags are
# hitcount=NUMBER : ipt_recent --hitcount parameter
# blockseconds=NUMBER : ipt_recent --seconds parameter
# recentname=NAME : ipt_recent --name parameter
# Example:
# Allow max three ssh connects per minute from the same IP address:
# "0/0,tcp,22,,hitcount=3,blockseconds=60,recentname=ssh"
#
# The special value _rpc_ is recognized as protocol and means that dport is
# interpreted as rpc service name. See FW_SERVICES_EXT_RPC for
# details.
#
# Note1: keep in mind that FW_SERVICES_EXT_TCP, FW_SERVICES_EXT_UDP
# take precedence over FW_SERVICES_ACCEPT_EXT so don't open the same
# port with both options.
#
# Note2: the iptables recent module may not be available for ipv6. To
# avoid an error message use 0.0.0.0/0 instead of 0/0. This will
# install the rule for ipv4 only.
#
After the first code block data is added below the second code block, save text config file and run the following code:
sudo /sbin/SuSEfirewall2
I have got us this far, found a bug in YaST Firewall (Not reported yet as there may more to the issue to add) and the solution only works one way. Who can step in and help with problem?
Thank You,
I didn’t see any need to add a widget as it was automatically added to my systray on install and notifications popped up as soon as I tried to pair the phone.
The feature I think I would use most with this app is moving files (multimedia) between my computer and the phone but the support seems limited.
I can send from phone to the computer but I cannot specify the location I send to. (it will only send to /home/~/Desktop/ )
I can’t find any way to send from my computer to the phone - I’d love to see that feature added (if it isn’t already there and I just can’t find it).
I,ve tried this, but it still does not work. I have even tried to enter the port range manually, since that corrected a few snags with my phone as an xbmc remote, I had high hopes it might work with kde connect as well.
I found this interesting firewall setting:
On openSUSE 12.3 firewall works perfect if enable KDE Connect service.
Create a file named “kde-connect” placed into the folder /etc/sysconfig/SuSEfirewall2.d/services/ that contains:
Name: KDE connect
Description: opens ports for KDE Connect in order to allow to connect phone
TCP=”1714:1764″
UDP=”1714:1764″
BROADCAST=”1714:1764″
I have not tried yet.
Thank You,
Tried it, and unfortunately, it did not work.
Nordli
Hi guys, I finally found a solution to our common problem with KDE Connect and SuSE Firewall.
This is confirmed to work, as I use this service file in firewall configuration, and my SGS2 works nicely 
The service file we have to put into “/etc/sysconfig/SuSEFirewall2.d/services” is:
## Name: KDE Connect
## Description: Opens port range 1714:1764 on tcp/udp/broadcast in order to let KDE Connect to work.
## Author: Alessandro Accardo (kLeZ-hAcK @ SuSE forums)
# space separated list of allowed TCP ports
TCP="1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764"
# space separated list of allowed UDP ports
UDP="1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764"
# space separated list of allowed UDP ports that accept broadcasts
BROADCAST="1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764"
Once done, enter YaST > Firewall and choose and add “KDE Connect” from the “Available Services”. Next > Next > Finish, and you should be done.
HTH.
kLeZ
It helps a lot, thankyou :D. I’ve been scratching my head over this one for a few days and only just found this thread. As for others I could get everything working but the initial connection between PC (ethernet) and phone (wifi) had to be made with the firewall down even with the custom rules in place. Once connected the firewall could go back up and everything would carry on working. No more of that nonsense now. Thanks again!
Xperia Z for the record, running Android 4.2.2.
Indeed you have:). You are a superhero.
Tried and tested to work even after reboot.
Nord
Silly question warning . . .
Does KDe Connect work with an Android tablet, or would there really be any reason to use it with one? (I’m alos not sure exactly what you would use it for with a tablet, but that may be another question entirely.) I saw KDe Connect discussed as part of the 13.1 review on Linux Action Show, and that got me curious. Thanks.