The Problem:
When connecting a secondary Wi-Fi adapter (wlan1) to guest/venue Wi-Fi networks with captive portals, there is no easy way to trigger and approve the splash page from a phone connected to the BELABOX AP (wlan0).
Proposed Solution:
A simple "SOCKS5 Proxy for Guest Login" toggle in the Network tab of belaUI.
Implementation:
Enabling the toggle could spin up a lightweight daemon (like microsocks on port 1080). Streamers can then point their phone's proxy settings to the BELABOX IP (10.42.0.1:1080) to open browser splash pages, approve the venue terms using the BELABOX MAC address, and then turn the proxy back off if they wish.
Why SOCKS5 over NAT:
A SOCKS5 daemon is lightweight, doesn't tamper with iptables or system routing tables, and won't interfere with srtla multi-interface bonding.
This would be a really handy feature and cost saving when visiting events and revenues like Twitch Con. ❤️
The Problem:
When connecting a secondary Wi-Fi adapter (wlan1) to guest/venue Wi-Fi networks with captive portals, there is no easy way to trigger and approve the splash page from a phone connected to the BELABOX AP (wlan0).
Proposed Solution:
A simple "SOCKS5 Proxy for Guest Login" toggle in the Network tab of belaUI.
Implementation:
Enabling the toggle could spin up a lightweight daemon (like microsocks on port 1080). Streamers can then point their phone's proxy settings to the BELABOX IP (10.42.0.1:1080) to open browser splash pages, approve the venue terms using the BELABOX MAC address, and then turn the proxy back off if they wish.
Why SOCKS5 over NAT:
A SOCKS5 daemon is lightweight, doesn't tamper with iptables or system routing tables, and won't interfere with srtla multi-interface bonding.
This would be a really handy feature and cost saving when visiting events and revenues like Twitch Con. ❤️