Previously, whenever I ran BitTorrent, I noticed numerous connections (about 30) from the same IP address with different port numbers. No traffic seems to be happening on those connections. When I killed the connections, they always reappeared immediately. For one torrent, the connections have the same IP addresses, but the address is random from the 184.108.40.206 to 220.127.116.11 range.
This stopped after I installed rules on my Windows Firewall to block out all traffic with 18.104.22.168/8. However after a while I noticed that PortableApps was not updating automatically on startup. And whenever I click on "Check For Updates", I get the error message "Unable to connect to PortableApps ...". I found this out after I worked on a different Windows host that does not have the Firewall rules; PortableApps automatically searched for updates on startup and updates were successful.
Please advice. Should I allow traffic on some specific addresses in the 22.214.171.124/8 range? What are they? Thanks in advance.
I've run a whois lookup against that IP range, and it's registered to M1 Limited our of Singapore.
This company appears to be an ISP, so perhaps that IP range belongs to other users local to you, or these may even be on the same network you're using?
[Edit] Also, by blocking that range, you may be blocking outbound connections from your computer as well.
Saw some type of comments (maybe relating to Windows-Store) about the ?appmage?-format. I did not follow through on where conversation ended. I was particularly interested in whether the 'PortableApps' has an ?"PortableApps.appimage?" format? (to run from Ubuntu)
I also saw somewhere about a ?WineBottler? that would run the ?PorableApp?, but that message seemed to stress that a Wine install was needed to make the PorableApp run.
Did not want to install 'PortableApp' on the Ubuntu-laptop, but run it from USB.
try to read between the lines if terms are incorrect
I have found and installed a better Firewall rule that blocks the range for BitTorrent but allows PortableApps to update. Everything is ok now. My apologies for posting this "non-issue"; I'm not good at Windows system and network management.