serf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SERF-190) Connection does not fall back to IPv4 when missing IPv6 default route
Date Fri, 07 Feb 2020 08:55:00 GMT

    [ https://issues.apache.org/jira/browse/SERF-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032213#comment-17032213
] 

Bert Huijben commented on SERF-190:
-----------------------------------

Thanks. I think we should cover this error code, like a few others where we
fall back.

Quick fix in some scenarios would be to disable the resolving of the
hostname as ipv6. Many nameservers have options to change the order in
which the results are returned.

Bert




> Connection does not fall back to IPv4 when missing IPv6 default route
> ---------------------------------------------------------------------
>
>                 Key: SERF-190
>                 URL: https://issues.apache.org/jira/browse/SERF-190
>             Project: serf
>          Issue Type: Bug
>    Affects Versions: serf-1.3.9
>            Reporter: Petr Menšík
>            Priority: Major
>         Attachments: serf_v6fallback.diff
>
>
> serf and subversion using it will not fall back to IPv4, if IPv6 is enabled on the system
but default IPv6 route leading to target is not available. It should try all addresses obtained
in my opinion, especially from different address families.
> {code:java}
> svn co https://nlnetlabs.nl/svn/unbound/trunk
> svn: E170013: Unable to connect to a repository at URL 'https://nlnetlabs.nl/svn/unbound/trunk'
> svn: E000113: Error running context: No route to host{code}
> Subversion does not have any switch to disable IPv6 and it does not fallback to IPv4.
The latter would be preferred.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message