Redirecting 192.168.49.1 Traffic to 192.168.0.X

[Zig-VS-TypeScript-VS]

~~Allow custom editing of Proxy URL/hostname~~

~~The IP address assigned by the Wi‑Fi router.~~ ~~> 192.168.0.X~~ ~~192.168.1.X~~

---

https://github.com/sequentialread/AndroidSocks5Proxy Redirecting 192.168.49.1:8228 Traffic to 192.168.0.X:8228

Operation Steps

1. Mobile device IP: 192.168.0.100
2. Enable tetherfi: 192.168.49.1:8228

Redirect traffic from 192.168.49.1:8228 to 192.168.0.100:8228

3. Enter proxy settings in Windows 10: 192.168.0.100:8228

[pyamsoft]

Hello

Unfortunately this is not possible, as the DHCP distribution of addresses is controlled by a low level part of the WiFi Direct implementation on Android. As a third party app, I do not have access to control this part, unless new APIs have been added recently.

I will double check, but sadly, I do not believe this is something a third party app can do :(

[Zig-VS-TypeScript-VS]

hello @pyamsoft https://github.com/sequentialread/AndroidSocks5Proxy The traffic from 192.168.49.1:8228 can be forwarded to 192.168.0.X:8228 on the LAN?

Operation Steps

1. Mobile device IP: 192.168.0.100
2. Enable tetherfi: 192.168.49.1:8228

Redirect traffic from 192.168.49.1:8228 to 192.168.0.100:8228

3. Enter proxy settings in Windows 10: 192.168.0.100:8228

[pyamsoft]

At an application level I can't control SNAT or DNAT so this isn't possible sadly, to my knowledge at least.

What I could possibly do is bind the Proxy server to the 0 address on all interfaces, and then you may be able to directly access it from 0.100

[Zig-VS-TypeScript-VS]

What I could possibly do is bind the Proxy server to the 0 address on all interfaces, and then you may be able to directly access it from 0.100

Cool