We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The application should not "Fail" when "Good" configuration is used.
Background:
To Reproduce Steps to reproduce the behavior:
iptables -t nat -A PREROUTING -i ens9f1 -p tcp -j REDIRECT --to-port 12345 iptables -t nat -A PREROUTING -i ens9f1 -p udp -j REDIRECT --to-port 12345 iptables -t nat -A POSTROUTING -o ens9f1 -j MASQUERADE iptables -t nat -L
iptables -t nat -A PREROUTING -i ens9f1 -p tcp -j REDIRECT --to-port 12345
iptables -t nat -A PREROUTING -i ens9f1 -p udp -j REDIRECT --to-port 12345
iptables -t nat -A POSTROUTING -o ens9f1 -j MASQUERADE
iptables -t nat -L
Listen on ens9f1 on port 12345 and forward out socks requests to 10.10.10.138:58888 : go-shadowsocks2 -verbose -c '10.10.10.138:58888' -socks ':12345'
Flow TCP traffic from another PC attached to ens9f1 as gateway.
each flow creates error.
"2024/01/30 02:22:32 tcp.go:67: failed to get target address: SOCKS error: 8"
Expected behavior
go-shadowsocks2 -verbose -c '10.10.10.138:58888' -socks ':12345' 2024/01/30 02:22:24 tcp.go:18: SOCKS proxy :12345 <-> 10.10.10.138:58888 2024/01/30 02:22:25 tcp.go:18: SOCKS proxy :12345 <-> 10.10.10.138:58888 - Connected ???
go-shadowsocks2 -verbose -c '10.10.10.138:58888' -socks ':12345'
2024/01/30 02:22:24 tcp.go:18: SOCKS proxy :12345 <-> 10.10.10.138:58888
2024/01/30 02:22:25 tcp.go:18: SOCKS proxy :12345 <-> 10.10.10.138:58888 - Connected ???
Unexpected go-shadowsocks2 -verbose -c '10.10.10.138:58888' -socks ':12345' 2024/01/30 02:22:24 tcp.go:18: SOCKS proxy :12345 <-> 10.10.10.138:58888 2024/01/30 02:22:32 tcp.go:67: failed to get target address: SOCKS error: 8 socks.pcap.zip
2024/01/30 02:22:32 tcp.go:67: failed to get target address: SOCKS error: 8
Screenshots
Desktop (please complete the following information):
Please let me know if anything more is needed.
I also tried -redir in replacement of -socks
go-shadowsocks2 -verbose -c '10.10.10.138:58888' -redir ':12345' 2024/01/30 02:33:49 tcp_linux.go:20: TCP redirect :12345 <-> 10.10.10.138:58888 2024/01/30 02:33:55 tcp.go:87: proxy 192.168.12.5:58041 <-> 10.10.10.138:58888 <-> 192.168.222.130:443 2024/01/30 02:33:55 tcp.go:87: proxy 192.168.12.5:58040 <-> 10.10.10.138:58888 <-> 192.168.222.130:443 2024/01/30 02:33:56 tcp.go:87: proxy 192.168.12.5:58042 <-> 10.10.10.138:58888 <-> 192.168.222.130:443 2024/01/30 02:33:57 tcp.go:87: proxy 192.168.12.5:58043 <-> 10.10.10.138:58888 <-> 192.168.222.130:443 redir.pcap.zip
but getting a relay error as suspected not being socks5 ...
The text was updated successfully, but these errors were encountered:
I'm having the same type of issue
go-shadowsocks2 -verbose -c 'socks4://10.10.10.10:58888' ... go-shadowsocks2 -verbose -c 'socks5://10.10.10.10:58888' ... go-shadowsocks2 -verbose -c 'socks5://abc:[email protected]:58888' ...
All of the above we may expect to work but fails, please help?
Sorry, something went wrong.
I also ecountered this problem, i tried both on win10 and centos, my command is
go-shadowsocks2 -c "ss://AEAD_CHACHA20_POLY1305:password@host:8488" -verbose -socks :1080
2024/11/10 16:50:12 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:12 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:12 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:12 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8 2024/11/10 16:50:17 tcp.go:67: failed to get target address: SOCKS error: 8
No branches or pull requests
Describe the bug
The application should not "Fail" when "Good" configuration is used.
Background:
( All ^^^ installed today, latest release. )
3 ens9f0 Internet
4 ens9f1 IP no rougting
To Reproduce
Steps to reproduce the behavior:
iptables -t nat -A PREROUTING -i ens9f1 -p tcp -j REDIRECT --to-port 12345
iptables -t nat -A PREROUTING -i ens9f1 -p udp -j REDIRECT --to-port 12345
iptables -t nat -A POSTROUTING -o ens9f1 -j MASQUERADE
iptables -t nat -L
Listen on ens9f1 on port 12345 and forward out socks requests to 10.10.10.138:58888 :
go-shadowsocks2 -verbose -c '10.10.10.138:58888' -socks ':12345'
Flow TCP traffic from another PC attached to ens9f1 as gateway.
each flow creates error.
"2024/01/30 02:22:32 tcp.go:67: failed to get target address: SOCKS error: 8"
Expected behavior
go-shadowsocks2 -verbose -c '10.10.10.138:58888' -socks ':12345'
2024/01/30 02:22:24 tcp.go:18: SOCKS proxy :12345 <-> 10.10.10.138:58888
2024/01/30 02:22:25 tcp.go:18: SOCKS proxy :12345 <-> 10.10.10.138:58888 - Connected ???
Unexpected
go-shadowsocks2 -verbose -c '10.10.10.138:58888' -socks ':12345'
2024/01/30 02:22:24 tcp.go:18: SOCKS proxy :12345 <-> 10.10.10.138:58888
2024/01/30 02:22:32 tcp.go:67: failed to get target address: SOCKS error: 8
socks.pcap.zip
Screenshots
Desktop (please complete the following information):
Please let me know if anything more is needed.
I also tried -redir in replacement of -socks
go-shadowsocks2 -verbose -c '10.10.10.138:58888' -redir ':12345'
2024/01/30 02:33:49 tcp_linux.go:20: TCP redirect :12345 <-> 10.10.10.138:58888
2024/01/30 02:33:55 tcp.go:87: proxy 192.168.12.5:58041 <-> 10.10.10.138:58888 <-> 192.168.222.130:443
2024/01/30 02:33:55 tcp.go:87: proxy 192.168.12.5:58040 <-> 10.10.10.138:58888 <-> 192.168.222.130:443
2024/01/30 02:33:56 tcp.go:87: proxy 192.168.12.5:58042 <-> 10.10.10.138:58888 <-> 192.168.222.130:443
2024/01/30 02:33:57 tcp.go:87: proxy 192.168.12.5:58043 <-> 10.10.10.138:58888 <-> 192.168.222.130:443
redir.pcap.zip
but getting a relay error as suspected not being socks5 ...
The text was updated successfully, but these errors were encountered: