-
Notifications
You must be signed in to change notification settings - Fork 144
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
proxy forwarding not working #3
Comments
what is your proxy software? what type is the proxy? this script require the proxy supports transparent proxy. have you tried redirecting all traffic to your proxy not just port 80? |
after many hours... I was able to get it working with sshuttle # Create new chain
iptables -t nat -N REDSOCKS
# Everything should be redirected to port 12345
iptables -t nat -A REDSOCKS -p tcp -j REDIRECT --to-ports 12345
# Any tcp connection made by `root' should be redirected.
iptables -t nat -A OUTPUT -p tcp -m owner --uid-owner root -j REDSOCKS still would love your help to get it working without sshuttle thank you |
As I remember, iptables doesn't support redirecting to SOCKS proxy. I have tried
I guess your proxy does special treatment on web requests. Did you test ports and protocols other than web? If yes, maybe it really supports transparent proxy. Besides there's a program called
|
Also found these tools useful: |
my setup is as following I believe my issue is somewhere with |
thank you for your awesome effort in putting the script together.
I am trying to test with AP and PROXY. AP works fine with following command
./lnxrouter -o eth0 --ap wlan0 AP_NAME --password AP_PASS
, I am able to connect my android device and internet is working. When I try to launch with--tp PORT
option my phone no longer gets internet.I have validated my redsocks is setup properly by following steps
iptables -t nat -A OUTPUT -p tcp --dport 80 -j REDIRECT --to-port 12345
curl http://yahoo.com
in redsocks logs I see curl is making connection.
I am using
Ubuntu Server
on VM Ware Fusion on Maclsb_release -a
The text was updated successfully, but these errors were encountered: