couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Stapelberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-665) Replication not possible via IPv6
Date Wed, 16 Mar 2011 17:51:34 GMT

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

Michael Stapelberg commented on COUCHDB-665:
--------------------------------------------

You *do* have easy access to an IPv6 environment, just install miredo and you’ll automatically
have a working IPv6 tunnel within seconds (provided you’re not behind some very restrictive
firewall).

An alternative would be to configure the IPv6 addresses statically between two computers (or
between to instances of CouchDB running on different IPs), chosen from the unique local addresses
prefix or some example prefix.

> Replication not  possible via IPv6
> ----------------------------------
>
>                 Key: COUCHDB-665
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-665
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core, Replication
>    Affects Versions: 0.10.1
>         Environment: Linux x200 2.6.32-2 #2 SMP Wed Feb 17 01:00:03 CET 2010 x86_64 GNU/Linux
>            Reporter: Michael Stapelberg
>            Priority: Blocker
>              Labels: ipv6
>         Attachments: couchdb-ipv6.patch, patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I have a host which is only reachable via IPv6. While I can connect to a CouchDB running
on this host just fine, I cannot replicate my database to it.
> This is due to the inet6-option missing from the gen_tcp.connect() call. I will attach
a patch which fixes the issue.
> To test it, you can use a host which only has an AAAA record in the DNS. CouchDB will
immediately return 404 if you want to replicate to it unless you add the inet6 option.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message