From af4380921020ddc03d37883ff27e64c3f81a94b5 Mon Sep 17 00:00:00 2001 From: ShadowNinja Date: Sat, 10 Jul 2021 15:02:34 -0400 Subject: [PATCH] Update address verification message --- server_list/templates/address_verification_failed.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/server_list/templates/address_verification_failed.txt b/server_list/templates/address_verification_failed.txt index e1e1a04..3b9da5f 100644 --- a/server_list/templates/address_verification_failed.txt +++ b/server_list/templates/address_verification_failed.txt @@ -3,8 +3,8 @@ Announce IP: {{ announce_ip }} Address records: {{ valid_addresses | join ", " }} Help: This is usually because your server is only listening on IPv4 but your announcement is being sent over IPv6. -There are two ways to fix this: - 1. (preferred) Set bind_address = :: in your server config to listen on IPv6 and add your IPv6 address to DNS as an AAAA record. - This allows both IPv4 and IPv6 because the linux kernel will forward IPv4 requests to the IPv6 socket by default using an IPv4-mapped IPv6 address (look up IPV6_V6ONLY for more information). - On other operating systems this option may not work and you'll have to use the second option. +If that is the case there are two ways to fix this: + 1. (preferred) Set ipv6_server = true in your server config to listen on IPv6 and add your IPv6 address to DNS as an AAAA record. + On Linux this allows clients to connect using both IPv4 and IPv6 (unless you have enabled net.ipv6.bind6only). + On other operating systems this option may only work with IPv6 clients and you'll have to use the second option if you want to support IPv4. 2. Set bind_address = 0.0.0.0 in your server config to force IPv4 only, the announce will then be sent from the IPv4 address.