Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Hotspot always routed #1120

Open
Fabian42 opened this issue Apr 7, 2024 · 3 comments
Open

[BUG] Hotspot always routed #1120

Fabian42 opened this issue Apr 7, 2024 · 3 comments
Labels

Comments

@Fabian42
Copy link

Fabian42 commented Apr 7, 2024

It seems like traffic from other devices using the phone's WLAN hotspot is always routed through Tor, no matter what "Open proxy on all interfaces" is set to.

Either that setting is broken or it means something other than what I interpreted, in which case a new setting for just would be helpful.

  • Device: Shift6mq
  • OS: LineageOS 19, Android 12
  • Version: 16.6.3-RC-1-tor.0.4.7.10 (Tor 0.4.7.10-2-g74a98cc7)
@Fabian42 Fabian42 added the bug label Apr 7, 2024
@n8fr8
Copy link
Member

n8fr8 commented May 7, 2024

The "open proxy" means that the tor daemon's HTTP and SOCKS proxy ports can be accessed from any local IP address.

The hotspot routing over the VPN feature isn't one we have a specific feature to turn off or on. In stock Android, I believe this does NOT happen. It must be a Lineage feature to have the hotspot route over the VPN.

@Fabian42
Copy link
Author

Fabian42 commented May 7, 2024

Oh yeah, "Allow clients to use VPNs" in the system's internet settings! It would still be nice to have a setting for this for Tor specifically, in case I use a different VPN for everything else.

@ghost
Copy link

ghost commented May 15, 2024

Oh yeah, "Allow clients to use VPNs" in the system's internet settings! It would still be nice to have a setting for this for Tor specifically, in case I use a different VPN for everything else.

To the best of my knowledge, in stock AOSP, this is not provided to user applications via any API.

Likely it would have to use root to temporary enable/disable this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants