Bug description
Enabling SOCKS5 Auth (username + password) in profile settings completely breaks internet connectivity in TUN/VPN mode.
Traffic stops entirely after connection.
SOCKS5 Proxy mode works correctly with authentication.
Steps to reproduce
Create or edit a profile
Enable SOCKS5 Auth and enter username/password
Connect in TUN mode (system VPN)
No internet / no traffic
Root cause
In TUN mode traffic flows:
Android TUN → gVisor netstack → tun2socks → internal SOCKS5 listener.
When SOCKS5_AUTH = true, the listener requires credentials, but the internal SOCKS5 dialer in the Android bridge does not forward SOCKS5_USER / SOCKS5_PASS.
Proposed fix
Update the SOCKS5 client/dialer creation inside the Android Go bridge (cmd/android + tun2socks integration) to properly pass username and password when authentication is enabled.
Bug description
Enabling SOCKS5 Auth (username + password) in profile settings completely breaks internet connectivity in TUN/VPN mode.
Traffic stops entirely after connection.
SOCKS5 Proxy mode works correctly with authentication.
Steps to reproduce
Create or edit a profile
Enable SOCKS5 Auth and enter username/password
Connect in TUN mode (system VPN)
No internet / no traffic
Root cause
In TUN mode traffic flows:
Android TUN → gVisor netstack → tun2socks → internal SOCKS5 listener.
When SOCKS5_AUTH = true, the listener requires credentials, but the internal SOCKS5 dialer in the Android bridge does not forward SOCKS5_USER / SOCKS5_PASS.
Proposed fix
Update the SOCKS5 client/dialer creation inside the Android Go bridge (cmd/android + tun2socks integration) to properly pass username and password when authentication is enabled.