From ae8da007c6f485fe3d81750ca6f965f9a884bf53 Mon Sep 17 00:00:00 2001 From: Anderson Silva Date: Sat, 22 Mar 2025 22:10:44 -0300 Subject: [PATCH] Update service status to better reflect 'no PLAT' state When checking the service status of clatd in systemctl, if no NAT64 prefix is identified, clatd prints _"No PLAT prefix could be discovered. Your ISP probably doesn't provide NAT64/DNS64 PLAT service. Exiting."_. I understand the point of it but there are cases that a maintainer (i.e. yours truly) deploys a local PLAT on LAN for an IPv6-mostly network despite the ISP who this network upstreams traffic to the Internet has it or not. So, my intention is to reflect a better status, stating that the current connection, regardless of the medium (Ethernet, Wi-Fi, WWAN, mobilt tethering a.k.a. hotspot), has no PLAT available instead of blaming the ISP only. --- clatd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clatd b/clatd index 52ea56b..2ed59f6 100755 --- a/clatd +++ b/clatd @@ -392,7 +392,7 @@ sub get_plat_prefix_from_dns64 { p("No PLAT prefix could be discovered, using fallback"); return $CFG{"plat-fallback-prefix"}; } else { - p("No PLAT prefix could be discovered. Your ISP probably doesn't provide", + p("No PLAT prefix could be discovered. Your connection probably doesn't provide", " NAT64/DNS64 PLAT service. Exiting."); cleanup_and_exit(0); }