worstperson

Seems like my kernel is not built with ipv6 nat support, so even running a transparent proxy is out of the question. Still have hope bridging might work. VPN clients...

Quickly found that bridging is also not possible, not without compiling tap support into the kernel and using native clients. Just going to post my test script that I used...

It supports IPV6 tethering the correct way, each tethered device receives a unique address from the provider. This is clearly undesirable as any traffic through those addresses is defacto tethering...

Think I answered poorly. AFAICT public ipv6 addresses for tethered clients are configured via slaac server on the provider side, not anything on the client side. Guess this would be...

Ideally rom and kernel maintainers will pick up on this use case and start building with these options. At the very least it could save advanced users a bunch of...

Finally stumbled on how this can be done, I feel really dumb for not landing on this sooner. Turns out we can use TPROXY mangle rules to capture and redirect...

Sorry for the extremely late reply. https://github.com/heiher/hev-socks5-server https://github.com/heiher/hev-socks5-tproxy The last line in Android.mk for hev-socks5-tproxy is set to 'BUILD_SHARED_LIBRARY', change to 'BUILD_EXECUTABLE'. Both projects crash on localtime calls for me,...

It's possible to do it like this, in this case I'm usb tethering wlan0 and routing one client through a VPN: ``` # Allow traffic between rndis0 and tun0, but...

This is an example of redirecting DHCP requests to your own instance of Dnsmasq serving on a non-standard port, in this case for usb tethering. This lets you set any...

Below "Edit:", I had fixed it by setting the DNS port to avoid conflicting and added a rule to point traffic to it.