| This is likely an issue with interface/address selection and I can confirm this happens, but does not prevent connections. May only occur with IPv6 and/or TCP or UDP. |
|
| I think this can happen when the router blocks outgoing IPv6 traffic. I assume in such a case it should be detected by the communicator and automatically disable its IPv6 functionality (or at least tell the transport service, there's no need to forward IPv6 addresses to it for opening connections because it simply does not work). If it can be detected by the communicator, it should also be possible to re-enable it (if not explicitly disabled via configuration). |
|
| Did you fix this with the last commits made to master? |
|
| No, this isn't fixed yet. |
|
| I'm not sure if we should handle "network is unreachable" errors. Those are networks/system misconfigurations that the user/admin is the only person able to fix that. |
|
| Maybe we could workaround this at least to reduce such errors. If IPv4 and IPv6 were separated acting as own communicators and transport would be rating communicators on a rate of successful connections, transport could at least understand if there are issues with some protocol and default to use a different communicator if possible to make connections to a certain peer. |
|
| That may be a good idea. In that process, I would also support having a communicator that does not do any encryption as fallback. Can you please create a new issue for the IPv4/IPv4 separation? Then I will close this. |
|
| You are right. IPv6 is not configured on my host and network. Thank you for the hint! |
|
| Related bug 0009263 is better suited to track this issue. |
|
| Released |
|