-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
After building the binary, run the socks server with
./socks --addr :26480 --user-auth [REDACTED] --password [ALSO REDACTED] --country "United States"
It should open a socks server, listening on 26480 both on 127.0.0.1 and ::1 (it did)
When fetching through ipv4:
http_proxy=socks5://localhost:26480 https_proxy=socks5://localhost:26480 curl -4 ip.sb
It works fine, returning a ip which indicates that the traffic do go through the vpn network.
Howver, when fetching through ipv6:
http_proxy=socks5://localhost:26480 https_proxy=socks5://localhost:26480 curl -6 ip.sb
It returns
curl: (97) cannot complete SOCKS5 connection to ip.sb. (4)
The following is the console log of the socks proxy:
socks5 server is listening on :26480
Dialing tcp [2606:4700:20::681a:d1f]:80
socks5: 2025/04/29 19:07:41 [E]: server: connect to [2606:4700:20::681a:d1f]:80 failed, connect tcp [2606:4700:20::681a:d1f]:80: no route to host
Dialing tcp [2606:4700:20::681a:c1f]:80
socks5: 2025/04/29 19:07:43 [E]: server: connect to [2606:4700:20::681a:c1f]:80 failed, connect tcp [2606:4700:20::681a:c1f]:80: no route to host
which indicates that seems ipv6 is not properly supported.
(Need to note that ip.sb by default resolve to a ipv6 address, so it's not caused by the website's lack of ipv6 support. Any sites supported ipv6 should share the same problem with it.)
Metadata
Metadata
Assignees
Labels
No labels