From 7ab6d491729473f9a78eaef53875cbb3ed48846e Mon Sep 17 00:00:00 2001 From: Matthew Vivian Date: Wed, 13 Nov 2024 16:32:35 +0000 Subject: [PATCH] fix: Support OCSP in dualstack mode I considered adding IPv6 support to the OCSP responder but it would add more files and complexity for (I think) little gain. Instead this change keeps the OCSP responder on IPv4 only, but makes sure it's properly configured in the hosts file even when using the -6 flag. The OCSP responder will always use IPv4, other services will be able to reach it via IPv4 regardless of whether they're using IPv6 for their own communication. --- federation/docker-compose-network-dualstack.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/federation/docker-compose-network-dualstack.yml b/federation/docker-compose-network-dualstack.yml index 03856d9..2f50952 100644 --- a/federation/docker-compose-network-dualstack.yml +++ b/federation/docker-compose-network-dualstack.yml @@ -22,6 +22,7 @@ services: - "conference.xmpp1.localhost.example=fd23:d79:d076::10" - "xmpp2.localhost.example=fd23:d79:d076::20" - "conference.xmpp2.localhost.example=fd23:d79:d076::20" + - "ocsp.localhost.example:172.50.0.88" xmpp2: networks: @@ -33,6 +34,7 @@ services: - "conference.xmpp1.localhost.example=fd23:d79:d076::10" - "xmpp2.localhost.example=fd23:d79:d076::20" - "conference.xmpp2.localhost.example=fd23:d79:d076::20" + - "ocsp.localhost.example:172.50.0.88" networks: openfire-federated-net: