couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-665) Replication not possible via IPv6
Date Tue, 21 Feb 2012 10:17:34 GMT


Robert Newson commented on COUCHDB-665:

I've successfully replicated a db using a remote source and target for an ipv6 couchdb. Here
are my steps.

1) added this to local_dev.ini;

bind_address = ::1

2) Created a 'db1' and 'db2' database and added a doc to 'db1'.

3) Performed replication;

curl localhost:5984/_replicate -Hcontent-type:application/json -d '{"source":"http://[::1]:5984/db1","target":"http://[::1]:5984/db2"}'

4) Replication succeeded, 'db2' has one document.

Bastiaan, can you please respond to Filipe's request for more information? This would be a
release blocking ticket if it can be confirmed (and assuming my result doesn't invalidate
the ticket).

> Replication not  possible via IPv6
> ----------------------------------
>                 Key: COUCHDB-665
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: 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
>            Assignee: Filipe Manana
>            Priority: Blocker
>              Labels: ipv6
>             Fix For: 1.1, 1.0.3, 1.2
>         Attachments: COUCHDB-665-replication-ipv6.patch, 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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message