No auto-discovery of Kolibri peers in Ubuntu 16.04.6

Observed behavior

Installed Kolibri v0.13.2-beta1 in two Ubuntu 16.04.6 VMs and when trying to import content from “Local network or internet” each other. The auto-discovery of Kolibri peers did not work.

Setup:

• I have 2 VMs running both with channel contents for importing.
• Both VMs have gufw (graphical firewall in Ubuntu) installed and have allowed incoming/outgoing network traffic .
• I tried auto-discovery first without gufw but that didn’t work. Thus I installed it to specifically allow network traffic.

Screenshot of the two VMs (a .gif would have been better but it’s >10MB):

Expected behavior

Auto-discovery of Kolibri peers to work without having to manually input the Kolibri server IP and port.

There’s already a warning in the Channels and Resources documentation regarding “inability to discover other peers”, etc.

Steps to reproduce

1. Setup two Ubuntu 16.04.6 VMs, with bridged networking.
2. Install kolibri v0.13.2-beta1
3. Attempt to do the “Import from Local network or internet” task

Context

• Kolibri version: kolibri v0.13.2-beta1
• Operating system: VM Ubuntu 16.04.6 Desktop, 4GB RAM, 2 CPUs, 768 Video RAM, 64GB disk
• Browser: Firefox v74 (default of Ubuntu)

Note/s:

• I recorded a .gif of the two VMs but cannot import it here due to the 10MB limit of Github, it is about 32MB. Will try another later.

[radinamatic]

Did some more digging, and on Windows 10 you need to explicitly allow both Python and kolibri.exe through the firewall, to be able to add a peer for import. Auto-discovery will still not work, but at least you can add the peer IP manually, it will be saved and import enabled.

[radinamatic]

Agreed, these Windows details will be added in the next docs update!