serf-dev mailing list archives

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

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

Gleb Smirnoff commented on SERF-190:
------------------------------------

Same problem on FreeBSD:

>svn up
Updating '.':
svn: E170013: Unable to connect to a repository at URL 'https://svn.openstreetmap.org/applications/editors/josm'
svn: E000047: Error running context: Address family not supported by protocol family

Error comes from serf because the kernel is compiled without IPv6 support.

Error code EAFNOSUPPORT should also be covered.

 

> 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