This media is not supported in your browser
VIEW IN TELEGRAM
Networking is unkillable now 🗿
100% uptime.
Even if you enable or disable Wi-Fi, data, or hotspot thousands of times,
no worries!
The Droidspaces daemon will perfectly handle everything in the background 🗿
100% uptime.
Even if you enable or disable Wi-Fi, data, or hotspot thousands of times,
no worries!
The Droidspaces daemon will perfectly handle everything in the background 🗿
🗿4❤1
This is how Port Forwarding Works in NAT Mode
When a container runs in NAT mode, its network is completely isolated with a private IP (like
Port forwarding solves this by creating a mapping between a port on the phone's own IP (which IS visible to your local network) and a port inside the container.
For example, mapping phone port 22 → container port 22 means:
When someone on your network SSHes into <phone-ip>:22, the phone intercepts that connection and transparently forwards it into the container - as if the container were directly reachable.
The container itself never needs a public IP. The phone acts as the gateway.
When a container runs in NAT mode, its network is completely isolated with a private IP (like
172.28.33.133) that only the phone knows about. Other devices on your local network - and even your router - have no idea this private network exists, so trying to SSH directly into the container's IP from another device will simply fail.Port forwarding solves this by creating a mapping between a port on the phone's own IP (which IS visible to your local network) and a port inside the container.
For example, mapping phone port 22 → container port 22 means:
Another Device ──► Router ──► Phone (your real IP) ──► Container (172.28.x.x)When someone on your network SSHes into <phone-ip>:22, the phone intercepts that connection and transparently forwards it into the container - as if the container were directly reachable.
The container itself never needs a public IP. The phone acts as the gateway.
Droidspaces v5.3.0-pre-release
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.3.0-pre-release
This will be the last release from the
What's in this release:
- Universal, fully working network isolation, with a DHCP server for assigning IPs AND a daemon that watches network changes in real time to ensure 99.999% uptime. Works on both Android and Linux - tested on kernels 4.14 to 6.19 🗿
- Cgroups won't be isolated on kernels lower than 5.2. This makes it possible to run Ubuntu 24.04 and other semi-modern distros on older kernels with 100% compatibility. I'm literally running Ubuntu 24.04 with 100% systemd health on my old 4.14.113 kernel.
- Fixed CTRL+ALT+Q tends to reboot in foreground mode.
- More misc. improvements that I can't remember.
Notes: The upstream interface is the interface that has internet access, such as
Connect to Wi-Fi → Select the interface that appears → Disable Wi-Fi and connect to mobile data → Press the refresh button in that menu → Select the interface(s) that appear.
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.3.0-pre-release
This will be the last release from the
network-isolation branch. Once you guys test everything and confirm it’s working, I’m going to merge network isolation into the main branch and take a break from development for a while 😇What's in this release:
- Universal, fully working network isolation, with a DHCP server for assigning IPs AND a daemon that watches network changes in real time to ensure 99.999% uptime. Works on both Android and Linux - tested on kernels 4.14 to 6.19 🗿
- Cgroups won't be isolated on kernels lower than 5.2. This makes it possible to run Ubuntu 24.04 and other semi-modern distros on older kernels with 100% compatibility. I'm literally running Ubuntu 24.04 with 100% systemd health on my old 4.14.113 kernel.
- Fixed CTRL+ALT+Q tends to reboot in foreground mode.
- More misc. improvements that I can't remember.
Notes: The upstream interface is the interface that has internet access, such as
wlan0 or rmnet0. The app can auto-detect upstream networks - all you need to do is:Connect to Wi-Fi → Select the interface that appears → Disable Wi-Fi and connect to mobile data → Press the refresh button in that menu → Select the interface(s) that appear.
🔥1🗿1
New release with new fixes:
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.3.1-pre-release
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.3.1-pre-release
GitHub
Release Droidspaces v5.3.1-pre-release · ravindu644/Droidspaces-OSS
What's Changed
docs: Add a new row to the comparison table detailing network isolation capabilities. (23f7083)
docs: Add troubleshooting for NAT mode internet access with IPv6-only upstream. (...
docs: Add a new row to the comparison table detailing network isolation capabilities. (23f7083)
docs: Add troubleshooting for NAT mode internet access with IPv6-only upstream. (...
Thanks to the latest changes around cgroups in Droidspaces,
legacy kernel users can now run relatively modern Systemd on older kernels like 4.14 as well..!
As you can see in this screenshot, I'm running Ubuntu 25.04 without any issues - 0 failed units, no "Operation not permitted", or "Function not implemented" type of nonsense.
So basically, you can run anything below Systemd v258, since they nuked the legacy code for older kernels there, which specifically blocks legacy kernels in the first place 🤡
legacy kernel users can now run relatively modern Systemd on older kernels like 4.14 as well..!
As you can see in this screenshot, I'm running Ubuntu 25.04 without any issues - 0 failed units, no "Operation not permitted", or "Function not implemented" type of nonsense.
So basically, you can run anything below Systemd v258, since they nuked the legacy code for older kernels there, which specifically blocks legacy kernels in the first place 🤡
❤2
Added the ability to completely lift the cgroup v1 restriction, even on older kernels, so users aren’t artificially blocked from using cgroup v2 🗿
Droidspaces v5.4.2-hotfix
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.4.2-hotfix
this release fixes:
- "Operation not permitted" ping failure in NAT mode
- Running
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.4.2-hotfix
this release fixes:
- "Operation not permitted" ping failure in NAT mode
- Running
login from terminating the shell when using the droidspaces enter modeAs the project is now stable,
I'm stepping back from Droidspaces development until September 2026.
I need to focus the next five months on my studies.
If you encounter any bugs, please report them before 10 PM GMT+5:30.
The
I'm stepping back from Droidspaces development until September 2026.
I need to focus the next five months on my studies.
If you encounter any bugs, please report them before 10 PM GMT+5:30.
The
final-net-isolation branch will be merged into the main branch as it is stable, and the project will remain on my GitHub for some time.❤5👍2
Droidspaces
Droidspaces v5.4.2-hotfix https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.4.2-hotfix this release fixes: - "Operation not permitted" ping failure in NAT mode - Running login from terminating the shell when using the droidspaces enter mode
Hotfix for this issue in the app:
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.4.2-hotfix
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.4.2-hotfix
👏1
Droidspaces
Thanks to the latest changes around cgroups in Droidspaces, legacy kernel users can now run relatively modern Systemd on older kernels like 4.14 as well..! As you can see in this screenshot, I'm running Ubuntu 25.04 without any issues - 0 failed units, no…
Ubuntu 25.10 is barely working with 0 failed units on an older Linux 4.14.113 💀
Even this setup is currently stable "for now" - if Ubuntu releases a systemd update that upgrades systemd to v258+, the container will be cooked.
All of this is currently possible because, as of 2026-03-09, Ubuntu 25.10 uses systemd v257.9.
Only 0.1 more is needed to turn the container into a paperweight.
Even this setup is currently stable "for now" - if Ubuntu releases a systemd update that upgrades systemd to v258+, the container will be cooked.
All of this is currently possible because, as of 2026-03-09, Ubuntu 25.10 uses systemd v257.9.
Only 0.1 more is needed to turn the container into a paperweight.
😱1