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

connect: store IPv6 connection status after valid connection #2053

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
2 participants
@bagder
Member

bagder commented Nov 4, 2017

... previously it would store it already in the happy eyeballs stage
which could lead to the IPv6 bit being set for an IPv4 connection,
leading to curl not wanting to do EPSV=>PASV for FTP transfers.

connect: store IPv6 connection status after valid connection
... previously it would store it already in the happy eyeballs stage
which could lead to the IPv6 bit being set for an IPv4 connection,
leading to curl not wanting to do EPSV=>PASV for FTP transfers.

@bagder bagder closed this in 6b12beb Nov 9, 2017

@bagder bagder deleted the bagder/connection-ipv6 branch Nov 9, 2017

@waltw

This comment has been minimized.

Show comment
Hide comment
@waltw

waltw Apr 13, 2018

I am seeing a similar issue sending https requests on Android. I start sending requests over mobile cell data link with wi-fi disabled to an ipv6 server endpoint.. I enable wi-fi and set CURLOPT_INTERFACE to "wlan0". Requests continue to go, now over wifi as ipv4 packets.

As soon as Linux declares the mobile data link dormant, and disconnects, requests over wi-fi begin to fail with CURLE_COULDNT_CONNECT (7). tcpdump shows all traffic to and from the server endpoint has stopped.

I thought this bug sounded like the issue I'm seeing, but implementing this fix didn't help. I am using libcurl 7.43.0. I didn't see any other issues that sounded ike mine so I have held off upgrading to the newest release.

Anyone have any thoughts or suggestions?

waltw commented Apr 13, 2018

I am seeing a similar issue sending https requests on Android. I start sending requests over mobile cell data link with wi-fi disabled to an ipv6 server endpoint.. I enable wi-fi and set CURLOPT_INTERFACE to "wlan0". Requests continue to go, now over wifi as ipv4 packets.

As soon as Linux declares the mobile data link dormant, and disconnects, requests over wi-fi begin to fail with CURLE_COULDNT_CONNECT (7). tcpdump shows all traffic to and from the server endpoint has stopped.

I thought this bug sounded like the issue I'm seeing, but implementing this fix didn't help. I am using libcurl 7.43.0. I didn't see any other issues that sounded ike mine so I have held off upgrading to the newest release.

Anyone have any thoughts or suggestions?

@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018

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