Skip to content
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

Jump to bottom

--ipv4 not working when using proxy #7345

Closed
shithappens2016 opened this issue Jul 5, 2021 · 3 comments
Closed

--ipv4 not working when using proxy #7345

shithappens2016 opened this issue Jul 5, 2021 · 3 comments
Assignees
@bagder
Labels
connecting & proxies

Comments

@shithappens2016
Copy link

shithappens2016 commented Jul 5, 2021 •
edited

network has both ipv6 & ipv4
--ipv4 wouldn't working when using proxy

curl --ipv4 -x socks4://111.111.111.111:9090  https://www.cloudflare.com

curl still gonna try to connect ipv6 address

end up:

SOCKS4 connection to 2409:8728:5eff:1005:3::3fe not supported
bagder added a commit that referenced this issue Jul 5, 2021
@bagder
socks4: scan for the for IPv4 address in resolve results
b41d0f4 
Follow-up to 84d2839 which changed the resolving to always resolve
both address families, but since SOCKS4 only supports IPv4 it should
scan for and use the first available IPv4 address.

Reported-by: shithappens2016 on github
Fixes #7345
@bagder bagder mentioned this issue Jul 5, 2021
Closed
@bagder
Copy link
Member

bagder commented Jul 5, 2021

Any chance you can try #7346 and see if it fixes the issue for you?

@bagder bagder self-assigned this Jul 5, 2021
@shithappens2016
Copy link
Author

shithappens2016 commented Jul 5, 2021 •
edited

It seems to be OK

@bagder bagder closed this as completed in cffbccd Jul 5, 2021
@bagder
Copy link
Member

bagder commented Jul 5, 2021

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bagder bagder

Labels
connecting & proxies
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

socks4: scan for the for IPv4 address in resolve results curl/curl
2 participants
@bagder @shithappens2016