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

IPv6 reachable servers time out with wrong utun* interface selected #10469

Closed
cyberduck opened this issue Sep 22, 2018 · 5 comments
Closed

IPv6 reachable servers time out with wrong utun* interface selected #10469

cyberduck opened this issue Sep 22, 2018 · 5 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Sep 22, 2018

003e8e7 created the issue

Trying to access a server with DNS resolution of AAAA records with IPv6 address results in a connection timeout. Same if we specify the IPv6 address directly. Accessing the same server via its IPv4 address works fine. Nothing is recorded in the log drawer...

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 5, 2018

@ylangisc commented

I was unable to replicate the issue with Google Drive on Mojave when specifying 2607:f8b0:4007:804::200a for www.googleapis.com as hostname in the bookmark. Can you provide the IPv6 address if your server publicly reachable?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 5, 2018

003e8e7 commented

We cannot sftp 2001:470:1f0b:7df:12dd:b1ff:febd:6a5d, timing out with cyberduck. If we use sftp/ssh from the command line or other apps on the same machine in the same network everything works fine.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 30, 2018

003e8e7 commented

We have done a bit more research. In general other sftp clients like "Transmit" work without any problems on the same mac os x machine and the same user account. IPv6 connections are only a problem in cyberduck!

During our research we found ticket #8848... It was resolved by putting utun0 on a blacklist of interfaces.

Our machine also implements utun1-utun4 interfaces. So after removing these interfaces the behaviour changes. We do not get timeouts anymore but "no route to host errors" immediately. It looks like cyberduck is still trying to use an interface with no internet connectivity.

Is there a way to specify the interface cyberduck should use for connections?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 22, 2018

@dkocher commented

As a workaround you could try to modify the default blacklist of interfaces using

defaults write ch.sudo.cyberduck network.interface.blacklist awdl0 utun0 utun1 utun2 utun3 utun4

@cyberduck
Copy link
Collaborator Author

cyberduck commented Aug 20, 2019

@ylangisc commented

Fixed in 8ac652e.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants