diff options
| author | nthumann <me@n-thumann.de> | 2021-05-26 19:25:53 +0200 |
|---|---|---|
| committer | nthumann <me@n-thumann.de> | 2021-06-20 16:56:08 +0200 |
| commit | e6998838e5548991274ad2bf1697d862905b8837 (patch) | |
| tree | 5d35993988c6549d94f4c844a9f6f939a219c44e /doc/zmq.md | |
| parent | 8abe5703a9bb76bc92204a6f69775790e96208fa (diff) | |
| download | bitcoin-e6998838e5548991274ad2bf1697d862905b8837.tar.xz | |
doc: Add IPv6 address to zmq example
Diffstat (limited to 'doc/zmq.md')
| -rw-r--r-- | doc/zmq.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/zmq.md b/doc/zmq.md index 85f3370130..0521fe08d8 100644 --- a/doc/zmq.md +++ b/doc/zmq.md @@ -84,6 +84,7 @@ For instance: $ bitcoind -zmqpubhashtx=tcp://127.0.0.1:28332 \ -zmqpubhashtx=tcp://192.168.1.2:28332 \ + -zmqpubhashblock="tcp://[::1]:28333" \ -zmqpubrawtx=ipc:///tmp/bitcoind.tx.raw \ -zmqpubhashtxhwm=10000 @@ -125,6 +126,9 @@ Setting the keepalive values appropriately for your operating environment may improve connectivity in situations where long-lived connections are silently dropped by network middle boxes. +Also, the socket's ZMQ_IPV6 option is enabled to accept connections from IPv6 +hosts as well. If needed, this option has to be set on the client side too. + ## Remarks From the perspective of bitcoind, the ZeroMQ socket is write-only; PUB |