Droidspaces x OpenWRT x VirtualAP integration!

This is our final goal!

Making the device into a fully functional Wi-Fi router.

VirtualAP is just a middleman whose only purpose is creating the hotspot.

OpenWRT has the full freedom to manage the vaplan0 interface inside its own isolated network namespace, as well as nft/iptables and firewall rules, with DHCP and DNS 🗿

OpenWRT never touches your phone's hardware. No more kernel panics!

Testing:

https://github.com/ravindu644/VirtualAP/releases/tag/v1.4.0

Notes: We'll ship a custom OpenWRT rootfs. Until then, iptables-legacy must be installed inside your OpenWRT container to do this :)

@Droidspaces

New Gateway mode, official OpenWRT rootfs with VirtualAP compatibility, container-to-container networking (OpenWRT manages the networking, not Droidspaces), and more!

It's tinkering time 🍳

CI: https://t.me/DroidspacesCI/521?single

The ultimate flex: an S10 as a fully working Wi-Fi router

Both the PC (via the VirtualAP Droidspaces bridge hotspot) and the Ubuntu container hosting Jellyfin are connected to the OpenWRT container on the same device.

I can access my services using the static IP I assigned to the Ubuntu container via OpenWRT.

I can plug any container I want into my OpenWRT router and manage them individually with their own firewall, DHCP, and DNS configurations, which is insane.

I bet no one ever imagined such complex networking was possible inside Android, while running Android, without Android even noticing, without breaking Android's networking, and under full SELinux enforcing mode.

The cherry on top: with our new "auto boot priority" feature, the OpenWRT container starts first, and then the other gateway containers start second.

This means the networking is fully automated, and you don't even need to unlock the phone to decrypt it.

This is the beauty of Droidspaces :)

You can do the unthinkable.

@Droidspaces