-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
Routing failure when connecting to IPv6 address because of wrong default network interface #8802
Comments
~~ Can you try to append the interface (such as |
Replying to [comment:5 dkocher]:
|
I cannot reproduce this issue. Please share more details of your setup to reproduce. |
Replying to [comment:8 dkocher]:
See this Screencast: In the video I show you that I can successfully 'ping6 ftp6.netbsd.org' and 'ftp ftp6.netbsd.org', but in Cyberduck the result to the same server is always: 'No route to host'. This is just an example, it is like that for any IPv6 only host on internet. Hope this helps. |
This looks to be an issue with the wrong default interface being selected. On my machine if I disable
|
Some reference
|
Great! I will test it as soon as the snapshot build arrives. |
Replying to [comment:16 richardvd]:
|
I just installed the latest snapshot version 4.8 (17573). No change, it still results in 'no route to host' in this situation. It does work after |
Can you post the output of |
In case you still want to see my
I look forward to you next snapshot release! |
I think my above change cf832b4 will unfortunately make no difference given the |
No change unfortunately for this case. This is the debug logging output of Version 4.8 (17592):
The above is all logged before I try to connect. Nothing extra is added to the log when the 'no route to host' error appears. |
Debug logging is not enabled. Please try
and restart Cyberduck.app. |
I double checked it, debug logging is enabled:
And of course I already did ⌘-Q and then restarted and verified the version number (17592). The debug setting does work, because if I delete the logging key, then it logs nothing on startup. So debug logging is enabled and working as far as I can tell, the error just doesn't seem to follow the code path you expect it to. :-) |
Replying to [comment:29 dkocher]:
|
Snapshot release 17649 logs:
Now the error in the popup has changed from 'no route to host' to 'already connected'. |
Confirmed working in d8613dd, thanks a lot! Connecting to IPv6-only hosts is now possible using Cyberduck, but there are still cases where it won't work. For the other cases I have opened [8848 ticket 8848] to keep this ticket clean. |
I'm still having the same problem with Cyberduck 4.8.4 and 5.0 (fca29aa). Dual-stack connected mac, trying to connect to host with IPv4 and IPv6 address, both in DNS. By preferring IPv6 using "defaults write ch.sudo.cyberduck connection.dns.ipv6 true" the connection always gives "No route to host". This is because it again selects awdl0 as the interface to use.
|
Replying to [comment:39 peterf]:
Thanks for the perfect regression test! We will look into this again. |
You should see a log statement
|
Connection to an IPv6-only server is impossible when using the Mac version. The result is always: 'No route to host'.
I can ping6 the IPv6 server, so there is a working route.
Additional information:
The text was updated successfully, but these errors were encountered: