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.
pull/67/head
Matthew Vivian 2024-11-13 16:32:35 +00:00
parent ba38461ab3
commit 7ab6d49172
No known key found for this signature in database
GPG Key ID: BADAD4A1EE1C9B34
1 changed files with 2 additions and 0 deletions

View File

@ -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: