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
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
🔥21❤8👏1
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
It's tinkering time 🍳
CI: https://t.me/DroidspacesCI/521?single
❤11❤🔥3🔥2
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
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
🔥22❤6🗿5
You guys ready for the next release?
I cannot find any issues anymore. Everything seems stable.
I want your guys' help to test this CI:
https://t.me/DroidspacesCI/565?single
Basically, the only things that need to be tested are:
1. NAT mode - mandatory upstream interfaces are gone. Everything is automated.
Additionally, we introduced Pinned upstream mode, which basically allows you to pin the container WAN side to the interface(s) you like.
Let's say you enabled both Wi-Fi and Mobile Data, but you want your container to pull the internet only from the mobile data: this feature is for you.
2. Gateway mode (this needs some networking knowledge to tell OpenWrt to manage the plugged virtual switch via the eth1 interface inside OpenWrt).
The client containers are plugged into the virtual switch. Exactly how a physical switch behaves.
I cannot find any issues anymore. Everything seems stable.
I want your guys' help to test this CI:
https://t.me/DroidspacesCI/565?single
Basically, the only things that need to be tested are:
1. NAT mode - mandatory upstream interfaces are gone. Everything is automated.
Additionally, we introduced Pinned upstream mode, which basically allows you to pin the container WAN side to the interface(s) you like.
Let's say you enabled both Wi-Fi and Mobile Data, but you want your container to pull the internet only from the mobile data: this feature is for you.
2. Gateway mode (this needs some networking knowledge to tell OpenWrt to manage the plugged virtual switch via the eth1 interface inside OpenWrt).
The client containers are plugged into the virtual switch. Exactly how a physical switch behaves.
❤17👌1
Droidspaces v6.4.0 has been released! 🥳
Plus the usual round of translation updates, UI polish, and under-the-hood refactoring.
Full Changelog and Downloads:
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v6.4.0
@Droidspaces
- net: Virtual router support (Gateway mode)
- net: detect the internet uplink automatically instead of forcing the users asking an "upstream interface"
- net: configure --upstream to pin NAT WAN to specific interface(s)
- net: fix port forwards being unreachable from hotspot/USB-tether clients
- feat: add auto-boot priority ordering for gateway networking mode
- net: unify /etc/resolv.conf wiring, fix gateway-mode DNS
- app: add OpenWrt procd service management
- build: add Debian package artifact generation
- app: trim and collapse whitespace in container names
- selinux: fix permission denied when read/write mounted storage
- mount: don't force a full e2fsck on every container start (improves container boot time)
- net: re-assert ip_forward on every platform, not just Android
- app: fix Panel tab polling not resuming after returning from background
- mount: force image rootfs read-write before pivot_root (fixes openwrt internal reboot!)
Plus the usual round of translation updates, UI polish, and under-the-hood refactoring.
Full Changelog and Downloads:
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v6.4.0
@Droidspaces
Please open Telegram to view this post
VIEW IN TELEGRAM
❤15🔥5🎉4
Please open Telegram to view this post
VIEW IN TELEGRAM
😁23🗿5👻4😱3❤2👌1