You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@serf.apache.org by "Joe Orton (JIRA)" <ji...@apache.org> on 2019/04/16 10:22:00 UTC
[jira] [Updated] (SERF-190) Connection does not fall back to IPv4
when missing IPv6 default route
[ https://issues.apache.org/jira/browse/SERF-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Orton updated SERF-190:
---------------------------
Attachment: serf_v6fallback.diff
> 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
(v7.6.3#76005)