-
Notifications
You must be signed in to change notification settings - Fork 33
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
How to use VEthernet with Tor, Shadowsock,... #6
Comments
If you connect to 127.0.0.1:1080 of the host then tun2socks sends all data to 127.0.0.1:1080. shadowsocks sends all data to the server ip address (assume: 1.1.1.1:7777), then 1.1.1.1:7777 is not configured with the ip route then it will go tun2socks so in fact loopback. You need to add the server ip connected to "shadowsocks" to the system ip route table. Such as add 1.1.1.1 ip route: |
May you support VEthernet with command "-proxy direct://". |
In fact, you can use the existing "--bypass-iplist=./ip.txt"... Configure the shadowsocks server ip address within the ip.txt file. |
Thank you for your support. With tun2socks from xjasonlyu: Devices (TV, phones, ...) -> Wifi router (Adapter Interface) -> Internet connection sharing -> Tun2socks (Proxy mode direct) -> GoodbyeDPI (windivert only modify app, not interface) -> Internet. So may you support that feature ? |
Tor, Shadowsock, Latern, Psiphon,... They open socks proxy on localhost then transfer traffic to internet. They have a loopback connection.
Instead of: Browser -> VEthernet -> Tor -> Internet; then: Browser -> (Tor -> VEthernet; loopback) -> Internet.
So how to use VEthernet with them, and I dont know the command --product=yes it is for what.
The text was updated successfully, but these errors were encountered: