[
https://issues.apache.org/jira/browse/SERF-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397746#comment-17397746
]
Justin Erenkrantz commented on SERF-190:
----------------------------------------
Does applying the attached patch resolve the issue?
If I understand the use case, a machine that is configured for IPv6 interface
but doesn’t have IPv6 working but the dual stack falls back to IPv4 on a reset?
In reading the patch, it’s not clear how we would be retrying to do only IPv4
on a subsequent connect.
> 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)
